Home › ADA lawsuit guide
ADA website lawsuit guide: the risk, the cost, and how to avoid one
What an ADA web-accessibility lawsuit is, why they're so common, and the real way to reduce your exposure.
How an ADA web lawsuit works
- A user (often with a screen reader) can't complete a task on your site: checkout, booking, form.
- That's framed as a denial of access under the ADA (and state laws like California's Unruh Act).
- A demand letter or filing follows, citing specific WCAG failures.
- Most businesses settle to avoid litigation costs.
Why overlays make it worse, not better
Accessibility overlay widgets (accessiBe, UserWay, AudioEye) are specifically targeted by plaintiff firms. Sites running them still get sued, because the widget doesn't fix the underlying code. In 2025 the FTC fined an overlay vendor $1M for deceptive "compliance" claims. An overlay can be evidence you knew about the problem and papered over it.
How to actually reduce your risk
| Do | Why |
|---|---|
| Scan for WCAG issues | Know your machine-detectable failures |
| Fix them in your code | The only thing that removes the barrier |
| Monitor continuously | New code = new issues = new exposure |
| Document remediation | Shows good-faith effort |
This is general information, not legal advice. Consult an attorney about your situation. AdaClear automates the scan + fix-list + monitoring; start with a free scan to see where you stand.
Enter your site for an instant ADA/WCAG scan: score + top issues. No overlay, no signup.
Frequently asked
Can I get sued for an inaccessible website? Yes. Thousands of ADA web-accessibility lawsuits and demand letters are filed in the US every year against businesses whose sites blind or motor-impaired users can't use. Settlements commonly run $10,000-50,000.
Do accessibility overlays protect me from ADA lawsuits? No. Hundreds of ADA suits have named sites that had an overlay installed, and the FTC fined an overlay vendor $1M in 2025. (FTC, 2025) Only fixing your code reduces real risk.
How do I reduce my ADA lawsuit risk? Find your WCAG issues, fix them in your code, keep monitoring, and document your remediation. Start with a free scan to see where you stand.