Free website accessibility checker for WCAG 2.2

Paste an address and we check that page against WCAG 2.2 AA in a real browser. One page checked here in about 30 seconds, then — if you want it — a 100-page report with the keyboard agent by email. Free, no account, no card.

Check a page now

We check the one page at this address. The full report, by email, covers up to 100 pages of the site.

  • Free
  • No sign-up
  • Results right here

Request your free scan

One form, a few fields. The report comes by email, usually within the hour; a person replies within one working day.

A page on your site, for example /checkout. Leave empty and it starts on the homepage.

We use your details only to answer this request. No newsletter unless you ask for one.

  • No script to install, no code change
  • Your data stays in the EU and is never sold

What the full report adds

  • Your baseline score

    Automated WCAG 2.2 AA check results across the pages we reach, with detected failures and their frequency. A starting point for review, not a conformance certificate.

  • A keyboard walk

    Real key presses through the page you name — tab order, visible focus, traps and dead ends — with the keystroke trail and a screenshot at each failure.

  • What no scan can decide

    The WCAG 2.2 AA criteria our checks cannot settle, listed as partial or untested rather than left blank — so the report never reads cleaner than it is.

  • A fix list

    Grouped by rule, with the fixes that help most for the least work first. Yours to keep, whatever you decide about us.

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.

Frequently asked questions

Is the checker really free?

Yes. The one-page quick check needs no account and no email. For the full report (up to 100 pages plus a keyboard run) we ask for your email so we can send it. There's no subscription.

If the checker finds nothing, is my site accessible?

Not necessarily. A tool can only decide some WCAG criteria. No findings means the automatable rules pass on that page. We show the remaining criteria as "partial" or "untested".

Which standard does the checker use?

WCAG 2.2 levels A and AA. In the full report each result is also mapped to the matching clause in chapter 9 of EN 301 549, the European standard for digital accessibility.

Can I check pages behind a login?

Not in the free check. From an account you can give the crawler a way in: the browser's password prompt, a login form or token headers. The credentials are stored encrypted and sent to your own domain only.

How is this different from WAVE or Lighthouse?

Those check one page in your browser. The full report covers up to 100 pages, sends a keyboard agent along a real journey and flags untestable criteria explicitly. The platform adds scheduled crawls, history and evidence for your statement.

Do I still need an audit?

If you want to make a reliable statement about conformance: yes – or at least documented manual tests for the criteria no tool can decide. The automated check shows you where to start.

See what a scan finds on your site

One page in about thirty seconds, no email needed. The full report covers up to 100 pages and a keyboard journey.