Skip to main content
Back to all posts

ADA Website Lawsuits: The Statistics Developers Need in 2026

Benjamin Morton

After two years of falling, ADA website lawsuits came roaring back. In 2025, plaintiffs filed 3,117 federal website accessibility lawsuits, a 27% jump on the 2,452 filed in 2024 (Seyfarth Shaw, 2026). Website cases now make up 36% of every federal ADA Title III filing, up from 28% a year earlier.

Here's what should interest you as a developer. A firm screening sites for a viable claim is not hand-testing your modal focus order; it's almost certainly running a scanner. So the barriers a screening scanner surfaces first are the ones worth closing first: missing alt text, unlabelled form inputs, low-contrast text. Those failures are cheap to find and cheap to fix, and most sites have left them sitting there. This post covers what the filing data actually says, what the legal standard actually is, and which failures to close first. It builds on our web accessibility compliance guide.

TL;DR: Federal website accessibility lawsuits rose 27% in 2025 to 3,117, or 36% of all ADA Title III filings (Seyfarth Shaw, 2026). There is still no ADA technical standard for private-sector sites; courts use WCAG 2.1 AA by convention. Six failure types cause 96% of all detected errors (WebAIM, 2026), and every one is machine-detectable, which makes them exactly what a screening scanner surfaces first.

How Many ADA Website Lawsuits Are Being Filed?

More than at any point since 2022. Federal website accessibility filings hit 3,117 in 2025, up 27% from 2,452 in 2024, reversing two consecutive years of decline (Seyfarth Shaw, 2026). Seyfarth builds that count by keyword-searching Courthouse News data and manually reviewing the hits, so read it as a floor rather than a ceiling.

Year

Federal website accessibility lawsuits

Change on prior year

2021

2,895

n/a

2022

3,255

+12%

2023

2,794

-14%

2024

2,452

-12%

2025

3,117

+27%

Source: Seyfarth Shaw, ADA Title III blog, March 2026. Federal court only.

Total federal Title III filings actually fell slightly in 2025, to 8,667 (Seyfarth Shaw, 2026). Website claims grew as a share of a shrinking pie, which tells you where the plaintiffs' bar is putting its energy.

Federal filings are also only part of the picture. Counting federal and key state courts together, UsableNet put 2025 above 5,000 digital accessibility lawsuits and projects roughly 6,176 for 2026 (UsableNet, 2026). Treat that projection carefully. UsableNet sells accessibility services, so it has a commercial interest in a big number, and its methodology is thinly documented. We're citing it because no independent tracker of state-court filings exists, not because it's beyond question. (For the avoidance of doubt: a11yFlow sells scanning software, so we have our own interest here too. Check the primary sources.)

Citation capsule: Federal website accessibility lawsuits rose 27% in 2025 to 3,117, the highest total since 2022, and accounted for 36% of all federal ADA Title III filings, up from 28% in 2024 (Seyfarth Shaw, 2026). Total federal Title III filings fell slightly to 8,667 over the same period, so website claims grew as a share of an overall shrinking caseload.

