What the free checker tests
The quick check covers exactly one page – the one you enter:
- Real rendering: the page loads in Chromium, including JavaScript, web fonts and lazy-loaded content. We test what people actually see, not just the source.
- WCAG 2.2 A and AA rules: every applicable axe-core rule runs, and each result is mapped to a WCAG success criterion.
- Colour contrast for every piece of text, measured against its real background (1.4.3 Contrast (Minimum)).
- Structure and semantics: headings, landmarks, page language and title, and the names and roles of links, buttons and form fields.
What no automated checker can decide
No tool can call a website "accessible" on its own. Of the 55 WCAG 2.2 A and AA success criteria, our checks reach 52, none of them completely – a check can find a failure, never prove a pass – and 3 they cannot reach at all. How far we get on each criterion, measured, is in our WCAG 2.2 checklist.
A few examples that need human judgement:
- Alt text: a tool knows whether an image has alt text, not whether "IMG_4711.jpg" describes it.
- Headings: their presence is testable; whether they structure the content sensibly is not.
- Form errors: whether a message explains how to fix the problem.
- Captions and audio description: whether they exist, are complete and in sync.
- Focus order: whether tabbing through the page follows a logical sequence.
That is why our results have three states, not two: failed, partly tested and untested. Untested never means passed. Checks that can't reach a verdict – text over a photo, for instance – go into a separate "potential issues" list instead of silently counting as a pass.