Accessibility testing that shows you the fix.

ADA website compliance means people with disabilities can use your website, under Title III of the Americans with Disabilities Act. The ADA does not name a technical standard for private businesses; courts and the Department of Justice look to WCAG, usually Level AA, and in 2024 the Department of Justice adopted WCAG 2.1 Level AA for state and local governments. Courts disagree on whether online-only businesses are covered. Since June 2025 the European Accessibility Act also requires accessible websites from many businesses serving EU customers. ADAGuard tests your pages against WCAG 2.2 Level AA and shows you what to fix.

WCAG 2.2 (Web Content Accessibility Guidelines 2.2) is the current version of the international web accessibility standard, published by the W3C. It defines 86 success criteria under four principles: perceivable, operable, understandable and robust. Level AA is the level that the ADA Title II rule, Section 508, EN 301 549 and most accessibility laws point to, some of them at an earlier WCAG version.

ADAGuard loads your page in a real Chromium browser, so JavaScript, dynamic content and CSS render as they do for a visitor. It then runs axe-core 4.10.2 plus 22 checkers of its own against the rendered page. Each issue comes with the element’s selector and HTML, the WCAG criterion it fails, and guidance on how to fix it.

Yes, on Professional plans and above. You log in yourself in a secure remote browser, ADAGuard keeps the resulting session (never your password), and scans your dashboard, member pages or any other page behind the login.

Yes. On Professional and Business plans ADAGuard pre-fills a VPAT (Voluntary Product Accessibility Template) or ACR (Accessibility Conformance Report) from your scan results and flags the criteria that still need manual testing before a conformance claim can be made. These reports are used in US federal procurement and enterprise vendor reviews.

Yes. The ADAGuard GitHub App scans the preview deployment of every pull request and posts the score and issue list as a PR comment with a GitHub check run. It finds the preview URL itself, or you set one in a .adaguard.yml file. Public repositories are always free; the free plan covers one private repository.

Yes. adaguard-io/accessibility-action@v1 runs a scan as a step in your own workflow and fails the build when the score falls below your threshold. It exposes the score, issue counts and scan ID as step outputs, supports crawling and pages behind a login, and runs on any trigger. It needs an ADAGuard API key, which comes with Professional plans and above.

EN 301 549 is the European standard for ICT accessibility, published by ETSI. It is the technical specification behind the European Accessibility Act and the EU public-sector accessibility rules. Its clause 9, for web content, maps to WCAG 2.1 Level AA, which ADAGuard checks in every scan. ADAGuard tests web pages only; clause 10 (documents) and clause 11 (non-web software) need separate evaluation.

The Accessibility for Ontarians with Disabilities Act (AODA) requires designated public-sector organisations, and businesses and non-profits with 50 or more Ontario employees, to meet WCAG 2.0 Level AA. WCAG 2.0 AA is a subset of WCAG 2.2 AA, so every ADAGuard scan checks it: 40 of the 55 WCAG 2.2 A/AA criteria are automated, fully or partly. A passing scan does not by itself establish AODA compliance; the remaining criteria need manual testing.