Skip to main content

Raveka Technologies

ada_compliances

ADA vs EAA vs WCAG: The Complete 2026 Website Compliance Guide for US and European Businesses

ADA, EAA & WCAG: 2026 Website Compliance Guide

Website accessibility compliance means meeting legal requirements for people with disabilities. In the US, that’s the ADA. In the EU, it’s the European Accessibility Act (EAA). Both point back to the same technical standard: WCAG 2.1 Level AA.

If your business serves customers in the US, the EU, or both, your website is very likely already in scope. That’s true whether or not anyone on your team has looked into it yet.

2026 is the year this stopped being theoretical. ADA website lawsuits are on pace for a new US record. In the EU, regulators are now actively fining non-compliant businesses. This guide breaks down what each law requires, who it applies to, what non-compliance actually costs, and how to fix it.

The short version

  • ADA (USA): No single named technical standard for private businesses. But courts and settlements consistently point to WCAG 2.1 or 2.2 Level AA as the benchmark. Litigation risk drives this, not a filing deadline.
  • EAA (EU): A specific law with a specific enforcement date — June 28, 2025 — that’s already active. It applies to most businesses selling products or services to EU consumers, and it points to WCAG 2.1 AA through the EN 301 549 standard.
  • WCAG: The technical rulebook both laws point back to. WCAG is a W3C standard, not a law — the W3C itself uses the word “conformance,” not “compliance.” Meeting WCAG 2.1 AA is the strongest evidence you can have toward legal compliance. But it isn’t an automatic safe harbor. US courts still decide ADA cases one at a time, with no codified technical standard. And full EAA compliance includes obligations beyond web content itself, like accessibility statements and accessible PDFs.

ADA website compliance in the US

The Americans with Disabilities Act doesn’t mention websites by name. It was written in 1990, before the commercial web existed.

But courts have applied it anyway. Title III covers “places of public accommodation.” Since the Domino’s Pizza case reached the Supreme Court in 2019 — and the Court declined to hear Domino’s appeal — that’s consistently been read to include commercial websites.

Lawsuit volume is climbing

That precedent turned into a real litigation industry. Federal courts are on track for more than 5,500 ADA website lawsuits in 2026. That’s the highest total on record, and volume has climbed steadily since 2018.

E-commerce is the single biggest target. Nearly 70% of 2025’s web-related ADA lawsuits went after online stores. The trend is now spreading into healthcare portals, banking apps, and education platforms too. Florida overtook New York as the top state for filings in early 2026, though cases are spreading well past either state.

What it actually costs

This point gets misreported a lot, so it’s worth being precise.

Civil penalties up to $75,000 for a first violation, and $150,000 for repeat violations, do exist under Title III. But those are penalties the DOJ can seek in its own enforcement actions — not something an individual plaintiff collects. DOJ-initiated cases are rare.

In a private lawsuit, which is the overwhelming majority of ADA website cases, federal law only lets plaintiffs recover two things: injunctive relief (a court order to fix the site) and attorney’s fees. Not monetary damages.

Here’s what businesses actually pay:

  • ~95% of sued businesses settle rather than litigate
  • Demand-letter settlements typically run $1,000–$25,000
  • Average out-of-court settlement: around $25,000
  • Average court judgment: around $75,000, once legal costs are included

The real exposure is legal fees and settlement costs, not a fixed statutory fine. One exception: state laws can add real damages on top of federal law. California’s Unruh Civil Rights Act allows $4,000 per violation, and the plaintiff doesn’t have to prove harm.

Who’s actually getting sued

Not primarily large corporations with badly broken sites. Plaintiff firms use automated scanners to find common, fixable issues — missing alt text, unlabeled form fields, poor keyboard navigation — across huge numbers of ordinary small-business sites. Then they send near-identical demand letters at scale.

An otherwise well-run website with a handful of accessibility gaps is a completely normal lawsuit target.

Is there a government deadline?

Yes — but only for public entities, not most private businesses. And the date has moved.

The DOJ’s original 2024 rule set an April 2026 deadline for larger state and local government sites. But on April 20, 2026, the DOJ issued an Interim Final Rule that pushed both deadlines back by one year:

  • April 26, 2027: state and local government sites serving populations of 50,000+
  • April 26, 2028: smaller entities and special district governments

Private businesses have no equivalent statutory deadline at all. That doesn’t reduce your exposure, though — private-lawsuit risk comes from litigation volume year-round, not a filing date.

EAA website compliance in the EU

The European Accessibility Act is a different animal: a specific EU directive with a specific enforcement date that has already passed.

Full compliance and penalty enforcement began June 28, 2025. It applies broadly — e-commerce, banking, telecommunications, transport services, computers and smartphones, and audiovisual media are all named as covered sectors. And it applies to any business selling into the EU, including companies headquartered outside Europe. A US or UK business with EU customers is in scope.

The technical standard

The benchmark is EN 301 549, the harmonized European ICT accessibility standard. The current version incorporates WCAG 2.1 Level AA. A newer version incorporating WCAG 2.2 is in development, expected sometime in 2026 — but 2.1 AA remains the operative legal benchmark for now.

