An ADA Demand Letter Just Landed. Now What?

ClearPath Team · 2026-08-01 · 7 min read

You open your email, or a certified letter shows up at your office, and it says your website violates the Americans with Disabilities Act. Maybe it names a specific person who tried to use your site with a screen reader. Maybe it lists a dozen alleged barriers with WCAG citations attached. Either way, your stomach drops and your first instinct is probably wrong, whatever it is.

This happens to a lot of businesses. Federal ADA Title III filings hit 8,667 in 2025, a marginal 2% dip from 2024, and filings are more than 3 times the 2013 baseline with no signs of receding. Plaintiff activity is concentrated: the most active law firm in 2025 filed over 600 cases on behalf of multiple plaintiffs. You are very likely one of many businesses that got a nearly identical letter this month, not a uniquely targeted one. That doesn't make it less serious. It just means there's a known playbook for how to respond, and panicking isn't part of it.

Day one: read it, don't ignore it, don't fire back an email

Read the whole letter slowly. Note two things specifically: the deadline it gives you to respond, and the exact barriers it claims exist, page by page if it lists them. Demand letter response windows typically run 10 to 30 days, and a formal federal lawsuit response is usually 21 days, or 60 if you're out of state. Write that date on a calendar today.

What you should not do is reply on your own with an explanation, an apology, or a promise. The first instinct, especially if the letter quotes specific violations on your site, is to fire back an email explaining or apologizing. Don't. Anything you say can become part of the record. And whatever you do, don't just set it aside and hope it resolves itself. The most dangerous action you can take is inaction. Many business owners, overwhelmed by the complexity of the allegations or the fear of legal costs, simply set the letter aside hoping it will go away. If you ignore it and a lawsuit is later filed, it will not be possible to settle it for as little as would have been possible pre-suit. It will not go away.

Don't panic-buy a "guaranteed compliance" product

Somewhere in the next 48 hours you'll probably see an ad or get a cold email promising instant ADA compliance for $49 a month. Be skeptical of anything that claims to make the legal exposure disappear. Courts have rejected widget defenses for several reasons, including that screen readers can conflict with overlay code. No plugin, script, or vendor contract can make an existing claim go away, and no honest vendor will tell you it can. What actually moves the needle with a plaintiff's attorney is evidence that you're taking real, documented action on your actual code. Tools like ClearPath can still be useful here, but only as a visitor-facing aid that runs alongside real fixes, not as a substitute for them. It won't touch your underlying markup or custom JavaScript, so don't let anyone sell it to you as a stand-in for that work.

Get a real audit, not just an automated scan

Before you respond to anything, you need to know what's actually true on your site. Don't rely on a five-minute automated scan alone. Don't rely only on automated scanning. Automated tools reliably catch only 30 to 40% of WCAG failures. A manual accessibility audit, or an audit conducted by people with disabilities, gives you a complete picture, which is also what your legal team needs to negotiate from an informed position. This audit does double duty: it tells you whether the specific claims in the letter hold up, and it gives your attorney something concrete to negotiate from.

Fix the blocking failures first

You won't fix everything in a week, and nobody expects you to. Triage instead. Prioritize the highest-impact barriers first: checkout and payment flows, account access, and any functionality that directly limits a disabled person's ability to use your core service. Common issues named in these letters include missing form labels, keyboard traps that prevent tabbing through a menu or checkout, images with no alt text, low contrast text, and empty links that just say "click here." Start with whatever blocks someone from actually completing a purchase or booking. That's what a court and a plaintiff's attorney both care about most. While your developers work through that list, ClearPath's 25 adjustment tools can give some visitors, people who need larger text, higher contrast, or a different reading profile, a workable way to use your site in the meantime, in whichever of its 14 supported languages they read.

Document the plan

Write down what you found, what you've already fixed, and a realistic timeline for the rest. Courts evaluating ADA web cases look at whether the site conforms to a recognized standard like WCAG 2.1 AA, whether the defendant has taken reasonable steps to identify and remediate barriers, and whether documentation exists to support a good-faith claim. A site with real source-level remediation, regular scans, and a public accessibility statement is in a much stronger position. This documentation isn't paperwork for its own sake. It's what your lawyer hands over during settlement talks to show you're acting in good faith, not stalling. ClearPath's automatically generated accessibility statement can be one small piece of that paper trail, alongside your audit and remediation records, though it's no substitute for the source-level fixes courts are actually looking for.

Talk to a lawyer, this week

Don't wait until you've fixed everything to call an attorney who handles ADA Title III cases. Engage an attorney to review the complaint and assess your compliance status within the first days after the letter arrives. They'll tell you whether the plaintiff has standing, whether the specific claims are credible, and how aggressive the sending firm typically is. That context changes your negotiating position more than anything else you can do this week.

What it actually costs and what plaintiffs ask for

The numbers vary by source, but they cluster in a predictable range. Demand letters average around $5,000 to settle, out-of-court settlements average around $30,000, and court judgments average around $85,000, with defense legal fees of $30,000 to $175,000 on top in all cases. Litigated cases run higher: litigated cases typically settle for $30,000 to $150,000 or more, depending on company size, violation count, and jurisdiction. Most plaintiffs aren't asking for a check alone. Settlements typically require WCAG conformance, not widget installation, and you'll need actual remediation regardless. Expect a request for a signed remediation timeline, sometimes ongoing monitoring, plus a settlement payment covering the plaintiff's attorney fees.

A demand letter is stressful, but it's also a known process at this point. Read it carefully, get real data instead of guessing, fix what blocks people from using your core service, write it all down, and let a lawyer who does this work handle the negotiation. That's the whole first week.