ADA, EAA, WCAG: Practical Compliance Comparison

ADA, EAA, and WCAG are three related but distinct frameworks for digital accessibility: the ADA is a US civil rights law, the EAA is an EU directive, and WCAG is the technical standard both rely on. In practice, complying with WCAG 2.1 AA is the most direct way to satisfy both the ADA and the EAA, but the legal obligations, enforcement bodies, and timelines differ significantly. This article compares the three so you can plan your accessibility work with clarity.

What Each Acronym Actually Means

ADA (Americans with Disabilities Act) is a US federal civil rights law passed in 1990. Title III covers places of public accommodation (businesses, schools, transit, etc.) and requires “reasonable modifications” to ensure equal access. Since the late 2010s, courts have consistently ruled that websites and mobile apps fall under Title III, making digital accessibility a legal requirement for most US businesses.

EAA (European Accessibility Act) is an EU directive (2019/882) that must be transposed into national law by each member state. It applies to products and services like e-commerce, banking, e-books, and transport, and it explicitly references WCAG 2.1 AA as the technical benchmark for web content. The enforcement date is June 28, 2025, after which member states can impose penalties for non-compliance.

WCAG (Web Content Accessibility Guidelines) is a technical standard published by the W3C, not a law. It defines success criteria at three levels (A, AA, AAA). Most regulations reference WCAG 2.1 AA as the minimum bar. WCAG 2.2 was released in October 2023, but the EAA still cites 2.1; many organisations are adopting 2.2 AA proactively.

How the Laws Use WCAG

The ADA does not explicitly name WCAG, but the Department of Justice has repeatedly cited WCAG 2.0 AA and 2.1 AA as the de facto standard in settlement agreements. Courts have also used WCAG as evidence of whether a site is “accessible” under the ADA. The EAA, by contrast, explicitly requires that web content meet WCAG 2.1 Level AA (with some limited exceptions for live media and maps).

So the practical answer is simple: if you meet WCAG 2.1 AA, you are very likely to be compliant with both the ADA (as interpreted) and the EAA. The differences lie in who enforces them, what penalties you face, and how you prove compliance.

Key Differences at a Glance

• Geography: ADA applies to the US (and its territories); EAA applies to EU member states. WCAG is global.
• Legal status: ADA is a law with private right of action (individuals can sue); EAA is a directive that must be transposed into national law; WCAG is a technical standard.
• Scope: ADA covers “public accommodations” (broadly, most private businesses open to the public); EAA covers specific product/service categories (e-commerce, banking, e-books, etc.).
• Enforcement: ADA is enforced via civil lawsuits and DOJ complaints; EAA is enforced by national authorities (e.g., the Equality and Human Rights Commission in the UK, or the Barrierefreiheitsstärkungsgesetz in Germany).
• Timeline: ADA has no fixed deadline—compliance is ongoing; EAA has a hard deadline of June 28, 2025, for most products and services.
• Penalties: ADA allows for injunctive relief and attorney’s fees; EAA penalties vary by member state but can include fines and orders to fix the issue.

Practical Steps to Achieve Compliance

1. Audit your current site against WCAG 2.1 AA using automated tools (e.g., axe, Lighthouse) and manual testing with screen readers (NVDA, VoiceOver).
2. Fix the most common issues first: missing alt text, low contrast, missing form labels, and lack of keyboard navigation.
3. Create an accessibility statement that lists known issues and a timeline for fixes—this is required by the EAA and recommended by the ADA.
4. Train your developers and content editors on WCAG principles (Perceivable, Operable, Understandable, Robust).
5. Plan for ongoing testing—accessibility is not a one-time project; new content must be checked.
6. Document everything—keep records of audits, fixes, and testing dates. This is crucial for EAA enforcement and useful in ADA lawsuits.

Common Misconceptions

“WCAG is a law.” It is not. WCAG is a technical standard. Laws like the ADA and EAA reference it, but WCAG itself has no enforcement mechanism.

“If I have an accessibility overlay, I’m compliant.” Overlays (widgets that claim to fix accessibility) do not automatically make a site WCAG-compliant. They can help with some issues, but they often fail to address complex problems like ARIA misuse, and some overlays actually introduce new barriers. Manual testing is still required.

“ADA compliance is only for government sites.” No. Title III of the ADA applies to private businesses open to the public—that includes most commercial websites. Government sites fall under Title II, but the requirement is similar.

“The EAA only applies to EU-based companies.” The EAA applies to products and services sold in the EU, regardless of where the company is headquartered. If you sell to EU customers, you likely need to comply.

How to Choose What to Follow

If you operate only in the US, focus on ADA compliance by meeting WCAG 2.1 AA. If you operate in the EU (or sell to EU customers), you must comply with the EAA, which also points to WCAG 2.1 AA. If you operate globally, the safest approach is to meet WCAG 2.2 AA, which is backward-compatible with 2.1 and adds new criteria like focus appearance and accessible authentication.

In practice, the difference between 2.1 and 2.2 is small for most sites. The new criteria in 2.2 are mostly about focus visibility and dragging movements. Upgrading to 2.2 AA is a low-effort way to future-proof your compliance.

Costs and Resources

The cost of accessibility work varies widely. A small site with basic issues might be fixed in a few days by a developer familiar with WCAG. A large e-commerce platform could take months and require external consultants. Typical costs include:

• Automated audit tools: free to a few hundred dollars per month.
• Manual audit by a specialist: $2,000–$10,000 depending on site size.
• Developer time to fix issues: $50–$150 per hour.
• Ongoing testing and maintenance: often 5–10% of development budget.

But the cost of non-compliance can be higher. ADA lawsuits can result in six-figure settlements plus attorney fees. EAA penalties vary by country but can also be substantial. Investing in accessibility early is almost always cheaper than reacting to a lawsuit or enforcement action.

Frequently Asked Questions

Is WCAG 2.1 AA the same as ADA compliance? Not exactly, but it is the closest thing to a safe harbour. The ADA does not specify a technical standard, but courts and the DOJ treat WCAG 2.1 AA as the benchmark. Meeting it dramatically reduces legal risk.

Does the EAA apply to my small business? The EAA has exemptions for micro-enterprises (fewer than 10 employees and annual turnover under €2 million) for some provisions, but not all. If you provide e-commerce services, you are likely covered regardless of size.

What is the difference between WCAG 2.1 and 2.2? WCAG 2.2 adds nine new success criteria, including focus not obscured (2.4.11), dragging movements (2.5.7), and accessible authentication (3.3.8). Most are Level AA and are relatively easy to implement.

Can I be sued under the ADA if my site is not WCAG-compliant? Yes. Thousands of ADA website lawsuits are filed each year, and most are settled. The absence of a specific DOJ rule does not protect you; courts have consistently ruled that websites are places of public accommodation.

Do I need to comply with both ADA and EAA if I sell to both US and EU customers? Yes. They are separate legal requirements, but since both point to WCAG 2.1 AA, you can satisfy both with the same effort. Just be aware of the different enforcement mechanisms and documentation requirements.

What is the fastest way to become compliant? There is no shortcut. Start with an automated audit to find low-hanging fruit, then do a manual audit with a screen reader. Fix issues in order of severity (e.g., keyboard traps, missing alt text, contrast). Use a professional if your site is complex.

Related

• Math Word Problem Solver: How It Works
• Math Word Problem Solver Free No Sign Up
• 2nd Grade Math Word Problem Solver

in t | Finish time | min | 50 | 0
in d | Distance | km | 10 | 0
out pace | Average pace | min/km | t / d | 2
out speed | Average speed | km/h | d / (t / 60) | 2