Skip to content

Free tool · no sign-up

Website accessibility checker

European Accessibility Act requirements apply from 28 June 2025. This runs 18 automated WCAG 2.2 checks and shows each one with its success criterion — so you can verify the result rather than take it on trust.

No sign-up. Checks the single page at the address you give.

A clean result is not EAA conformance

Automated checks catch a minority of WCAG criteria — roughly a third. A machine cannot judge whether alt text means the right thing in context, whether focus order is logical, whether an error message is understandable, or whether someone can complete checkout with a screen reader alone. This tool clears the mechanical failures. That is a necessary first step; conformance is established by a manual audit, not by a score.

Five groups, 18 checks

Every check names its WCAG criterion, so you can open the source and confirm it yourself. Work from the three priorities: failures first, then warnings.

  • Page structure

    Document language, title, a single H1, heading order with no skipped levels, main and nav landmarks.

  • Images and media

    Image alt text and whether it means anything, titles on visible iframes, audio that autoplays.

  • Forms and links

    Field labels, links with no accessible name, and link text like “read more” that means nothing out of context.

  • Keyboard and focus

    Positive tabindex breaking the tab order, a skip-to-content link, aria-hidden on something still reachable by keyboard.

  • Markup and zoom

    Viewport blocking zoom, duplicate ids breaking label association, tables without th.

FAQ

Does a high score mean EAA conformance?
No. This is the single most important thing to understand about any automated checker, this one included. Automation catches a minority of WCAG criteria — around a third by most estimates. Everything requiring judgement is invisible to a machine: whether alt text means the right thing here, whether focus order is logical, whether an error message is understandable, whether checkout can be completed with a screen reader alone. A clean result means no mechanically detectable failures. Necessary, not sufficient.
Why is there no contrast check?
Judging contrast requires rendering the CSS and knowing what colour is actually behind the text, accounting for gradients, background images and states. We do not do that, so we do not show a number. In a domain with legal exposure, an invented "all good" is worse than an honest "not checked". Test contrast by hand or in browser devtools.
What is the EAA and who does it apply to?
The European Accessibility Act is an EU directive whose requirements apply from 28 June 2025. It covers a broad range of consumer-facing digital products and services in the EU: e-commerce, banking, transport, e-books. The technical reference is EN 301 549, which builds on WCAG 2.1 AA. If you sell into the EU it applies regardless of where the company is registered.
Does it crawl the whole site?
No, just the single page at the address you give. That is deliberate: most accessibility failures come from the template and repeat everywhere, so checking the homepage plus one typical inner page usually surfaces the same issues a full crawl would.
Is anything stored?
No. We fetch the public page at the moment of the check, return the result and keep nothing. No email, no sign-up.