Top 10 Accessibility Issues
Web developers worldwide have found 74 million A11Y issues on 10 million checked web pages.
Here are the most common issues detected by Rocket Validator.
Last update: Monday, September 16, 2024
1. Images must have alternate text. 34.97%
To express their purpose and meaning to screen reader users, all images must include alternate text.
2. Buttons must have discernible text. 19.65%
For screen reader users, buttons must include recognizable text that specifies the destination, purpose, function, or action.
3. Zooming and scaling must not be disabled. 11.56%
The user-scalable="no" parameter in the <meta name="viewport"> element must not be used since it prevents text scaling and zooming, which are necessary for individuals with impaired vision.
4. Form elements must have labels. 10.54%
Each form element must have a label element attached with it.
5. Elements must only use supported ARIA attributes. 6.88%
Not all ARIA role-attribute combinations are valid. Each role must have its required qualities.
6. Certain ARIA roles must contain particular children. 6.45%
Some ARIA role values in parent elements must contain specific child elements and role values in order to execute the intended accessibility function.
7. Certain ARIA roles must be contained by particular parents. 5.59%
Certain ARIA roles must be enclosed by specific parent roles in order to carry out their intended accessibility functions.
8. Select element must have an accessible name. 1.76%
A label element with a programmatic association must be included for each select element.
9. Non-empty <td> elements in larger <table> must have an associated table header. 1.45%
Markup for data tables can be tedious and perplexing. Tables must be semantically marked up and have the proper header structure. Table navigation is made easier by features in screen readers, but for these capabilities to function properly, the tables must be precisely marked up.
10. Required ARIA attributes must be provided. 1.15%
ARIA widget roles must contain attributes describing the widget’s state or properties.
ARIA widget roles necessitate additional properties describing the widget’s state. If a needed attribute is missing, the widget’s status is not conveyed to users of screen readers.
Ready to validate your sites?
Start your trial today.