Skip to content
wcagc
Create account
←Back to blog
ADATitle IIIlawsuits

Accessibility lawsuit trends in 2026: what the data shows

What the 2026 filing data shows: the UsableNet and Seyfarth counts, who is actually getting sued, and what lowers your accessibility risk.

P

Pavel Charkasau

Updated:

Website accessibility filings are running ahead of last year. UsableNet recorded 432 new ADA web accessibility lawsuits in August 2026 alone, and its midyear report projects about 6,176 for the full year, close to 20% above the 4,928 filed in 2025 (UsableNet tracker, UsableNet midyear). The federal-only picture from Seyfarth: 3,117 website accessibility suits in 2025, up 27% from 2,452 the year before (Seyfarth ADA Title III). Four in five filings name e-commerce sites, most defendants report under $50M in revenue, and roughly a quarter have been sued over this before. Sites already running an accessibility overlay are still being sued: 134 of August's 432 defendants had a widget installed when the complaint arrived. That last number is the one worth sitting with. Below is what each tracker counts, why their totals differ, where the filings concentrate, and what lowers your risk under the ADA. Short version: a scan plus human review of the journeys people actually use does more for you than any widget.

How many accessibility lawsuits have been filed in 2026?

Start with the cleanest recent month. UsableNet's tracker recorded 432 new ADA web accessibility lawsuits in August 2026 (UsableNet tracker). Its midyear report, published July 8, projects roughly 6,176 filings for the full year, nearly 20% more than 2025 (UsableNet midyear). A follow-up analysis at the end of July put the range wider, at approximately 6,000 suits and a 20 to 25% rise (UsableNet, five trends). The spread between them is a useful reminder that a projection made in July is a projection, not a count.

The federal baseline for 2025 is firmer. Seyfarth reviewed federal dockets and found 3,117 website accessibility lawsuits, a 27% jump from 2,452 in 2024, making up 36% of all federal ADA Title III filings that year out of 8,667 total cases (Seyfarth). Monthly volume ran between 219 in June and 319 in July. This is a steady stream, not a seasonal spike.

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 only. UsableNet's 4,928 for the same year is larger because it also pulls website suits filed in state courts, mainly New York and California, where a large share of these cases land. The two figures are not in conflict. They are two different nets over an overlapping pond. When you see a headline number that doesn't match another one, check whether it is federal-only or federal-plus-state before deciding someone got it wrong.

That distinction is getting more load-bearing, not less. Seyfarth reports that in New York more cases are moving to state court, most likely because federal judges are scrutinizing the standing of serial plaintiffs and applying a rigorous standard (Seyfarth, 2026 outlook). A federal-only tracker will show that shift as a decline that isn't really there.

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

Who is actually getting sued?

Not the household-name retailers you might expect.

  • 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 midyear). 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, 22% fall between $50M and $1B, and 10% clear $1B (UsableNet midyear). The number I keep coming back to is that first one. The defendants are mostly businesses least likely to have ever run an accessibility scan, not the ones with a compliance team.
  • The same companies, twice. About a quarter of digital accessibility lawsuits name a company that already faced a similar claim (UsableNet, five trends). August bears that out: 108 of the month's 432 defendants had been sued before (UsableNet tracker). A settlement that doesn't change the code leaves the same barriers in place for the next person to find.

Geography is the fourth pattern, and it moved this year. In federal court in 2025, New York led with 1,021 filings, 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). In 2026 UsableNet describes Illinois as one of the fastest-growing jurisdictions, alongside the established activity in New York, California and Florida (UsableNet, five trends). Where a suit gets filed is a venue choice, not a map of where inaccessible sites are.

Who is filing all these cases?

A small group. UsableNet estimates that roughly 20 to 25 plaintiffs, working with a relatively small set of law firms, bring most digital accessibility lawsuits, and that the 10 most active plaintiff firms account for about 84% of filings (UsableNet, five trends). That concentration explains the template quality of the complaints. They tend to name the same machine-detectable barriers, because those are the ones you can document from outside the login wall: unlabeled form fields, missing image alternatives, empty links.

The pool of filers is also widening at the edges. Seyfarth notes more self-represented litigants bringing cases with the help of AI (Seyfarth, 2026 outlook). Someone who once needed a firm to draft a complaint can now produce a serviceable one, which lowers the cost of filing. We covered that shift separately in AI-drafted ADA complaints.

UsableNet also estimates businesses receive roughly two to three times as many demand letters as filed lawsuits (UsableNet, five trends). Filing counts understate how often this lands in someone's inbox.

Do accessibility overlays reduce lawsuit risk?

The data says no, and so does the regulator. UsableNet's midyear 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 midyear). About 20% of sued companies had an overlay installed, by its July estimate; in the August tracker data the figure was 134 of 432 defendants (UsableNet, five trends, UsableNet tracker). The reason is simple. An overlay sits on top of your markup at runtime and cannot rewrite the underlying code a screen reader reads.

There is an enforcement marker here too. In January 2025 the FTC ordered overlay vendor accessiBe to pay $1 million over marketing claims that its accessWidget product would make websites comply with WCAG (FTC). Overlays don't fix code, and we built the opposite on purpose. If you're weighing one, do overlays actually reduce lawsuit risk goes deeper on the evidence, and 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, and finish the job. Save your scan reports and remediation notes. Given that a quarter of defendants are repeat defendants, the part that matters is closing the findings rather than filing the report.

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 have been filed in 2026?

UsableNet recorded 432 new ADA web accessibility lawsuits in August 2026 and projects about 6,176 for the full year, close to 20% above the 4,928 filed in 2025 (UsableNet tracker, UsableNet midyear).

How many 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 and 36% of all federal ADA Title III filings (Seyfarth). UsableNet's count of 4,928 is higher because it includes state-court cases.

Which industries and companies get sued the most?

E-commerce, by a wide margin. UsableNet reports 79% of 2026 filings name online stores, and 68% of defendants report under $50M in annual revenue (UsableNet midyear).

Do accessibility overlays protect against lawsuits?

No. UsableNet found a widget is not a meaningful deterrent, and 134 of the 432 defendants sued in August 2026 had one installed (UsableNet tracker). In 2025 the FTC ordered overlay vendor accessiBe to pay $1 million over claims its product would make sites comply with WCAG (FTC).

Can a company be sued twice over the same website?

Yes. About a quarter of digital accessibility lawsuits name a company that already faced a similar claim (UsableNet, five trends). Settling without changing the underlying code leaves the same barriers for the next plaintiff to find.

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, most defendants are smaller businesses that never scanned, and a quarter of them are being sued for the second time. A scan won't make you immune to a complaint, but it shows 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 filing trackers so you can plan around what the data actually says, not the scare headlines about it.

Last updated: September 15, 2026

Sources