AccessLumens

WCAG criteria and accessibility rules, with real failure rates

See which WCAG criteria actually fail on real websites and how often, and which of them automated testing can detect at all.

This covers all 86 success criteria in WCAG 2.2, at Levels A, AA and AAA. (WCAG 2.2 lists 87, but 4.1.1 Parsing is obsolete and no longer tested.) We publish the limits of automation because they matter: across 609 website scans and 941 PDF documents, only 20 of the 86 criteria produced any automated signal. A site can pass every automated check we run and still fail criteria that need a person to evaluate.

Want these checks on your own site? A free scan reports every criterion automation can reach on a web page, with the exact elements that fail.

Run a free scan

What can automation actually test?

Automated testing speeds up an accessibility review. It does not replace the person doing it.

  • measured20 of 86

    Our scans detected failures of this criterion, on websites, in PDFs or both. The rate is a floor: it counts only the parts an engine can see.

  • proxy only8 of 86

    Related checks can bound it but cannot confirm it, so we publish no failure rate.

  • needs a person58 of 86

    No automated check can establish it, ours included. Only a human review can say whether a page passes.

Highest measured failure rates on websites

Share of the 609 scanned sites that fail each, across our five research cohorts. This is a convenience sample, not a representative estimate of the web. Rates for the 941 county government PDFs are a separate population, listed per criterion below and labelled as such.

Explore all 86 criteria

Level

Principle

Testing

Showing 86 of 86 criteria

1.1 Text Alternatives

Perceivable

1.2 Time-based Media

Perceivable

1.3 Adaptable

Perceivable

1.4 Distinguishable

Perceivable

2.1 Keyboard Accessible

Operable

2.2 Enough Time

Operable

2.3 Seizures and Physical Reactions

Operable

2.4 Navigable

Operable

2.5 Input Modalities

Operable

3.1 Readable

Understandable

3.2 Predictable

Understandable

3.3 Input Assistance

Understandable

4.1 Compatible

Robust

Accessibility checks beyond WCAG

Not every accessibility problem maps to a WCAG success criterion. These 22 checks find structural problems that decide whether assistive technology can navigate a page efficiently rather than merely read it. Failing them is not failing WCAG, but they still matter to the people using the page.

What this does not measureLimits of these figures, and where the corpus came from
  • These are five targeted cohorts, not a random sample of the web. Per-cohort rates are the figure to quote; the pooled rate is a convenience sample.
  • Denominators count sites that produced a result. Sites that were blocked or errored are excluded rather than counted as passing.
  • Occurrence counts are floors: the engine records at most 25 occurrences of a rule per page.
  • The EU and Indian cohorts retained only the primary success criterion per finding, so a rule mapping to several criteria contributes to one of them in those two cohorts and to all of them in the other three.
Cohorts in the corpus, with sites scanned and attempted
CohortScannedAttempted
Shopify DTC stores7575
US local government158221
US healthcare providers208218
EU e-commerce107170
Indian financial services6172

Corpus generated 2026-09-18.