Why California Looks Safe in the Data (and Isn't)

Because the headline datasets only count federal court. Look at Seyfarth's 2025 state breakdown and California appears almost untouched, with 4 federal website suits. That is not a typo. California also had 3,252 total federal ADA Title III filings, more than any other state (Seyfarth Shaw, 2026).

State

Federal website suits (2025)

New York

1,021

Florida

961

Illinois

585

Minnesota

162

Pennsylvania

137

California

4

So where did California's web cases go? To state court. California's Unruh Civil Rights Act offers statutory damages with a $4,000 minimum plus attorney's fees, and federal court doesn't offer that. Plaintiffs file where the money is, and drop out of the federal statistics entirely.

Citation capsule: California recorded just 4 federal website accessibility lawsuits in 2025, against 1,021 in New York, despite having the most federal ADA Title III filings of any state at 3,252 (Seyfarth Shaw, 2026). The gap is an artefact of court selection: California web plaintiffs file in state court to claim Unruh Act statutory damages, which federal court cannot award, so they vanish from federal datasets.

Read a "which states sue most" chart built on federal data and you'd conclude your California-facing product is low risk. You'd have it backwards. The state with the strongest financial incentive to sue you is the one that looks emptiest, precisely because that incentive lives somewhere the chart can't see.

What Fails on Most Sites (and What a Screening Scanner Finds)

The boring stuff, overwhelmingly. In 2026, 95.9% of the top one million home pages had detected WCAG 2 failures, up from 94.8% a year earlier (WebAIM Million, 2026). That's the first rise after six straight years of small improvements. Average errors per page climbed 10.1%, to 56.1.

Six failure types account for 96% of all errors detected, and WebAIM reports they've been the same six for seven consecutive years (WebAIM Million, 2026).

Failure type

Home pages affected

WCAG criterion

Low contrast text

83.9%

1.4.3

Missing alternative text

53.1%

1.1.1

Missing form input labels

51.0%

3.3.2 / 4.1.2

Empty links

46.3%

2.4.4

Empty buttons

30.6%

4.1.2

Missing document language

13.5%

3.1.1

Source: WebAIM Million, March 2026. WAVE API against the Tranco top one million home pages, evaluating the rendered DOM.

Now the caveat, because this is where most articles on this topic quietly cheat. WebAIM measures what fails on home pages. It does not measure what gets cited in complaints, and no public dataset systematically codes which WCAG criteria ADA complaints actually plead. Anyone quoting you a precise percentage for "the most-litigated barriers" is inventing it.

What you can say, defensibly, is narrower and still useful. The failures easiest for a machine to find are the ones a plaintiff's firm can find at scale, cheaply, without ever opening your codebase. The overlap between "trivially detectable" and "plausibly pleadable" is the entire screening model. Every one of those six is machine-detectable, which puts them first in line.

Citation capsule: WebAIM's 2026 scan of the top one million home pages found 95.9% had detected WCAG 2 failures, up from 94.8% in 2025, the first increase after six years of improvement (WebAIM Million, 2026). Six machine-detectable failure types cause 96% of all errors: low-contrast text (83.9% of pages), missing alt text (53.1%), missing form labels (51.0%), empty links (46.3%), empty buttons (30.6%), and missing document language (13.5%).

Every one of those six is fixable in a sprint. Our guide to fixing the most common WCAG violations walks through each with code.

Does an Accessibility Widget Protect You? No.

It may actively work against you. Across 2024 and 2025, roughly a fifth to a quarter of all digital accessibility lawsuits targeted sites that already had an accessibility overlay or widget installed (UsableNet, 2025). Same caveat as before: UsableNet is a vendor, and this is a single-source claim. It's also consistent across two separate years of their reporting, and no one has published data contradicting it.

Complaints increasingly name the widget explicitly, alleging both that it failed to fix the underlying code-level barriers and that it introduced new ones by interfering with screen readers (UsableNet, 2026). The product sold as a legal shield is now being cited as evidence.

What we see: When a11yFlow scans a site running an overlay, the violations underneath are unchanged. The overlay adds a layer on top of the DOM; it doesn't repair the DOM. An empty button is still an empty button, and our scanner reports it exactly as it would on any other site. That's the same picture a plaintiff's screening scanner sees.

We've covered the mechanics in detail in why accessibility overlays fail. The short version: they're a JavaScript layer trying to infer intent it doesn't have access to.

What Does an ADA Website Lawsuit Actually Cost?

Nobody credibly knows, and you should be suspicious of anyone who says otherwise. Settlements are overwhelmingly confidential, so no public dataset with a real sample size exists. The tidy ranges quoted around the web ("$5,000 to $20,000 for a demand letter, $25,000 to $75,000 for a suit") trace back to vendor and law-firm marketing pages with no stated methodology, no sample size, and conspicuously round numbers. We went looking for a primary source behind them and couldn't find one.

Here are the numbers that are real, taken from court filings rather than sales decks.

The statutory floor. Under California's Unruh Act, statutory damages carry a minimum of $4,000, plus attorney's fees, and don't require proving actual harm (Cal. Civ. Code § 52(a)). One important nuance: damages attach per occasion on which a plaintiff was denied access, not per WCAG failure (Cal. Civ. Code § 55.56). You cannot multiply $4,000 by your error count, and any vendor implying otherwise is selling fear.

A real settlement. In Alcazar v. Fashion Nova (N.D. Cal.), the proposed class settlement put roughly $2.43M toward California class members, capped at $4,000 per household, and $2.52M toward plaintiffs' counsel (Seyfarth Shaw, 2026). Counsel's fee exceeded the class recovery.

The Department of Justice noticed. In February 2026 it filed a Statement of Interest opposing the settlement, arguing the injunctive relief wouldn't meaningfully improve accessibility, and writing that it opposed "using a civil claim principally to enrich class counsel on the backs of persons with disabilities" (as quoted by Seyfarth Shaw, 2026). DOJ also noted that class counsel had filed more than 500 similar cases between 2019 and 2023, and that the settlement administrator's own website was inaccessible to screen reader users.

Citation capsule: No reliable public data exists on ADA website lawsuit settlement costs, because settlements are almost always confidential; the ranges circulating online trace to vendor marketing with no stated methodology. What is verifiable: California's Unruh Act sets a $4,000 statutory damages minimum per occasion of denied access (Cal. Civ. Code §§ 52(a), 55.56), and the proposed Alcazar v. Fashion Nova settlement allocated $2.43M to the class against $2.52M for plaintiffs' counsel (Seyfarth Shaw, 2026).

None of which is a reason to shrug. The barriers are real, the users hitting them are real, and so is your exposure.

Is There Even a Legal Standard for Private Websites?

Officially, no. DOJ's web accessibility rule adopts WCAG 2.1 Level AA, but it applies to state and local government (Title II) only (ADA.gov, 2026). No equivalent technical standard has ever been issued for private-sector Title III websites. Courts have converged on WCAG 2.1 AA as the working benchmark anyway, and it's what consent decrees typically require, but that's judicial convention rather than regulation. You're being measured against a standard nobody formally imposed on you.

The government timeline also just moved. In an interim final rule published on 20 April 2026, four days before the original deadline, DOJ extended the Title II compliance dates by a year (ADA.gov, 2026).

Entity

Original deadline

Current deadline

State/local government, population 50,000+

24 April 2026

26 April 2027

Population under 50,000, and special districts

26 April 2027

26 April 2028

One nuance matters here. The extension delays only the WCAG 2.1 AA compliance dates. It doesn't suspend Title II's underlying nondiscrimination and effective-communication duties, which supported web accessibility claims for years before any technical standard existed. A delayed deadline is not a permission slip.

There are early signs courts are pushing back on the most aggressive plaintiffs. Two 2025 New York federal decisions found serial plaintiffs hadn't plausibly alleged an intent to return to the site, and one judge ordered an evidentiary hearing into standing on his own initiative (Seyfarth Shaw, 2025). Don't build a strategy on it. A standing defence only comes into play once you've already been sued, and it turns on facts about the plaintiff rather than anything about the state of your site.

What Developers Can Actually Do

Start with the six, because they cause 96% of detected errors and every one is machine-findable (WebAIM Million, 2026). You don't need a compliance programme to begin. You need a scanner in CI and one sprint.

1. Scan what you ship, not what you remember shipping. Run an automated scan across your highest-traffic templates: home, category, product, cart, checkout, contact. UsableNet's tracking puts e-commerce at roughly 70% of digital accessibility lawsuits in 2025 (UsableNet, 2026), with the same vendor caveat as before, and the checkout funnel is where a blocked user becomes a plaintiff with a story.

2. Fix the six, in order of prevalence. Colour contrast first. At 83.9% of pages it's the biggest single bucket, and it's usually a CSS token change rather than a refactor. Then alt text, form labels, empty links, empty buttons, document language. Our guide to fixing common WCAG violations has the code for each, and the WCAG 2.2 checklist covers the criteria behind them.

3. Gate the regression, don't just clear the backlog. A one-off remediation decays. Wire axe-core into your pipeline so a new violation fails the build, using our GitHub Actions guide. This is the step that stops you doing all of this again in eighteen months.

4. Treat automation as a floor. Scanners catch high-volume failures and miss the judgment calls entirely: keyboard traps, focus order, whether alt text is meaningful rather than merely present. We covered the split in automated vs manual accessibility testing. Automate the six; test the journeys by hand.

5. Don't buy the widget. Roughly a fifth to a quarter of lawsuits in 2024 and 2025 hit sites that already had one installed (UsableNet, 2025). It's an expense that fixes nothing and now shows up in complaints.

Selling into Europe as well? The European Accessibility Act applies alongside all of this, with its own enforcement regime. Our EAA developer guide covers what changes.

Frequently Asked Questions

How many ADA website lawsuits were filed in 2025?

Plaintiffs filed 3,117 federal website accessibility lawsuits in 2025, up 27% from 2,452 in 2024 and the highest total since 2022 (Seyfarth Shaw, 2026). Counting state courts too, UsableNet, an accessibility vendor, puts the total above 5,000. Website cases were 36% of all federal ADA Title III filings.

Does the ADA legally require WCAG compliance for private websites?

Not formally. DOJ's WCAG 2.1 AA rule covers state and local government (Title II) sites only (ADA.gov, 2026), and no technical standard has ever been issued for private-sector Title III websites. Courts have adopted WCAG 2.1 AA as the de facto benchmark, but that's judicial convention, not regulation.

Will an accessibility overlay or widget prevent a lawsuit?

No. Roughly a fifth to a quarter of digital accessibility lawsuits in 2024 and 2025 targeted sites that already had a widget installed (UsableNet, 2025). Complaints now name the widget directly, alleging it failed to fix code-level barriers and interfered with screen readers.

How much does an ADA website lawsuit cost to settle?

There's no reliable public figure, because settlements are almost always confidential and the ranges quoted online cite no methodology. What's verifiable: California's Unruh Act sets a $4,000 statutory minimum per occasion of denied access, and the proposed Alcazar v. Fashion Nova settlement allocated $2.43M to the class against $2.52M for counsel (Seyfarth Shaw, 2026).

Which accessibility issues should I fix first?

The six causing 96% of all detected errors: low-contrast text (on 83.9% of home pages), missing alt text (53.1%), missing form labels (51.0%), empty links (46.3%), empty buttons (30.6%), and missing document language (13.5%) (WebAIM Million, 2026). All six are automatically detectable, so start with a scan.

The Bottom Line

The 2025 data on ADA website lawsuits points one way. Filings rose 27% to 3,117 federal website cases, website claims grew to 36% of all Title III filings, and the underlying web got measurably worse, with detected WCAG failures rising to 95.9% of the top million home pages (Seyfarth Shaw, 2026; WebAIM Million, 2026). More suits, more broken pages.

The exposure is unusually tractable, though, and that's the real takeaway. Six machine-detectable failures cause 96% of errors. No widget closes them, and no delayed government deadline changes your position. Run a scan, fix the six, and gate the regression in CI so they don't come back. Start with the common WCAG violations guide for the fixes, the GitHub Actions guide for the pipeline, and the web accessibility compliance guide for the wider legal picture.

Sources

PreviousAutomated vs Manual Accessibility Testing: The Data
NextADA Title II Deadline Extended: What It Does Not Excuse