Standards

Eight laws.
One technical standard.

Accessibility law is written in different places, enforced by different bodies, and names different versions of the same guidelines. Almost all of it is assessed against WCAG — and WCAG conformance is cumulative, so the technical bar underneath every framework below is covered by one audit at the top level.

Every date read from the primary source · Not legal advice

Recently changed

Three dates worth knowing.

Two of these moved in 2026 and most pages on this subject have not caught up.

26 Apr 2027 / 26 Apr 2028

ADA Title II compliance dates

The Department of Justice's final rule of 24 April 2024 set WCAG 2.1 Level AA for state and local government web content. An interim final rule published 20 April 2026 extended the compliance dates to 26 April 2027 for entities serving 50,000 or more people, and 26 April 2028 for smaller entities and special districts.

30 Nov 2026

EN 301 549 moves to WCAG 2.2 AA

V4.1.1 was published in September 2026 and takes the web, document and software clauses to WCAG 2.2 Level AA. The version cited in the Official Journal today is still V3.2.1, at 2.1 AA; the V4.1.1 citation is scheduled for 30 November 2026. If you already test at 2.2, nothing changes for you on that date.

28 Jun 2025

The EAA is in force

Directive (EU) 2019/882 has applied to services provided to consumers in the EU since 28 June 2025, with e-commerce named explicitly at Article 2(2)(f). It is a market-access rule rather than a territory one, so a business outside the EU selling to EU consumers is inside its scope.

Reference

What each one asks for.

Pick a framework for what it is, who it binds, the technical bar it points to, and — separately — what a scan does not settle about it.

International · W3C

Web Content Accessibility Guidelines 2.2

The technical standard every law below points at. Published by the World Wide Web Consortium as a Recommendation in October 2023, it defines what an accessible page actually is: perceivable, operable, understandable and robust, broken into testable success criteria at three levels.

Who it binds
Nobody, directly — WCAG is not legislation. It matters because it is the yardstick the regulations, the courts and the procurement standards all borrow.
The technical bar
Levels A, AA and AAA. Version 2.2 adds nine success criteria to 2.1 and retires 4.1.1 Parsing. Conformance is cumulative: content that meets 2.2 Level AA also meets 2.1 AA and 2.0 AA.

What our scan covers

WCAG 2.2 · A, AA and AAA

Tested automatically against WCAG 2.2 A, AA and AAA, with every finding named, ranked and tied to the criterion it fails.

What it does not settle

Roughly a fifth to a third of the success criteria can be decided by a machine at all. Your report says which ones were tested and which were not.

AdaChecked reports where your site stands against WCAG. It does not certify compliance with any law, and nothing here is legal advice.

FAQ

Questions about scope.

That depends on where you operate, who you sell to, and what kind of organisation you are — and it is a legal question rather than a technical one, so it belongs with your counsel rather than with a vendor. What is true regardless: almost every one of these frameworks is assessed against WCAG, so testing against WCAG is useful before you have the answer.
Yes. WCAG conformance is cumulative by design: content that satisfies 2.2 Level AA also satisfies 2.1 AA and 2.0 AA. That is why one audit at the top level covers the technical bar under laws that name different versions — AODA names 2.0, EN 301 549 currently names 2.1, and Section 508 incorporates 2.0.
No. A scan measures the technical bar and only the part of it a machine can decide — roughly a fifth to a third of the success criteria. Several of these laws also carry duties an audit does not touch at all: AODA has filing requirements, the EAA has documentation requirements, and the Accessible Canada Act is largely about published plans and progress reports.
Ontario's Integrated Accessibility Standards Regulation, O. Reg. 191/11 s.14(4), requires WCAG 2.0 Level AA other than success criterion 1.2.4 Captions (Live) and 1.2.5 Audio Descriptions (Pre-recorded). Both relate to media production rather than to page code, and the regulation carved them out when the schedule was set.
From the primary sources, and they are cited in the page source next to the content they support: ada.gov for the Title II rule and its extension, ontario.ca for O. Reg. 191/11, ETSI for EN 301 549, EUR-Lex for the EAA, and the US Access Board for the Section 508 refresh. If you find one out of date, tell us and we will correct it.

Test against the top of the stack.
It covers the rest.

Scan any site against WCAG 2.2 A, AA and AAA and get every finding mapped to the criterion it fails. Free plan, no card, nothing installed on your site.

Free plan · No card · AdaChecked does not provide legal advice