Skip to content
easeweb

Accessibility checker messages, and how to fix each

The exact words the free checkers use, each with the guide that shows what goes wrong for people and how to fix it. Find yours with your browser’s Find (Ctrl+F, or Command+F on a Mac).

axe DevTools

The issue titles in the axe DevTools extension, from axe-core 4.13. Accessibility Insights and many other tools run the same rules.

Lighthouse

The failing audits in the Accessibility section of a Lighthouse or PageSpeed Insights report, from Lighthouse 13.5. Older messages are marked with the version that dropped them.

WAVE

The errors, contrast errors and alerts in the WAVE extension. WAVE is in English only.

Pa11y (HTML_CodeSniffer)

The WCAG 2 AA errors from HTML_CodeSniffer, which Pa11y runs by default. Where a message names an element or value, it is shown as “…”.

IBM Equal Access Accessibility Checker

The reason the IBM Equal Access Accessibility Checker gives for each violation. Where a message names an element or value, it is shown as “…”. English only.

When the checker finds nothing

A clean report means none of these rules failed, not that the page works. Whether alt text is right, whether focus order makes sense, whether an error message helps: a person with a keyboard and a screen reader finds those.