Skip to content
wcagc
←Back to blog
ADATitle IIIlawsuits

Accessibility lawsuit trends in 2026: what the data shows

Website accessibility lawsuits are on track for a record 2026. What the UsableNet and Seyfarth data shows and what actually lowers your risk.

P

Pavel Charkasau

Website accessibility lawsuits are heading for a record year. UsableNet's 2026 midyear report projects roughly 6,176 digital accessibility filings for the full year, close to a 20% rise on 2025 (UsableNet). The federal-court picture from Seyfarth backs the trend: 3,117 website accessibility suits in 2025, up 27% from 2,452 the year before (Seyfarth ADA Title III). Almost four in five suits target e-commerce, most defendants are businesses under $50M in revenue, and sites already running an accessibility overlay are still being sued. That last point is the one worth sitting with. Below is what the two main trackers actually counted, why their numbers differ, who is getting sued, and what lowers your risk under the ADA. Short version: a scan plus human review of your key journeys does more for you than any widget.

How many accessibility lawsuits were filed, and where are the numbers going?

Two organizations count these cases, and they count differently, so start with the cleaner federal set. Seyfarth reviewed federal court dockets and found 3,117 website accessibility lawsuits filed in 2025, a 27% jump from 2,452 in 2024 (Seyfarth ADA Title III). Those suits made up 36% of all federal ADA Title III filings that year, up from 28% in 2024 out of a total of 8,667 Title III cases. Filings ran between 219 in the slow month (June) and 319 in the busy one (July), so this is a steady stream, not a seasonal spike.

The 2026 trajectory points up. UsableNet's midyear report, published July 8, projects about 6,176 digital accessibility lawsuits for the full year, nearly 20% more than 2025 (UsableNet). One reason the count keeps climbing: the DOJ pushed back the ADA Title II deadlines for governments, but Title III, which covers private business, never had a dated web rule to move. Private-sector exposure did not change, and plaintiffs kept filing.

Why do UsableNet and Seyfarth report different numbers?

Because they count different courts. Seyfarth's 3,117 is federal court only. UsableNet's tally is larger because it also pulls website suits filed in state courts, mainly New York and California, where a big share of these cases actually land. So the 6,176 projection and the 3,117 figure are not in conflict; they are two different nets over an overlapping pond. If you see a headline number and it doesn't match another one, check whether it's federal-only or federal-plus-state before you decide someone got it wrong.

Both trackers also note the same limits. Docket searches key on accessibility-specific language, so a case filed without those keywords can slip through. Treat every count as a floor, not a census.

Who is actually getting sued?

Not the household-name retailers you might expect. Three patterns hold across the 2026 data.

  • E-commerce is the target. UsableNet reports that 79% of 2026 filings name online stores, with every other industry combined making up the remaining 21% (UsableNet). A cart, a product filter, and a checkout are exactly the interactive flows that break for keyboard and screen-reader users.
  • Small companies, not giants. 68% of sued businesses report under $50M in annual revenue (UsableNet). The number I keep coming back to is that one: the defendants are mostly the businesses least likely to have ever run an accessibility scan, not the ones with a compliance team.
  • A handful of states. In federal court, New York led with 1,021 filings in 2025, Florida had 961, and Illinois had 585, while California saw just 4, because California plaintiffs file under the state's Unruh Act in state court instead (Seyfarth ADA Title III). Where a suit is filed is a venue choice, not a map of where inaccessible sites are.

Why are so many suits filed without a lawyer?

A structural shift is behind part of the volume. Self-represented (pro se) plaintiffs filed 40% more federal ADA Title III and Fair Housing Act cases in 2025 than in 2024, a surge Seyfarth attributes largely to AI-assisted complaint drafting (Seyfarth ADA Title III). A person who once needed a firm to draft a complaint can now generate a serviceable one, which lowers the cost of filing and raises the count. Whatever you think of that, it means the pool of potential plaintiffs is wider than it was two years ago, and template complaints tend to name the same easy-to-detect barriers: unlabeled form fields and missing image alternatives.

