Repeat Defendants: What the 2025 Filing Numbers Say About Second Lawsuits
Federal website accessibility filings rose 27 percent in 2025 to 3,117, and a large share targeted companies sued before. Why remediation that stops at settlement keeps failing.
The number that should worry a store owner is not 3,117, the count of federal website accessibility lawsuits Seyfarth Shaw tracked for 2025, up 27 percent on 2024. It is the repeat share. UsableNet's tracking of the broader 2025 docket, more than 5,000 digital accessibility suits across federal and state courts, found at least 1,427 targeted companies that had already faced a claim.
A second lawsuit is rarely about a second exotic barrier. It is about the first remediation being scoped to a complaint's example pages instead of the templates that generated them. This post reads the filing data for what it says about how stores get sued twice, and what a monitoring habit does to that risk.
What the trackers actually count
Methodology matters before conclusions. Seyfarth Shaw counts federal court filings: 3,117 website cases in 2025, 36 percent of all federal ADA Title III filings, concentrated in New York, Florida, and Illinois. UsableNet counts wider: federal plus state filings and app claims, which is how its total passes 5,000. The two numbers describe overlapping dockets, not competing truths, and neither counts the demand letters that settle before anything is filed, which practitioners consistently say are the larger volume.
Ecommerce is the centre of the docket: analyses of the 2025 filings put online retail at roughly seven in ten digital accessibility suits, and most defendants are companies under $25 million in revenue. This is a small and mid-sized store problem, not a Fortune 500 problem.
How a settled case becomes a second case
The pattern runs like this. A complaint names a homepage, a product page, and a checkout barrier. The settlement funds fixes to those flows as they existed that quarter. The store then changes themes, adds a reviews widget, and swaps its chat tool. Eighteen months later the same barriers exist again in new components, and the second filing notes the first, which changes the tone of everything that follows.
Nothing in that story requires bad faith. It requires only that remediation was treated as a project with an end date instead of a property the site has to keep. Templates regress; third parties ship updates on their own schedules; the standard, WCAG 2.1 Level AA in most Title III practice, does not move nearly as fast as a storefront does.
What monitoring changes
A watch cadence does not need to be elaborate to break the pattern: a monthly scripted pass over the core templates for the barriers complaints actually cite, keyboard traps, missing names, contrast on text over images, form errors, plus a manual screen reader run over checkout each quarter. When a regression is found and fixed in the same month it shipped, the site a plaintiff's firm tests is a different site from the one that accumulates findings.
Related reading: Watching Live Chat Widgets for Keyboard Traps and Focus Loss, Watching Third Party Payment Buttons: Iframes, Titles, and Tab Order, Watching Autoplay Video Backgrounds and Their Pause Controls.
Frequently asked questions
How many website accessibility lawsuits were filed in 2025?
Seyfarth Shaw counted 3,117 filed in or removed to federal court in 2025, up 27 percent from 2,452 in 2024. UsableNet's wider count, including state courts and app claims, puts total digital accessibility suits above 5,000. The difference is scope, not disagreement.
Why do companies get sued a second time?
Usually because the first remediation fixed the pages named in the complaint while the underlying templates and third-party tools kept changing. New components reintroduce the same barriers, and a later filing finds them. Repeat defendants made up a large share of the 2025 federal docket.
Does having an accessibility widget prevent a lawsuit?
No. UsableNet reported that a substantial share of 2025 suits targeted sites with a widget installed, and widgets do not repair template-level barriers such as keyboard traps or missing form labels. Courts and plaintiffs test the underlying site, not the overlay's claims.
Which standard do Title III website cases use?
WCAG 2.1 Level AA is the de facto benchmark in federal Title III website litigation. WCAG 2.2 is the current W3C recommendation and a sensible development target, but settlements and court practice still reference 2.1 AA most often.