Top 10 Accessibility Issues
Web developers worldwide have found 78 million A11Y issues on 10 million checked web pages.
Here are the most common issues detected by Rocket Validator.
Last update: Saturday, December 21, 2024
1. All page content should be contained by landmarks. 39.72%
The recommended practice is to keep all content, excluding skip links, in designated areas such the header, nav, main, and footer.
2. Elements must meet minimum color contrast ratio thresholds. 30.11%
According to WCAG 2 AA contrast ratio thresholds, all text elements must have sufficient contrast between foreground text and background colors.
3. Links must have discernible text. 9.85%
When used as links, link text and alternative text for images must be recognizable by screen readers, have no duplicate labels, and be focusable.
4. All touch targets must be 24px large, or leave sufficient space. 9.34%
Touch targets must have a minimum dimension of 24 by 24 CSS pixels. The greatest unobscured area of the touch target is used to calculate size. The target must be at least 24 CSS pixels distant from any other touch target if its size is insufficient.
5. Heading levels should only increase by one. 2.39%
The h1 through h6 element tags must be in a sequential order for headings to be in a correct logical order.
6. Elements must have their visible text as part of their accessible name. 1.98%
The visible label of interactive items labeled through their content must be included in their accessible name.
7. Landmarks should have a unique role or role/label/title (i.e. accessible name) combination. 1.80%
Landmarks must have an unique role or role/label/title (i.e. accessible name) combination.
8. Document should have one main landmark. 1.64%
A best practice is to guarantee that there is only one primary landmark for navigating to the page’s principal content, and if the page has iframe components, each should contain either no landmarks or a single landmark.
9. Images must have alternative text. 1.63%
To express their purpose and meaning to screen reader users, all images must include alternative text.
10. Elements in the focus order should have an appropriate role. 1.53%
Whether native HTML or a custom widget, user input elements need to play the right roles in order to make their meaning clear to screen reader users when they are focused on and landed on. If a custom widget, the element’s function must be correctly exposed by using appropriate ARIA role values rather than abstract roles.
Ready to validate your sites?
Start your trial today.