WCAG CHECKER

Check a page against WCAG 2.2.

We load it in a real browser and show each issue with its element, criterion and fix.

  • 10–30 seconds
  • No signup

WCAG in four principles

  • Perceivable

    Text alternatives, captions, contrast.

  • Operable

    Keyboard access, focus, no traps.

  • Understandable

    Language, predictable behavior, form help.

  • Robust

    Names, roles and states for assistive tech.

Questions

What version of WCAG does ADAGuard check?

WCAG 2.2 Level A and Level AA, across all four principles: perceivable, operable, understandable and robust. 40 of the 55 WCAG 2.2 A/AA criteria have automated checks, fully or partly (about 73%).

Does it test WCAG 2.1 too?

Yes. WCAG 2.2 keeps every WCAG 2.1 criterion except 4.1.1 Parsing, which the W3C has retired (for HTML it is now treated as always met), so a WCAG 2.2 Level AA test covers 2.1 AA as well.

Can automated tools check all WCAG criteria?

No. Some criteria need human judgment — for example whether alt text describes the image accurately, or whether content is written clearly. ADAGuard automates 40 of the 55 WCAG 2.2 A/AA criteria, fully or partly, and lists the rest for manual review.

What WCAG level do I need to meet?

Level AA is the level most accessibility laws point to: the ADA Title II rule, Section 508, the European Accessibility Act through EN 301 549, and AODA, some of them at an earlier WCAG version. Level A is the minimum; Level AAA is not expected across a whole site.

How long does a WCAG check take?

A single page takes 10–30 seconds. Multi-page scans run about 10 seconds per page, so a 100-page site takes 15–20 minutes.