Enforcement is no longer theoretical

France saw its first EAA-related lawsuits filed in late 2025. Several major grocery retailers were hit with formal legal notices within weeks of the deadline passing. The Netherlands, Germany, Sweden, and Ireland are all running active market-surveillance programs into 2026. Each EU member state sets and enforces its own penalties:

Country Penalty range
France €75,000 – €300,000 per violation
Germany €10,000 – €100,000 per violation
Netherlands Up to €90,000
Sweden Up to roughly €900,000
Ireland Up to €60,000

Is there an exemption?

A narrower one than it’s often described as.

Under Article 4(5) of the EAA, microenterprises — fewer than 10 employees, under €2 million annual turnover or balance sheet — are exempt from accessibility requirements for the services they provide. This exemption is automatic. No application is needed. It’s calculated at the whole-company level, not per country.

But it does not cover products. A microenterprise that manufactures or sells covered physical products still has product-side obligations, just a lighter documentation requirement.

Larger businesses of any size can also invoke a separate “disproportionate burden” defense. It’s much narrower, though — it requires a documented self-assessment, not just an assertion, and carries a five-year record-keeping obligation. Most small-to-mid-sized service businesses above the microenterprise threshold are fully in scope.

ADA vs EAA at a glance

ADA (USA) EAA (EU)
Type of law Civil rights law applied via court precedent Directive with explicit digital accessibility rules
Named technical standard None officially — WCAG 2.1/2.2 AA is the de facto court benchmark WCAG 2.1 AA, via EN 301 549
Enforcement mechanism Private lawsuits and demand letters Government regulators in each member state
Deadline None for private businesses; government sites face 2027/2028 Already active — June 28, 2025
Typical penalty DOJ-only penalties of $75K–$150K (rare); private cases settle $1K–$25K + fees €10,000–€900,000+, depending on country
Who’s exempt No formal small-business exemption Microenterprises — services only, not products

What WCAG 2.1 AA actually requires

WCAG runs on four principles, often remembered as POUR: content must be Perceivable, Operable, Understandable, and Robust.

In practice, a short, fixable list of issues triggers most ADA lawsuits and EAA complaints:

  1. Missing or poor alt text on images, so screen readers can’t describe them
  2. Keyboard navigation gaps — menus, forms, or checkout flows that only work with a mouse
  3. Insufficient color contrast between text and background
  4. Unlabeled form fields, especially on checkout and contact forms
  5. Missing focus indicators for keyboard users
  6. Inaccessible PDFs and downloadable documents

Automated scanning tools only catch an estimated 30–40% of real WCAG violations. A clean automated scan isn’t proof of compliance. Manual testing with real assistive technology — screen readers, keyboard-only navigation — is needed to catch the rest.

That gap is exactly what “quick fix” accessibility overlay widgets fail to close. It’s a big part of why several high-profile overlay-only remediations have themselves ended up in litigation.

A practical compliance path

  1. Start with an audit, not a fix. You need to know your actual gaps — automated scan plus manual review — before spending money on remediation.
  2. Prioritize by user journey, not page count. Login, contact forms, and checkout flows carry the highest legal risk. Fix these first.
  3. Avoid overlay-only solutions. Widgets that claim instant compliance address a fraction of real issues, and have themselves become the basis of lawsuits and regulatory penalties.
  4. Document everything. Most EU member states now require a published accessibility statement. In the US, documented audits and a remediation plan strengthen your legal position if a demand letter arrives.
  5. Treat it as ongoing, not one-time. New pages, plugins, and content can reintroduce issues. Accessibility needs to sit in your regular QA process, not a one-off project.

If you’re rebuilding or upgrading a site anyway — say, during a WordPress 7.0 upgrade — that’s the cheapest point to bake WCAG fixes in, rather than retrofitting later.

FAQ

Does my small business really need to worry about this? Yes. Small e-commerce businesses are disproportionately targeted by ADA lawsuits. The EAA’s microenterprise exemption only covers service businesses under 10 employees and €2 million turnover — and even then, only the services side, not any physical products sold. Most established small businesses don’t qualify.

Is WCAG 2.1 or 2.2 the right target? WCAG 2.1 AA is the current legal benchmark for both ADA litigation patterns and the EAA’s EN 301 549 standard. Building to WCAG 2.2 AA is good practice and future-proofs you, since regulators on both sides of the Atlantic are moving toward it.

Can an accessibility overlay widget make my site compliant? No. Overlays typically catch only a fraction of real accessibility barriers, and don’t replace genuine code-level fixes. Several businesses using overlay-only solutions have still faced successful lawsuits.

Does this apply to me if I only sell online, with no physical store? Yes, for both laws. US courts have consistently applied the ADA to online-only businesses. The EAA explicitly covers e-commerce regardless of physical presence.


Raveka Technologies offers accessibility audits and WCAG remediation for WordPress, Squarespace, and WooCommerce websites serving clients across the USA, UK, and Europe. Get a compliance audit →

Leave a comment

Your email address will not be published. Required fields are marked *