Foundations

Is WCAG a Law? How the Guidelines Map to Real Legal Requirements

No — the W3C isn't a government body, and WCAG isn't a statute. Nobody can be sued directly under "WCAG." But that's a technicality that matters less than it sounds like it should, because nearly every accessibility law that does have legal force either explicitly references WCAG by name or gets interpreted by courts and regulators as requiring it in practice.

In the United States

ADA Title II (state and local government) was amended by a 2024 DOJ rule that explicitly requires web content to meet WCAG 2.1 Level AA. This is a real, enforceable technical standard with real compliance dates. A DOJ interim final rule effective April 20, 2026 extended both: large entities (population 50,000+) must comply by April 26, 2027, and smaller entities and special districts by April 26, 2028.

ADA Title III (private businesses open to the public) is different: the statute itself never mentions WCAG or the word "website." But in the absence of formal regulations, courts have consistently treated WCAG 2.0/2.1 AA as the de facto benchmark for what "accessible" means when private businesses get sued — thousands of ADA Title III web accessibility lawsuits are filed every year, and settlement agreements almost always require the defendant to meet WCAG AA going forward.

Section 508 requires US federal agencies and their vendors to meet accessibility standards that were formally updated to align with WCAG 2.0 AA (and are moving toward referencing 2.1/2.2 over time).

In the European Union

The European Accessibility Act (EAA) has applied since June 28, 2025 and sets functional accessibility requirements for covered private-sector products and services. EN 301 549 v3.2.1 incorporates WCAG 2.1 AA for web content and is widely used as technical guidance, but that version is harmonised for the Web Accessibility Directive rather than as an EAA-specific harmonised standard. Updated standards for the EAA are still being developed.

The practical takeaway

"Is WCAG a law?" is the wrong question. Ask which law applies, which WCAG version it incorporates (if any), and what requirements sit outside WCAG. Building to WCAG 2.2 AA is a useful forward-looking engineering target and includes the active 2.0/2.1 A/AA criteria, but it does not by itself satisfy every legal, product-scope, documentation, or non-web obligation. See WCAG Versions Explained.

Common questions

Is WCAG legally required?

Not on its own. ADA Title II and Section 508 incorporate particular WCAG versions, while other regimes use WCAG as a benchmark or technical route. The EAA states functional requirements; EN 301 549 v3.2.1 is currently harmonised for the Web Accessibility Directive and used as guidance while EAA-specific standards are developed.

Which WCAG version and level do most laws require?

Level AA is the common technical target, but the version depends on the regime: Revised Section 508 incorporates WCAG 2.0 A/AA and ADA Title II requires WCAG 2.1 AA. EAA obligations are functional rather than a direct incorporation of WCAG 2.1 or 2.2.

Can you be sued for failing WCAG?

You are not sued under WCAG itself, but under the accessibility law that adopts it — for example an ADA Title III lawsuit that uses WCAG 2.1 AA as the yardstick for whether a site is accessible.

Does meeting WCAG guarantee legal compliance?

No. Conforming to WCAG AA is strong evidence of accessibility and the practical standard courts use, but no tool or checklist can guarantee legal compliance — automated testing alone covers only part of the criteria, and manual review is still required.