The most reliable way to avoid an ADA website lawsuit is to make your site genuinely accessible: run a manual audit against WCAG 2.1 AA, remediate the real code issues, publish an honest accessibility statement, and monitor for regressions. Compliance — not a widget — is what actually lowers your risk.
Why websites get sued under the ADA
Title III of the Americans with Disabilities Act (ADA) prohibits discrimination by “places of public accommodation.” Federal courts and the Department of Justice (DOJ) have repeatedly treated business websites as covered, meaning your site needs to be usable by people who rely on assistive technology — screen readers like NVDA, JAWS, and VoiceOver, plus keyboard-only navigation and other tools.
Thousands of ADA web lawsuits and pre-suit demand letters are filed in the United States each year. Most target the same recurring barriers: images with no alt text, forms screen readers can’t parse, poor color contrast, content you can’t reach with the keyboard, and broken focus management. A plaintiff doesn’t need to prove harm in dollars — they need to show the site presented a barrier to access. That’s why the fix is technical, not cosmetic.
This page is general information, not legal advice. For guidance on your specific situation, consult a qualified attorney.
The proactive playbook to prevent an ADA lawsuit
Avoiding a lawsuit isn’t about a single purchase. It’s a short, repeatable program: audit, remediate, document, and monitor. Here’s how each piece works.
1. Audit against WCAG 2.1 AA
You can’t fix what you haven’t measured. A proper accessibility audit tests your site against the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA — the standard the DOJ and courts consistently reference. WCAG is organized around four principles known as POUR: content must be Perceivable, Operable, Understandable, and Robust.
A credible audit combines:
- Automated scanning to catch obvious, machine-detectable issues quickly.
- Manual testing by a human using a keyboard and real screen readers — because automated tools catch only a fraction of WCAG failures.
If you’re weighing your options, see our breakdown of automated vs. manual accessibility testing. Tools alone routinely miss things like illogical reading order, unlabeled custom controls, and bad ARIA — exactly the issues plaintiffs cite.
2. Remediate the real code
This is the step overlays skip. Remediation means changing the underlying HTML, CSS, and JavaScript so the barriers are actually gone:
- Adding meaningful alt text to informative images and empty
altto decorative ones. - Fixing color contrast to meet the 4.5:1 ratio for normal text.
- Making every interactive element reachable and operable by keyboard navigation, with a visible focus indicator.
- Labeling form fields and associating error messages correctly.
- Using ARIA roles and properties only where native HTML can’t do the job — and removing ARIA that misleads screen readers.
Curbcut’s website accessibility remediation does this by hand, file by file. That’s the part that holds up when someone actually tests your site with assistive technology.
3. Publish an accessibility statement
An accessibility statement is a public page that documents your conformance target (WCAG 2.1 AA), what you’ve done, known limitations, and how to report a barrier. It does not grant legal immunity — but it demonstrates good-faith effort, gives users a path other than a lawyer, and is widely expected by plaintiffs’ counsel.
4. Monitor so you don’t backslide
Most sites change weekly. A new blog post with a missing image description, an untagged PDF, or a third-party booking widget can reintroduce barriers overnight. Ongoing accessibility monitoring flags regressions early, so a single new page doesn’t turn into a demand letter.
The standards, in one table
| Term | What it is | Why it matters to your risk |
|---|---|---|
| ADA Title III | Civil rights law covering public accommodations | The legal basis for most US website accessibility suits |
| WCAG 2.1 AA | The technical accessibility standard | The conformance target courts and the DOJ point to |
| Section 508 | Accessibility law for federal agencies and contractors | Relevant if you sell to or work with the government |
| VPAT | A document reporting your conformance | Often requested in procurement; proves your AA claims |
| Conformance levels | A, AA, AAA | AA is the practical legal bar; A is too low, AAA too strict for full sites |
Want the legal landscape in more depth? Read ADA Title III and websites and our comparison of ADA vs. Section 508 vs. WCAG.
The overlay trap: why widgets won’t protect you
The single most common — and most expensive — mistake is buying an accessibility overlay and assuming you’re now safe. Overlays are JavaScript widgets that promise instant compliance with one line of code. They don’t deliver it.
- Overlays don’t fix your source code; they paint over it at runtime, and screen-reader users frequently report they make sites harder to use.
- Overlay vendors themselves have been named in ADA lawsuits, and hundreds of accessibility professionals have publicly pledged not to use them.
- A widget gives you a false sense of security while the real barriers — and the legal exposure — remain.
If you’re currently relying on one, read why overlays don’t ensure ADA compliance and the case for manual remediation over overlays. The honest answer is that real accessibility comes from real code changes, which is exactly what overlays avoid doing.
What if you’ve already been targeted?
Receiving a demand letter is alarming but not the end of the road — many are resolved before any lawsuit is filed. Don’t ignore it, loop in an attorney, and start remediation immediately. Our guides on what to do after an ADA demand letter and on serial ADA plaintiffs explain how these cases typically unfold and how to respond.
Authoritative resources
For primary sources, see the W3C Web Accessibility Initiative (WAI) for WCAG, ADA.gov for federal guidance, WebAIM for practical testing help, and Section508.gov for federal accessibility requirements.
The bottom line
There is no overlay, plugin, or one-click fix that makes ADA risk disappear. Lawsuits are avoided by being genuinely accessible — and that is fixable. Start by finding out where you stand with a free accessibility scan, then let Curbcut audit and remediate the issues by hand so your site is defensible, not just decorated.