| 3.3 |
1404 |
Use markup and style sheets and do so properly.
|
Using markup improperly -- not according to specification -- hinders accessibility. Misusing markup for a presentation effect (e.g., using a table for layout or a header to change the font size) makes it difficult for users with specialized software to understand the organization of the page or to navigate through it. |
| 1.1 |
916 |
Provide equivalent alternatives to auditory and visual content.
|
Problems may occur for users with e.g. screen readers when alternative text to nontext elements are missing. |
| 12.3 |
513 |
Provide context and orientation information.
|
Complex relationships between parts of a page may be difficult for people with cognitive disabilities and people with visual disabilities to interpret. |
| 3.4 |
224 |
Use markup and style sheets and do so properly.
|
Using markup improperly -- not according to specification -- hinders accessibility. Misusing markup for a presentation effect (e.g., using a table for layout or a header to change the font size) makes it difficult for users with specialized software to understand the organization of the page or to navigate through it. |
| 10.1 |
187 |
Use interim solutions.
|
For example, older browsers do not allow users to navigate to empty edit boxes. Older screen readers read lists of consecutive links as one link. These active elements are therefore difficult or impossible to access. |
| 9.2 |
170 |
Design for device-independence.
|
Not providing a device independent interface, e.g. requiring a mouse to visit some links,
makes it difficult for those users who have challenges with operating a mouse. |
| 12.4 |
105 |
Provide context and orientation information.
|
Complex relationships between parts of a page may be difficult for people with cognitive disabilities and people with visual disabilities to interpret. |
| 5.5 |
84 |
Create tables that transform gracefully.
|
Tables should be used to mark up truly tabular information ("data tables"). Content developers should avoid using them to lay out pages ("layout tables"). Tables for any use also present special problems to users of screen readers |
| 3.5 |
63 |
Use markup and style sheets and do so properly.
|
Using markup improperly -- not according to specification -- hinders accessibility. Misusing markup for a presentation effect (e.g., using a table for layout or a header to change the font size) makes it difficult for users with specialized software to understand the organization of the page or to navigate through it. |
| 4.3 |
50 |
Clarify natural language usage.
|
When content developers mark up natural language changes in a document, speech synthesizers and braille devices can automatically switch to the new language, making the document more accessible to multilingual users. |
| 10.4 |
47 |
Use interim solutions.
|
For example, older browsers do not allow users to navigate to empty edit boxes. Older screen readers read lists of consecutive links as one link. These active elements are therefore difficult or impossible to access. |
| 9.5 |
26 |
Design for device-independence.
|
Not providing a device independent interface, e.g. requiring a mouse to visit some links,
makes it difficult for those users who have challenges with operating a mouse. |
| 1.5 |
22 |
Provide equivalent alternatives to auditory and visual content.
|
Although some people cannot use images, movies, sounds, applets, etc. directly, they may still use pages that include equivalent information to the visual or auditory content. |
| 5.2 |
10 |
Create tables that transform gracefully.
|
Tables should be used to mark up truly tabular information ("data tables"). Content developers should avoid using them to lay out pages ("layout tables"). Tables for any use also present special problems to users of screen readers |
| 12.1 |
10 |
Provide context and orientation information.
|
Complex relationships between parts of a page may be difficult for people with cognitive disabilities and people with visual disabilities to interpret.
|