Do accessibility overlays reduce lawsuit risk?

The data says no, and so does the regulator. UsableNet's report is blunt that suits against companies already running an accessibility widget keep rising, and that a widget "has not proven to be a meaningful deterrent, legally or practically" (UsableNet). The reason is simple: an overlay sits on top of your markup at runtime and cannot rewrite the underlying code that a screen reader reads.

There is also an enforcement marker here. In January 2025 the FTC ordered the overlay vendor accessiBe to pay $1 million over marketing claims that its accessWidget product would "automatically comply" with WCAG 2.1 AA; the Commission approved the order as final in April 2025 (FTC). Overlays don't fix code, and we built the opposite on purpose. If you're weighing one, accessiBe alternatives that fix code walks through the difference.

What actually lowers your legal risk?

Meeting the standard your remediation is measured against, and having evidence you're working at it. The ADA does not name a specific web regulation for private businesses, but courts and the DOJ both point to WCAG as the practical yardstick, so that is what to build toward (ADA.gov). A sane order of operations:

  1. Scan to get the map. Run your templates and key pages against WCAG 2.2 AA so you know the size and shape of the problem. Automation is fast at the machine-detectable barriers a template complaint tends to cite. Start with a free accessibility scan.
  2. Fix the paths people use. A checkout or a signup form that a keyboard user can't complete outranks a hundred decorative-image warnings. Triage by user impact, not issue count.
  3. Book the human review. Automated testing catches roughly 30 to 57% of issues depending on how you count (Deque). The rest, like whether an error message makes sense through a screen reader, needs a person. Federal contractors have the same reality under Section 508.
  4. Keep evidence. Save your scan reports and remediation notes. A documented, dated effort is what your counsel wants if a demand letter ever arrives, and it beats a widget that claims perfection.

No tool makes a site immune to a complaint, and anyone who tells you otherwise is selling the thing the FTC just fined. What a scan gives you is a ranked, specific list of what to fix first, with the exact selector for each finding. The WCAG checklist lays the criteria out by level if you want the working reference.

FAQ

How many website accessibility lawsuits were filed in 2025?

Seyfarth counted 3,117 website accessibility lawsuits in federal court in 2025, up 27% from 2,452 in 2024. That was 36% of all federal ADA Title III filings for the year (Seyfarth ADA Title III). State-court cases, which UsableNet also tracks, push the combined total higher.

Are accessibility lawsuits going up in 2026?

Yes. UsableNet's midyear report projects about 6,176 digital accessibility filings for the full year, close to a 20% increase over 2025 (UsableNet).

Which industries get sued the most?

E-commerce, by a wide margin. UsableNet reports 79% of 2026 filings name online stores, with all other industries combined at 21% (UsableNet).

Do accessibility overlays protect against lawsuits?

No. Suits against companies already using an overlay keep rising, and UsableNet found the widget is not a meaningful deterrent. In 2025 the FTC ordered overlay vendor accessiBe to pay $1 million over claims its product would automatically make sites compliant (FTC).

Does the ADA require a specific version of WCAG for private websites?

Not by regulation. There is no dated Title III web rule, but courts and the DOJ treat WCAG as the practical benchmark, so building toward WCAG 2.2 AA is the defensible target (ADA.gov).

See where your site stands

The filing numbers are rising, and most defendants are smaller businesses that never scanned. A scan won't make you immune to a complaint, but it shows you which WCAG issues are on your pages today, ranked so you fix the ones that block real users first. Run a free accessibility scan and you get the violation list with the exact selector for each finding.

Written by Pavel Charkasau, founder of wcagc.com. I read the 2026 midyear filings so you can plan around what the data actually says, not the scare headlines about it.

Last updated: July 22, 2026

Sources