Automated WCAG assessment
Automated checks against WCAG, with every rule’s result shown — including rules that found nothing to test.
How it works
- Your page is loaded in a real browser and checked by an open-source accessibility rules engine.
- Each rule reports one of four outcomes: a problem, a pass, “needs review” or “not applicable on this page”.
- Pages are observed at a desktop width and at a narrow, phone-like width.
Details
- Choose WCAG 2.0, 2.1 or 2.2 as your baseline — for example 2.0 for Section 508 work. WCAG 2.2 Level A and AA is the default.
- Findings are grouped by WCAG success criterion, with the affected elements and how to fix them.
- Best-practice advice is shown separately and never counted as a WCAG failure.
- See how each automated rule fares in W3C’s own implementation tests — and tell us when a finding is wrong.
What it does not do
- It does not decide the criteria that need human judgement — for WCAG 2.2 A/AA that is 32 of 55. They are listed for manual review, never shown as passed.
- A page scan does not click, type or submit forms on your site. Journeys you record yourself do click and type — and submit nothing unless you confirm a test environment.
- A clean automated result is not a statement that the page conforms to WCAG.