A serial ADA plaintiff is a person who files large numbers of website-accessibility lawsuits — sometimes hundreds a year — usually working with a handful of plaintiff-side law firms. The barriers cited are generally real, but the volume and repeatable pattern are what make these filings a distinct phenomenon for small businesses.
How the serial-plaintiff model works
Most ADA web lawsuits are brought under ADA Title III, which prohibits discrimination by “places of public accommodation.” Courts in many jurisdictions treat business websites as covered, even though the ADA itself predates the modern web and the DOJ has not issued binding private-sector web regulations. That legal gray area, combined with a clear technical standard most sites fail — WCAG 2.1 AA — created the conditions for high-volume litigation.
The mechanics are straightforward:
- A small number of law firms specialize in these claims and partner with a few repeat plaintiffs, often people who genuinely use a screen reader such as NVDA, JAWS, or VoiceOver.
- The plaintiff (or a tester working with the firm) visits a site and documents barriers that block a real task — buying a product, booking a table, filling out a contact form.
- The firm sends a demand letter or files a lawsuit, usually seeking injunctive relief (fix the site) plus attorney’s fees, and in some states statutory damages.
- Most cases settle quickly because litigating is more expensive than paying — which is exactly what makes the model scalable.
People call these operations “ADA lawsuit mills” because the same firms file near-identical complaints against hundreds of defendants. Thousands of ADA web-access lawsuits are filed in the U.S. each year, with filings heavily concentrated in a few states. This is not legal advice — it is a description of a documented pattern.
Why small businesses are the easy target
Serial filers go where the effort-to-reward ratio is best, and small businesses sit in the sweet spot. Here is why SMBs get hit so often.
| Factor | Why it makes you a target |
|---|---|
| Common CMS templates | Off-the-shelf themes ship the same defects to thousands of sites |
| No prior remediation | Barriers are obvious to an automated scan in seconds |
| Limited legal budget | Settling is cheaper than fighting, so cases close fast |
| Public-facing transactions | Carts, booking, and forms are easy to show as “blocked tasks” |
| No accessibility statement | Signals the site was never reviewed |
The CMS point is the big one. A typical WordPress, Shopify, Wix, or Squarespace site, set up from a template and never remediated, will fail the same handful of checks every time:
- Images with missing or useless alt text (WCAG 1.1.1).
- Form fields without programmatic labels (WCAG 1.3.1, 4.1.2).
- Insufficient color contrast on buttons and body text (WCAG 1.4.3).
- Content that can’t be reached or operated with keyboard navigation alone (WCAG 2.1.1).
- Missing or broken ARIA roles and labels that confuse assistive technology.
Because these failures are nearly universal across un-remediated template sites, a filer can scan dozens of businesses in an afternoon and find provable barriers on almost all of them. You’re not being singled out for who you are — you’re being selected by what your code does.
What actually makes a site a target
A few concrete signals push a site to the top of the list:
- Demonstrable, automatable failures. If a free tool flags missing alt text and unlabeled forms, so will a plaintiff’s tester. These map to specific WCAG success criteria, which makes them easy to cite in a complaint.
- A blocked transaction. Sites where a user with a disability can’t complete a core action — checkout, scheduling, account signup — are the strongest cases.
- An accessibility overlay. This surprises people: installing an overlay widget (accessiBe, UserWay, AudioEye, and similar) does not make you safer. Plaintiffs and their experts now specifically test overlay sites, document that the underlying barriers remain, and sometimes name the overlay in the complaint. An overlay is a JavaScript layer that can’t fix invalid HTML, missing labels, or a broken focus order — so the overlay fails the exact tests it claims to pass.
- No evidence of effort. No accessibility statement, no VPAT, no audit history — nothing showing the business takes access seriously.
The throughline is that automated detectability is what gets you noticed. The same scan that a plaintiff runs is the same scan you can run on yourself first.
How to stop being an easy mark
There is exactly one durable defense, and it is not a legal trick — it’s making the site genuinely usable. Conforming to WCAG 2.1 AA removes the barriers a plaintiff would cite, which removes the case before it starts. The POUR principles — Perceivable, Operable, Understandable, Robust — are the framework standards bodies like the W3C/WAI and WebAIM use to organize that work, and Level AA is the conformance target courts and the Section 508 program both reference.
Here is the honest hierarchy of responses:
- Do nothing. You stay on every scan list and remain an efficient target.
- Install an overlay. You spend money, add a plaintiff flag, and the real barriers stay put.
- Remediate by hand. A human-led accessibility audit finds every barrier — including the ones automated tools miss, which is most of them — and manual remediation fixes them in the actual code. That’s what holds up to a screen-reader tester and a court.
Curbcut does the third one only. We’re explicitly anti-overlay: we believe the only thing that protects an SMB is a site that a person using assistive technology can genuinely operate. If you want to see what a serial plaintiff would see on your site today, run a free accessibility scan, then let us remediate the real barriers by hand.
If you’ve already received a demand letter, don’t ignore it and don’t reply impulsively — read the guide and talk to a qualified attorney. This page is general information about how serial ADA litigation works, not legal advice about your specific situation.