Easy to work with different Web browsers and Technologies
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies: As technologies and user agents evolve, the content should remain accessible.
Under this principle you will find guidelines relating but not limited to:
- Maximize compatibility with current and future user agents by writing semantic HTML
- Use the W3C validator to validate code and identify errors
- Specify the purpose of non-standard user interface components using name, role and value
- Implement an accessibility testing protocol
Let’s see how to apply the guidelines to our products
Make sure the HTML does not contain markup errors that are known to cause conflicts with assistive technologies (such as incorrect nesting of elements, or duplicate ids).
4.1.2 Name, Role and State of interactive components
The website should enable assistive technologies to understand the name, role and state of every user interface component.
Make sure status messages are identified in , so that assistive technologies can convey them to users.