A website accessibility lawsuit is a legal claim — almost always under ADA Title III — that a business website is inaccessible to people with disabilities and therefore discriminatory. Thousands are filed in U.S. courts each year, most against small businesses, and the standard courts use to judge accessibility is WCAG 2.1 AA.

How big is the ADA website lawsuit problem?

ADA web accessibility filings have grown into one of the most active areas of consumer litigation in the United States. Industry trackers have counted thousands of website accessibility lawsuits filed in federal and state court each year, and that figure does not include the far larger volume of demand letters that settle quietly before any case is filed.

A few things make the trend matter for ordinary business owners:

  • The volume is steady and high. Filings have stayed in the thousands annually for several years running, concentrated in a handful of plaintiff-friendly jurisdictions (New York, Florida, and California lead).
  • Most defendants are small. This is not a Fortune 500 problem. The typical defendant is a local retailer, restaurant, clinic, law firm, or independent ecommerce brand.
  • Repeat filers drive much of it. A relatively small number of serial plaintiffs and a handful of law firms account for a large share of all filings.
  • Overlays didn’t fix it. Cases naming businesses that had installed accessibility overlay widgets have appeared in the hundreds in recent years — a sign the widgets don’t deliver the protection they advertise.

If your website is how customers find, contact, or buy from you, it is exactly the kind of “public accommodation” plaintiffs target.

Why websites get sued under the ADA

The legal theory is straightforward. ADA Title III prohibits discrimination by “places of public accommodation.” Federal courts have repeatedly applied that language to business websites, and the Department of Justice (DOJ) has affirmed that the ADA covers the web (ada.gov). When a website can’t be used by someone relying on assistive technology, plaintiffs argue that’s the digital equivalent of a store with no wheelchair ramp.

There is no separate federal regulation that spells out WCAG for private businesses yet — but that gap is exactly why litigation, rather than regulation, has become the enforcement mechanism. For the full legal background, see our explainer on ADA Title III and websites, and how the ADA relates to Section 508 and WCAG.

In practice, complaints almost always reference failures against WCAG 2.1 Level AA — the conformance level the courts treat as the working standard. Common allegations include:

Barrier allegedWhat it meansWCAG area
Missing alt textImages convey information a screen reader can’t readPerceivable
Poor color contrastLow-vision users can’t read text against its backgroundPerceivable
No keyboard navigationUsers who can’t use a mouse get stuck or trappedOperable
Unlabeled forms / ARIA errorsScreen readers can’t identify fields or controlsRobust
Broken focus orderTab order jumps around or hides the user’s locationOperable

These map to the four POUR principles — Perceivable, Operable, Understandable, Robust — that organize all of WCAG. Most lawsuits are not about exotic edge cases; they’re about basic, fixable issues that a proper audit surfaces in hours.

Who actually gets sued

The myth is that ADA web lawsuits hit big, careless corporations. The reality is the opposite.

  • Small and mid-sized businesses make up the bulk of defendants. A site doesn’t need high traffic to attract a filing — it needs an accessibility barrier and a plaintiff who finds it.
  • Ecommerce is heavily targeted because checkout flows are full of forms, dynamic content, and interactive widgets that break for assistive technology. (See ADA compliance for ecommerce.)
  • Service businesses with booking or contact functions — restaurants, healthcare practices, law firms, real estate, hotels — are frequent targets because the inaccessible task is obvious and central.
  • Repeat defendants exist too. Businesses that “fix” a complaint with an overlay or a partial patch often get sued again, sometimes by a different plaintiff, because the underlying code never changed.

The common thread: the lawsuit isn’t really about the business’s size or intent. It’s about whether a real person using a screen reader (NVDA, JAWS, or VoiceOver) or a keyboard can complete a meaningful task. If they can’t, the claim has legs.

Demand letters vs. lawsuits

Most businesses encounter the problem first as a demand letter, not a court summons. Understanding the difference matters.

A demand letter is a pre-litigation notice, usually from a plaintiff’s attorney, asserting that your site is inaccessible and inviting you to settle — typically by paying a sum and agreeing to remediate. It is not a court filing. You generally have a little breathing room, but ignoring it is risky: it often precedes an actual lawsuit.

