Top 10
Critical
Accessibility
Issues
Web developers worldwide have found
71 million A11Y issues
on 9 million checked web pages.
Here are the most common issues detected by Rocket Validator.
Last update: Friday, July 26, 2024
1. Images must have alternate text. 36.11%
To express their purpose and meaning to screen reader users, all images must include alternate text.
2. Buttons must have discernible text. 19.62%
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. 12.26%
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. Elements must only use supported ARIA attributes. 8.66%
Not all ARIA role-attribute combinations are valid. This rule ensures that each role has the required qualities.
5. Form elements must have labels. 7.50%
Each form element must have a label element attached with it programmatically.
6. Certain ARIA roles must contain particular children. 7.34%
Some ARIA parent role values 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. 3.93%
Certain ARIA roles must be enclosed by specific parent roles in order to carry out their intended accessibility functions.
8. Non-empty <td> elements in larger <table> must have an associated table header. 1.65%
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.
9. Select element must have an accessible name. 1.61%
A label element with a programmatic association must be included for each select element.
10. Required ARIA attributes must be provided. 1.34%
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.