“Are we ADA compliant?” and “do we need WCAG?” and “does the EAA apply to us?” sound like three separate questions. They’re really one question asked three ways — because a US civil-rights law, a technical standard, and an EU directive all converge on the same underlying work.
ADA is a US law, WCAG is a technical standard, and the EAA is an EU directive — each operates at a different level, and they overlap in practice.
Neither ADA nor the EAA names its own technical bar from scratch — courts and the EAA’s EN 301 549 both point back to WCAG.
ADA’s reach is broad and litigation-defined; the EAA’s is narrower but explicit, covering named product and service categories sold into the EU.
These three get run together constantly because they operate at three different levels that overlap in practice. ADA is a US law with no named technical standard. WCAG is a technical standard with no legal force of its own. The EAA is an EU law that explicitly names a standard — via EN 301 549 — aligned to WCAG. Build to WCAG 2.2 AA and you’re addressing the technical substance behind both the US litigation risk and the EU’s specific legal requirement — but the EAA still requires checking whether your product or service category is actually in scope, since its obligations are narrower than ADA’s broad reach.
| Dimension | ADA (US) | WCAG | European Accessibility Act (EU) |
|---|---|---|---|
| What it is | A US civil rights law (1990) prohibiting disability discrimination; names no technical web standard itself. | A W3C technical standard defining testable success criteria for digital accessibility, now at 2.2 with 3.0 in development. | An EU directive (2019/882) requiring specific products and services to meet accessibility requirements, with most 2025 compliance obligations already in force. |
| Legal mechanism | Enforced through litigation and DOJ guidance; courts consistently point to WCAG as the de facto benchmark, though ADA itself names no standard. | Not a law — a voluntary standard that becomes legally binding only when referenced by a law or regulation, as the EAA and many government mandates do. | A binding EU directive transposed into each member state’s national law, explicitly referencing EN 301 549, itself aligned to WCAG 2.1 AA. |
| Who it applies to | Places of public accommodation and their digital properties, as interpreted through ADA Title III case law — broad reach for US-facing businesses. | Anyone building digital products who wants a testable benchmark for “accessible” — applies by reference, not directly. | Specific product and service categories sold or offered in the EU — e-commerce, banking, e-books, transport ticketing, telecom — narrower than ADA’s reach. |
| Enforcement & penalties | Private lawsuits and DOJ enforcement; no fixed statutory penalty, with damages and remediation orders varying by case. | No enforcement of its own — it only has teeth when a law like the EAA or a government mandate requires conformance to it. | Member-state-level enforcement with fines and potential market withdrawal for non-conforming products; specifics vary by country’s transposition. |
| Practical takeaway | Compliance risk is real but technically undefined — courts default to WCAG 2.1/2.2 AA as the practical benchmark. | The common technical language both ADA litigation and EAA conformance point back to — build to WCAG and you’re addressing both. | The clearest, most specific obligation of the three, but only if your product or service falls into one of its named categories. |
Because WCAG sits underneath both ADA’s litigation risk and the EAA’s explicit requirement, a single accessibility programme built to WCAG 2.2 AA covers the technical substance of both — you’re not running two parallel compliance efforts. The EAA’s explicit technical reference, EN 301 549, aligned with WCAG 2.1 AA and partially 2.2, is actually the more useful anchor precisely because it’s specific; ADA compliance stays a moving target defined by case law rather than a named standard.
Build to WCAG 2.2 Level AA as your technical baseline regardless of which legal framework applies — it’s the common substance behind both. Then check EAA applicability specifically: does your product or service fall into one of its named categories, and do you sell or offer it into the EU? If yes, confirm you meet EN 301 549’s specific requirements, which go slightly beyond pure web content into areas like hardware and support services for some product categories.
Not explicitly — the ADA names no technical standard — but US courts and DOJ guidance have consistently pointed to WCAG 2.1/2.2 AA as the practical benchmark in litigation and settlements.
Yes, if they sell or offer in-scope products or services into the EU. Applicability is based on market presence, not company headquarters.
Largely, for the web-content parts — the EAA’s technical reference (EN 301 549) aligns closely with WCAG, but some product categories have additional hardware or service requirements beyond pure web content.
WCAG has no legal force by itself — it only becomes binding when a law like the EAA, or a court interpreting the ADA, points to it as the benchmark for compliance.