ADA Website Lawsuits Are Up 27%. Yours Could Be Next.

An owner emails me after getting a letter from a law firm they've never heard of, naming a plaintiff they've never heard of, over a website that's been up for three years with zero complaints and a Google ranking they're proud of. Nothing about the site looked broken. It loaded fast, looked clean, converted fine. It just wasn't readable by someone using a screen reader, and that alone was enough to trigger a federal lawsuit.

That's not a hypothetical inbox. It's the exact mechanism behind one of the fastest-growing categories of website legal exposure a small business can have, and almost nothing else on this blog — rankings, citations, AI Overviews — moves the needle on it at all.

Quick, honest note before anything else: I build and manage websites. I'm not a lawyer, and nothing below is legal advice. This is the plain-English version of a real and growing legal risk, so you know what to ask about. For anything specific to your business, talk to an actual attorney.

What's actually happening here

Title III of the ADA bans discrimination in "places of public accommodation" — historically read as physical spaces like stores and restaurants. Most federal circuit courts that have ruled on the question have extended that to commercial websites, on the theory that a site with no way for a blind or low-vision visitor to use it is functionally the same as a store with no way in. The Department of Justice has stated informally for years that it considers websites covered, without ever issuing a formal regulation spelling out an exact technical standard for private businesses.

Into that gap, courts have converged on WCAG — the Web Content Accessibility Guidelines, maintained by the World Wide Web Consortium — as the practical yardstick, specifically version 2.1 or 2.2 at Level AA. That's not a law Congress passed; it's a technical standard that's become the de facto legal expectation because it's the thing plaintiffs' experts cite, defense experts cite, and settlement agreements name as the target.

What that standard actually covers, in plain terms: images need text alternatives so screen readers can describe them, forms need labels a screen reader can announce, navigation needs to work from a keyboard alone (not just a mouse), color contrast needs to be high enough to read, and video needs captions. None of it is exotic. Most of it is invisible if you're not the person relying on it — which is exactly why it goes unnoticed until a demand letter arrives.

Why this matters for a business your size

Here's the part that surprises people, the same way it surprised owners reading about the FTC's fake-review rule last month: there's no small-business carve-out. The lawsuit volume backs that up directly — e-commerce and retail sites made up roughly 70% of 2025's digital accessibility filings, per UsableNet's tracking, and that's a category dominated by small and mid-size operations running ordinary storefronts, not primarily Fortune 500 sites with in-house legal teams.

The financial shape of these cases follows a pattern. Accessibility compliance vendor Accessible.org, which tracks settlement outcomes, reports that a first-time settlement for a small business commonly lands in the $5,000–$20,000 range, layered with a mandated remediation window (often 90 to 180 days) and a period of ongoing monitoring — sometimes a year or more of documented scans proving the fixes stuck. The number that trips people up isn't the settlement check. It's that the monitoring and remediation commitment attached to it can end up costing more than the check itself, stretched out over the following year.

Being sued once doesn't clear you, either. Roughly 45% of 2025's federal filings targeted businesses that had already been sued before, per UsableNet — the same plaintiffs' firms filing repeat suits when an earlier fix wasn't thorough enough, or a new page shipped without the same care as the one that got fixed.

I ran a dog grooming salon for years before any of this, and I can tell you exactly how this slips through: nobody who builds or runs a small business site set out to exclude anyone. It's not a decision. It's a gap nobody was watching, on a part of the site nobody who could see the screen ever had a reason to test.

The mechanics: what to actually check

1. Run an automated scan first, but don't stop there. Free tools (WAVE, axe DevTools, Lighthouse's accessibility audit) catch missing alt text, unlabeled fields, and contrast failures in minutes — but they only catch roughly a third of WCAG success criteria, since "does this alt text actually make sense" needs a human judgment call.
2. Test keyboard-only navigation. Unplug the mouse and try to reach every link, button, and form field using only Tab and Enter. If you get stuck anywhere, so does anyone who can't use one.
3. Check image alt text for accuracy, not just presence. A scan confirms alt text exists. It won't catch "IMG_4821.jpg" or a description of the wrong photo — both count as failures.
4. Verify form labels and error messages. Every input needs a label a screen reader announces, and errors need to be tied to the field they describe, not just shown in red text nearby.
5. Caption video with a human pass. Auto-generated captions are a starting point, not a finish line.
6. Then treat it like every setting that drifts. A site that passes in January can fail in June after a new plugin or landing page ships without the same review.