A lawsuit (complaint) is a formal filing in federal or state court. Once served, you face deadlines to respond, and the cost and complexity rise sharply.

What both have in common: the fastest, cheapest path through either is usually to make the site genuinely conform to WCAG 2.1 AA, because a remediated site removes the underlying claim and strengthens any settlement position.

If a letter has already landed, don’t improvise — read what to do if you got an ADA demand letter first, then talk to an attorney.

This page is general information, not legal advice. If you’ve received a demand letter or been served, consult a qualified ADA defense attorney about your specific situation.

What these cases cost

Costs fall into three buckets, and the third is the one businesses forget:

  1. Settlement / damages. Many small-business cases resolve for a few thousand to low tens of thousands of dollars. Statutory damages vary by state — California’s Unruh Act, for example, adds per-violation damages that raise the stakes considerably.
  2. Legal fees. Plaintiffs’ attorneys typically seek their fees as part of any settlement, and your own defense counsel adds cost on top.
  3. The remediation you needed anyway. Settling does not make your site accessible. You still have to fix the code — and settlement agreements often require it on a deadline, with monitoring.

The uncomfortable math: paying to settle and then paying to remediate is almost always more expensive than remediating proactively. See the detailed ADA lawsuit settlements and costs breakdown, or our general ADA compliance cost guide.

Serial plaintiffs and how this litigation works

A defining feature of this landscape is the serial plaintiff — an individual (often genuinely disabled) who, with a small set of law firms, files dozens or hundreds of accessibility cases. This pattern explains the sheer volume: a single browsing session can surface many non-compliant sites, and each is a potential filing.

It’s tempting to dismiss these as “shakedowns,” but two things are worth holding at once: some filings are opportunistic, and the barriers they cite are usually real. A site that fully conforms to WCAG 2.1 AA gives a serial plaintiff far less to work with. Learn how this engine operates in serial ADA plaintiffs.

Why overlays make you a target, not a shield

Accessibility overlays — the pop-up toolbars and “accessibility widgets” sold as one-line fixes — are the single biggest false sense of security in this space. They inject a script that layers options on top of your site, but they do not repair the underlying HTML, ARIA, labels, contrast, or focus order that screen readers and keyboards actually depend on.

The consequences are well documented:

  • Businesses running overlays still get sued — overlay-related cases have numbered in the hundreds in recent years.
  • Many screen reader users actively distrust overlays, and some disable them on sight.
  • Courts have not treated overlays as a defense. An overlay is not evidence of conformance.

The durable answer is manual remediation: a human fixing the semantic structure, labels, contrast, keyboard operability, and forms in the code itself, verified with real assistive technology. For the evidence, see why overlays don’t work and overlay vs. manual remediation.

How to lower your lawsuit risk

There’s no way to make any business legally untouchable, but you can move from “easy target” to “hard target” — and remove the underlying violations entirely. The reliable sequence:

  1. Audit against WCAG 2.1 AA. Combine automated scanning with manual testing — actually operating the site with a screen reader and keyboard. Automated tools alone catch only an estimated 30–40% of real issues. Start with a website accessibility audit.
  2. Remediate the code. Fix the findings at the source through manual accessibility remediation — not an overlay.
  3. Document conformance. Produce a VPAT / Accessibility Conformance Report and publish an accessibility statement so your good-faith effort is on record.
  4. Monitor for regressions. Sites change. Accessibility monitoring catches new barriers before a plaintiff does.

For the complete playbook, read how to avoid an ADA lawsuit. You can also sanity-check your current state with the question most owners start with: is my website ADA compliant?

The bottom line for business owners

ADA website lawsuits are common, they overwhelmingly hit small businesses, and they’re driven by a relatively small group of repeat filers and law firms. The barriers they cite are usually basic and fixable. Overlays don’t protect you; real conformance does. The cheapest moment to act is before a letter arrives.

If you want to know where you stand, run a free accessibility scan to see whether your site is currently a target — or talk to a human about a full audit and remediation plan.

Not legal advice. For guidance on a specific demand letter or lawsuit, consult a qualified ADA defense attorney.