We load it in a real browser and show each issue with its element, criterion and fix.Paste a URL for a free WCAG compliance test. We load the page in a real browser, run axe-core plus our own checks, and show each issue with its element, criterion and fix.
One page, 10–30 seconds
No signup
What you get.
A score out of 100
With every issue grouped by severity — critical, serious, moderate, minor.
The element and the fix
Each issue shows its HTML, the WCAG criterion, and how to fix it.
Honest coverage
Automated checks cover 40 of 55 WCAG 2.2 A/AA criteria. We list the 15 that need a person.
WCAG in four principles
01
Perceivable
Text alternatives, captions, contrast.Can people see or hear it? Text alternatives, captions, contrast.
02
Operable
Keyboard access, focus, no traps.Can people use it? Keyboard access, focus, enough time, no traps.
03
Understandable
Language, predictable behavior, form help.Can people follow it? Language, predictable behavior, form help.
04
Robust
Names, roles and states for assistive tech.Does it work with assistive tech? Valid names, roles and states.
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 does a WCAG check leave for a person to test?
Judgment. Whether alt text actually describes the image, whether the tab order makes sense, how a screen reader user gets through a dynamic page, and whether a login asks for something a person can’t reasonably do. Run the scan first to clear what it finds, then spend manual testing on the criteria it can’t settle.
How should I use the results?
Give each issue to whoever owns the code, with its criterion number (1.4.3 for contrast, 4.1.2 for name, role and value) and the failing element — a criterion is something a developer can act on, “low contrast” is not. Separate your own code from third-party widgets, which need a vendor ticket. Then re-scan: a fix can resolve one issue and introduce another. Keep the dated reports and fixes as a record of the work.
How often should I run a WCAG check?
After every significant release. Accessibility problems arrive the way other regressions do — through changes nobody tested for them — and sites with large catalogs or many third-party scripts change most often. Paid plans can scan on a schedule and email the results.
Can it check WCAG AAA?
Partly. The scan includes AAA checks such as enhanced contrast (1.4.6), focus appearance (2.4.13) and target size (2.5.5), and lists those results separately from the AA ones. With a free account you can set your scoring target to WCAG 2.2 AAA in settings, on any plan. Many AAA criteria need a person to judge, and AAA is not expected across a whole site.
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.
