Skip to main content

Web Accessibility Laws by Country and Sector (2026)

Benjamin Morton

Nearly every accessibility law measures you against WCAG, yet they differ on who is covered, which WCAG version counts and when it starts to bite. This page is the map: find the row that describes your organization, note the standard and the date, then follow the link to the post that covers that law in depth.

It is a developer's summary, not legal advice. If a deadline or penalty matters to your business, check it with a lawyer who practices in that jurisdiction.

Short answer: In the US, private businesses fall under ADA Title III (no technical standard in regulation), state and local governments under ADA Title II (WCAG 2.1 AA, due April 2027 or April 2028 depending on size), and federal agencies under Section 508 (WCAG 2.0 AA). In the EU, the European Accessibility Act has applied since June 28, 2025, and the newest version of its technical standard maps to WCAG 2.2 AA. UK public bodies must meet WCAG 2.2 AA. Where a law names a standard it is WCAG Level AA, so building to WCAG 2.2 AA covers every row below.

Which Law Applies to You?

If you are...

Law

Standard

Key date

Read next

A US business open to the public, such as a shop, bank or restaurant

ADA Title III

None in regulation; DOJ points to WCAG as guidance

No separate date: the ADA already applies

Lawsuit numbers

A US state or local government, including school districts

ADA Title II

WCAG 2.1 AA

Apr 26, 2027 (population 50,000+); Apr 26, 2028 (smaller entities, special districts)

The Title II extension, explained

An organization funded by the US Department of Health and Human Services

Section 504 (HHS rule)

WCAG 2.1 AA

May 11, 2027 (15+ employees); May 10, 2028 (fewer than 15)

Why 504 can come first

A US federal agency, or a vendor selling technology to one

Section 508

WCAG 2.0 A and AA

Required since Jan 18, 2018

The VPAT section below

Selling listed products, or consumer services such as e-commerce, banking or e-books, in the EU

European Accessibility Act

EN 301 549: WCAG 2.1 AA in V3.2.1, WCAG 2.2 AA in V4.1.1

Applies since Jun 28, 2025

EAA scope and penalties

A UK public sector body

Public Sector Bodies Accessibility Regulations 2018

WCAG 2.2 AA, plus a published accessibility statement

In force since Sep 23, 2018

Per-criterion WCAG 2.2 tests

Any organization providing services to the public in the UK

Equality Act 2010 (Disability Discrimination Act 1995 in Northern Ireland)

None named: a duty to make reasonable adjustments

Already applies

How to test each AA criterion

An Ontario public sector body, or a business or non-profit with 50+ employees

AODA

WCAG 2.0 AA, except 1.2.4 and 1.2.5

Jan 1, 2021

The full A and AA test list

Sources: ADA.gov (Title III, 2022); Federal Register (Title II, 2026) and Federal Register (Section 504, 2026); US Access Board (Section 508); EUR-Lex (EAA); ETSI (EN 301 549 V4.1.1); GOV.UK (UK); Ontario.ca (AODA).

Three Rows That Need a Closer Look

ADA Title III: a duty without a standard

The Justice Department says it "does not have a regulation setting out detailed standards" for the web, but that the ADA's nondiscrimination rules still apply online and that WCAG and the Section 508 Standards "provide helpful guidance" (ADA.gov, 2022). DOJ's 2024 web rule did adopt WCAG 2.1 Level AA, but only for state and local government (Federal Register, 2026). For a private site, that makes 2.1 AA the nearest thing to an official benchmark, and 2.2 AA a safe margin above it. Our lawsuit analysis covers who gets sued and why.

EAA: the standard moved to WCAG 2.2 in 2026

The directive covers listed products placed on the EU market after June 28, 2025, and listed services provided to consumers after that date, including consumer banking, e-books and e-commerce (EUR-Lex, 2019). It sets essential requirements, not a test method, and EN 301 549 fills that gap. Version 3.2.1 treats WCAG 2.1 Level AA as equivalent to its web clauses (ETSI EN 301 549 V3.2.1, 2021). Version 4.1.1, adopted on August 24, 2026 under the Commission's standardisation request for the EAA, does the same with WCAG 2.2 Level AA, and once it is cited in the Official Journal of the EU, meeting it gives a presumption of conformity with the directive (ETSI EN 301 549 V4.1.1, 2026).

So if you sell into the EU, target 2.2 AA now. Scope, the microenterprise exemption, transition periods and fines by country are in our EAA guide for developers.

UK: one rule for the public sector, one for everyone

The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 came into force on September 23, 2018. GOV.UK's guidance says a public body meets them if it meets WCAG 2.2 AA and publishes an accessibility statement (GOV.UK, 2024).

Everyone else is covered by the Equality Act 2010. It puts a duty to make reasonable adjustments on every service provider (section 29(7)), and where the barrier involves information, the reasonable steps include providing it in an accessible format (section 20(6)). The Act names no WCAG version, so the practical yardstick is the one the government applies to its own sites: WCAG 2.2 AA.

Which WCAG Version Should You Build To?

WCAG 2.2 AA. W3C describes 2.2 as backwards compatible with 2.1, and its working group "recommends that sites adopt WCAG 2.2 as their new conformance target, even if formal obligations mention previous versions" (W3C, 2024).

One wrinkle: 2.2 removed 4.1.1 Parsing, but if you report against a rule that cites 2.0 or 2.1, such as Section 508, Title II or AODA, W3C notes you "may need to continue to test and report 4.1.1." Our WCAG 2.2 AA test list gives the automated rule, manual step and pass condition for every A and AA criterion.

WCAG 3 is not something to plan compliance around yet: it is still a W3C Working Draft, most recently published on September 10, 2026 (W3C, 2026). Our WCAG 3 explainer covers what the draft proposes.

Selling to Government or Large Buyers: the VPAT

An Accessibility Conformance Report (ACR) documents how a product meets the Section 508 standards. The most common way to complete one is ITI's Voluntary Product Accessibility Template, after testing the product against the standards (Section508.gov). The current template, VPAT 2.5Rev from April 2025, comes in 508, EU, WCAG and INT editions (ITI, 2025). Use the edition that matches the law your buyer cites, and base it on manual as well as automated results.

How to Get Compliant

  1. Audit. Scan for a baseline, then do a manual pass. The per-criterion checklist shows what axe-core can check and what needs a person, and what each method catches explains why you need both.
  2. Fix. Start with the failures most sites share: fixes for the ten most frequent failures, contrast ratios in CSS and focus handling in single-page apps. An overlay widget will not do this for you; here is why.
  3. Test. Run axe in CI so a new failure blocks the merge (a pull request gate), and repeat keyboard and screen reader checks when a release changes a user flow.
  4. Monitor. Rescan on a schedule, because content and third-party scripts change after you ship, and keep your accessibility statement or ACR in step with the current release.

Frequently Asked Questions

Which laws apply to a US company that also sells in the EU and UK?

Possibly all three: ADA Title III at home, the EAA if you sell a listed product or consumer service such as e-commerce, and the Equality Act 2010 for UK customers. One WCAG 2.2 AA program covers the technical side of each.

Do these laws cover mobile apps?

Yes, in most cases. The DOJ Title II and HHS rules both cover web content and mobile apps, the UK regulations cover public sector websites and mobile applications, and EN 301 549 applies its non-web software clause to mobile applications.