EAA vs ADA: the differences EU agencies need to explain

Why this matters for agencies

If you are an EU agency, you probably have at least one US-headquartered client selling into the EU market — a Shopify brand, a SaaS company, a media publisher, a D2C retailer. Those clients have been running an ADA-focused accessibility program for years. When you mention the EAA, the first response you usually get is: "Are we not already covered by our ADA compliance?"

The short answer is no. The long answer is what this article covers. The EAA is a different legal instrument with different coverage rules, different technical references, and different enforcement mechanics. A site that passes an ADA-style audit in the US may still be non-compliant in Germany, France, or Spain — and vice versa.

Legal basis

The ADA is the Americans with Disabilities Act of 1990 — a US civil rights statute. It prohibits discrimination on the basis of disability across employment (Title I), state and local government services (Title II), and public accommodations (Title III). The ADA itself does not mention websites; courts have over the last decade extended Title III to cover websites of businesses considered public accommodations. The 2024 DOJ rule under Title II explicitly requires WCAG 2.1 AA for state and local government websites.

The EAA is Directive 2019/882, an EU directive adopted in April 2019 and transposed into national law by every member state. Enforcement became applicable on June 28, 2025. Unlike the ADA, the EAA explicitly names digital services: e-commerce, consumer banking, electronic communications, passenger transport ticketing, e-books, and audio-visual on-demand services. Each EU country enforces it through its own national transposition (BFSG in Germany, Ordonnance 2023-859 in France, Ley 11/2023 in Spain, Law 232/2022 in Romania, and so on).

Who is covered

The coverage models are fundamentally different. The ADA expanded to cover private-sector websites through case law and the 2010 ANPRM; the boundary is still being litigated and varies by federal circuit. The EAA defined coverage in statute and makes it concrete from day one.

Technical standard

Both regimes point at WCAG, but through different routes.

ADA: the 2024 DOJ rule for Title II explicitly requires WCAG 2.1 Level AA for state and local government websites. For Title III (private sector websites), there is no statutory technical standard; WCAG 2.1 AA is the de facto bar because it is what DOJ has consistently cited in settlements and consent decrees, but courts have not uniformly mandated it.

EAA: the directive itself is technology-neutral. Conformance with the harmonized European standard EN 301 549 gives you a presumption of conformance with the EAA. EN 301 549 clause 9 incorporates WCAG 2.1 Level AA for web content, plus additional provisions for software and non-web documents. This means the concrete technical bar for web content under both EAA and current ADA practice is the same: WCAG 2.1 Level AA.

Practical takeaway: a site that passes WCAG 2.1 AA under a US-style audit has done most of the technical work required for EAA conformance. What is usually missing is the EU-specific documentation and non-web-content provisions (authentication flows, captions, and so on) that EN 301 549 adds on top of WCAG.

Enforcement

This is where the two regimes diverge most sharply.

ADA enforcement is litigation-driven.Private plaintiffs (often serial filers) bring Title III cases in federal district court. Settlements typically include a consent decree requiring WCAG conformance, attorneys' fees, and damages (in some states). The DOJ rarely initiates private-sector cases. Volume: roughly 4,500+ federal ADA web lawsuits filed in 2024 according to UsableNet's tracking.

EAA enforcement is regulator-driven. Each member state designates a market-surveillance authority — BMAS and the Länder in Germany, DGCCRF in France, OACIAP in Spain, ANPC in Romania, and so on. Enforcement starts with consumer complaints, escalates to investigations, and can result in administrative fines, orders to fix within a deadline, and (in severe cases) removal of the service from the market. Private lawsuits for accessibility violations exist in some member states but are not the primary mechanism.

Penalties

Both regimes can be expensive — but the shape of the cost differs.

ADA:first-offense civil penalties up to USD 75,000, up to USD 150,000 for repeat offenses. Private settlements average USD 25,000 to USD 75,000 including attorneys' fees; high-profile cases (Domino's, Target) ran to millions. The bulk of cost is settlement and legal fees, not statutory penalties.

EAA (national transpositions): vary by country. Germany (BFSG): up to 100,000 € per violation. France: up to 4% of worldwide turnover for aggravated infractions. Spain: 601 € up to 1M+ €. Romania: percentage-based penalties proportional to turnover. Most regulators signal remediation orders before fines, but reputational damage from a public complaint often exceeds any direct penalty.

Side-by-side comparison

Practical takeaways

When briefing a US client on why their existing ADA program does not cover their EU exposure, keep it concrete:

1. The web content bar is the same. Both regimes land on WCAG 2.1 Level AA for web content. If your client has an ADA program hitting WCAG 2.1 AA, that work carries over. What does not carry over is the documentation, non-web-content provisions, and country-specific enforcement preparation.
2. The EAA is explicit, the ADA is inferred. US clients often debate whether their site is "covered" by the ADA. The EAA removes that ambiguity — if they sell to EU consumers in one of the named service categories, they are covered from June 28, 2025.
3. Enforcement cadence is different. In the US, a serial plaintiff sues and the client settles. In the EU, a regulator issues an order to fix within a deadline, with fines for failure. EU remediation windows are shorter and more technical; "we'll fix it at the next release" does not work the same way.
4. The EU requires documentation. Member states expect a conformity statement and a technical file demonstrating that EN 301 549 was used. An "Accessibility Statement" page on the US site is not sufficient. French Article 47 sites need three documents (déclaration d'accessibilité, schéma pluriannuel, annual plan). Spanish public sites need a periodic review. Your audit findings feed all of this — they are the source of truth for what goes into those documents.
5. Non-EU sellers are in scope. The EAA does not care where the company is incorporated — it covers services placed on the EU market. US brands selling to EU consumers need an EU compliance posture, full stop.

For detail on specific national transpositions, see our country pages: Germany (BFSG), France (RGAA + Article 47), Spain (Ley 11/2023), and Romania (Law 232/2022). For the EU-wide framework, see the European Accessibility Act overview.