Guide · updated September 2026 · sources linked

ADA website compliance in 2026, in plain English

If you run a business website in the US, the Americans with Disabilities Act applies to it — courts have treated websites as places of public accommodation for years, and the Department of Justice has said so explicitly. This guide covers what that means in practice: the real litigation numbers, the standard you're measured against, what a demand letter actually costs, and the order to fix things in that reduces risk fastest.

The numbers, honestly

Roughly 6,000 federal and state lawsuits over website and app accessibility are expected in 2026 — up 20–25% from 2025. Around 80% target e-commerce, because a store's checkout is easy to test and easy to explain to a judge. Filings concentrate in New York, California, Florida and Illinois, but defendants are sued where they sell, not where they're headquartered. About a quarter of defendants are repeat targets: settling once doesn't inoculate you. And roughly one in five companies sued already had an accessibility overlay widget installed when the complaint arrived.

The standard you're measured against

The ADA itself doesn't name a technical standard, but in practice everyone — DOJ settlements, plaintiff experts, courts — measures websites against the Web Content Accessibility Guidelines. WCAG 2.1 Level AA is the floor cited most often; WCAG 2.2 (published 2023) adds nine criteria that increasingly appear in expert reports, including visible focus requirements and redundant-entry rules for forms. If you're starting today, build to 2.2 AA and you're covered both ways.

What a demand letter actually costs

Typical pre-suit settlements run $5,000–$25,000; defending a filed case commonly costs $10,000–$50,000 before any settlement. The remediation you'd do afterward costs the same as doing it beforehand — you just also paid lawyers. If a letter has already arrived: don't ignore it, don't sign the first number, and start documented remediation immediately — the paper trail matters in negotiation. Our risk page estimates your exposure profile.

The fix order that actually reduces risk

Plaintiffs' testers run automated scanners first, so fix what scanners find, in this order:

1. Forms — missing labels, color-only error states, no autocomplete. The most-cited failure class, and it costs you real customers daily.
2. Keyboard paths — traps, invisible focus, skip links. Easy to test in a deposition; devastating when it fails there.
3. Images — missing or junk alt text on informative images.
4. Contrast — 4.5:1 for normal text, 3:1 for large text and UI components.
5. Motion and time — pausable carousels, no seizure-risk flashing, honoring reduced-motion preferences.

Then handle what scanners can't judge: whether alt text is meaningful, whether link text makes sense out of context, whether the cognitive load of a flow is reasonable. Anyone who claims software alone covers these is selling something — that's why our fix queue flags them for a human instead of auto-passing them.

The overlay question

A floating accessibility toolbar does not make you compliant, and the record now shows it clearly: the FTC fined the largest overlay vendor $1M in January 2025 over its compliance claims, overlays appear in demand letters as evidence rather than defense, and over 900 accessibility practitioners have asked site owners to remove them. The full record, cited, lives in our Theater Exhibit.

Don't forget the EAA

If you sell to EU customers, the European Accessibility Act has applied since June 28, 2025 — regardless of where your company sits. WCAG 2.1 AA is the working standard there too, so one honest remediation effort covers both regimes.

Sources: UsableNet lawsuit tracker & 2026 trends; FTC press release Jan 2025; Overlay Fact Sheet; W3C WCAG 2.2; EU Directive 2019/882. Educational content, not legal advice.