Home › Knowledge base › Topic

Testing accessibility

Automated tests are an important first step, but cover only a part. According to consistent sources they find roughly 30–40% of WCAG breaches.

Automated tools

Browser extensions like WAVE or axe DevTools and the built-in Lighthouse report in Chrome check the rendered page for contrast, missing alternative texts, ARIA errors and structure issues.

What only works manually

Keyboard operation and focus order, screen-reader announcement, whether motion is disruptive, whether error messages are understandable, whether the reading order is correct.

Where a11yglass fits in

The free scan checks the delivered HTML + CSS without an extension, gives a shareable report with a WCAG reference per finding and a statement generator. For depth, manual tests and JS rendering are additionally needed.

How a11yglass helps

The free scan checks the delivered HTML and CSS for automatically recognisable WCAG breaches, and names per finding the success criterion and a concrete step. It finds roughly 20–35% of issues and does not replace a full assessment.

Read on

• Overlay tools and accessibility
• EAA checklist
• The four WCAG principles

General information to the best of our knowledge, not legal advice. For an individual case, contact a law firm specialising in IT law.