What won't help

Installing an accessibility overlay widget and calling it done. This is the single most common shortcut, and it's the one plaintiffs' firms specifically look for. In April 2025, the Federal Trade Commission finalized a $1 million order against accessiBe, one of the largest overlay vendors, over claims that its widget would "automatically comply" with WCAG 2.1 AA — allegations the FTC said were false, alongside a separate finding that the company disguised paid, sponsored reviews as independent opinions (Federal Trade Commission). Overlays adjust some surface-level styling through a script; they don't rewrite the underlying code a screen reader actually parses. Courts and plaintiffs' firms know this now, which is part of why sites running these widgets keep showing up as defendants rather than being screened out.

Assuming a clean design means an accessible one. Plenty of genuinely attractive, well-converting sites fail WCAG basics, because visual polish and code-level accessibility are two different disciplines that don't automatically travel together.

Waiting for a letter before checking. By the time a demand letter shows up, you're negotiating from a worse position than if the same fixes had shipped on a normal schedule, on your own timeline, without a remediation deadline attached to someone else's lawsuit.

Treating one fix as permanent. Same lesson as the legal pages most sites forget to revisit: a site is a living thing. New pages, new plugins, new forms all reset the clock. A managed website is built around catching that kind of drift on a schedule, instead of finding out about it from a law firm.

FAQ

Does the ADA actually apply to small business websites?

Most federal circuit courts that have ruled on the question have found that Title III of the ADA, which covers "places of public accommodation," extends to commercial websites — and the law has no revenue threshold or small-business exemption written into it. The Department of Justice has informally taken the same position for years without issuing a single formal technical regulation for private businesses.

What standard do courts actually expect?

There's no ADA regulation naming an exact technical standard for private-sector websites, but courts, plaintiffs' experts, and settlement agreements have converged on WCAG (Web Content Accessibility Guidelines) 2.1 or 2.2 at Level AA as the practical benchmark.

Will an accessibility overlay widget protect me from a lawsuit?

Not reliably. The FTC fined one of the largest overlay vendors, accessiBe, $1 million in April 2025 over claims that its tool automatically delivered WCAG 2.1 AA compliance — and plaintiffs' firms have specifically targeted sites running these widgets, since the underlying code issues the overlay doesn't fix are still detectable.

How much does an ADA website lawsuit typically cost to settle?

Accessibility compliance vendor Accessible.org reports first-time small-business settlements commonly fall in the $5,000–$20,000 range, usually paired with a required remediation window and a period of ongoing monitoring — costs that can add up to more than the settlement check itself.

What actually reduces my risk?

Genuine remediation against WCAG 2.1/2.2 AA — proper alt text, keyboard navigation, labeled forms, sufficient color contrast, captioned video — checked with both automated tools and manual testing, then reviewed again whenever the site changes. There's no shortcut that substitutes for the underlying code being fixed.

Can I get sued even if I already fixed accessibility issues once?

Yes. Roughly 45% of 2025's federal website accessibility filings targeted businesses that had already been sued before, per UsableNet's tracking — usually because an earlier fix was incomplete or a newer page or feature shipped without the same review.

Is this legal advice?

No. I build and manage websites; I'm not a lawyer, and this is general information to help you know what to check and what to ask about. For anything specific to your business, talk to an attorney — this is a starting map, not a substitute for legal counsel.

---

Catching accessibility drift before it becomes a demand letter is exactly the kind of unglamorous, recurring work a managed website is built around. Nobody emails you when a form loses its label. Something has to be watching for it anyway.