The Envelope
It starts with an envelope.
Inside is a demand letter from a plaintiff's attorney. It cites the Americans with Disabilities Act, Title III. It names your website specifically — not "your online presence" in the abstract, but particular pages, particular pages' worth of barriers. A blind visitor, it says, using a screen reader, tried to check out and couldn't complete the purchase. Or tried to find your store hours and hit a wall. The letter lists what went wrong in specific, technical terms: missing alt text on product images, a form field with no label, a "skip to content" trap that never lets keyboard focus escape, text that fails color contrast against its background.
Then comes the deadline. Respond within a set window — usually short — with either a remediation commitment or a settlement offer, or expect a complaint to be filed in federal court.
If you run a business with a website — which is to say, if you run a business — this is worth understanding in detail, because the letter is not random, and neither is what happens after it arrives.
This Isn't a Fringe Risk
ADA Title III website lawsuits aren't a rare, edge-case phenomenon. They've been filed in U.S. federal courts by the thousands every year, for over a decade now, tracked closely by legal-tech researchers and law firms that publish annual litigation reports on digital accessibility (firms like Seyfarth Shaw and trackers like UsableNet are two well-known sources in this space). The filings cluster heavily in a handful of states — New York, Florida, and California lead — largely because those states have favorable state-law overlays and a body of precedent that makes these claims easier to bring and harder to get dismissed early.
The practical upshot: if your business operates online and serves customers in those states, or frankly anywhere, the exposure is real and it's ongoing, not theoretical.
Why It Usually Starts With a Letter, Not a Lawsuit
Here's a detail that surprises a lot of business owners: most cases don't begin with a courtroom filing. They begin with a pre-suit demand letter.
There's a reason for that sequencing. A demand letter is cheap for the plaintiff's attorney to send and gives the business a chance to settle before litigation costs stack up on both sides — which, perversely, is also exactly why letters get sent in volume. The letter typically documents specific barriers found through some combination of an automated accessibility scan and a manual test by an actual screen-reader user. Common findings show up again and again:
- Missing or meaningless alt text on images
- Form fields with no programmatic label
- Keyboard traps — places where a keyboard-only user can tab into a component and can't tab back out
- Insufficient color contrast between text and background
None of these are exotic. They're the same failure categories that show up in almost every unaudited website, which is exactly why they're the ones plaintiff's counsel scans for first.
What This Actually Costs
There's no single number to put on this, and any article that hands you a precise dollar figure without knowing your business is guessing. But the cost structure is consistent and worth laying out plainly, because it has more moving parts than most people expect.
Attorney fees to respond. Whether you settle quickly or fight it, you're paying legal counsel to evaluate the letter, negotiate, or litigate. This cost exists regardless of outcome.
A settlement or judgment amount. Litigating an ADA Title III claim through to trial is expensive on its own terms, and the underlying legal standard tends not to favor an inaccessible defendant once the barriers are documented — the statute asks whether removing the barrier was "readily achievable," and WCAG 2.1 AA has become the practical, widely referenced benchmark courts and plaintiffs point to for what "accessible" means. That combination — expensive to litigate, weak ground to defend from — is exactly why settling is the common outcome.
Remediation costs, which you're paying either way. This is the part that catches people off guard: settling the lawsuit does not fix the website. The alt text is still missing. The keyboard trap is still there. You will pay to remediate the actual barriers regardless of whether you settle, lose, or win — because the site still doesn't work for disabled visitors, and that's a business problem independent of the legal one.
An ongoing monitoring or consulting commitment. Many settlement agreements don't just resolve the individual claim — they require the business to commit to continued accessibility monitoring or consulting for a period afterward, which is its own recurring cost.
Stack those four together and the "cost of the letter" is rarely just one line item. It's legal fees, plus a settlement, plus the remediation work you needed to do anyway, plus an ongoing obligation.
The Part Nobody Tells You: Settling Doesn't End the Exposure
Here's the detail that matters most and gets missed most often: resolving one lawsuit does not fix your risk. It resolves one claim, from one plaintiff, about the barriers that plaintiff happened to hit.
If the underlying barriers on your site aren't actually remediated — just settled around — you remain fully exposed to a second demand letter from a different plaintiff's attorney, representing a different visitor, citing the same or similar barriers. The lawsuit didn't create the exposure. The inaccessible website did. Settling a claim without remediating the site is like paying a fine for a broken stair and then leaving the stair broken — someone else is going to trip on it.
This is why remediation, not settlement alone, is the thing that actually closes the loop.
The Cheapest Path Is the One You Take Before the Letter
Every dollar spent above assumes reactive mode: something already happened, and now you're managing consequences. The lowest-cost version of this entire story is the one where the letter never gets written, because there's nothing on your site for a scan or a screen-reader tester to find.
That means, concretely:
- A WCAG 2.1/2.2 AA conformance review, done before any claim arrives — not as damage control, but as standard due diligence, the same way you'd audit your own financials or security posture.
- Fixing the highest-risk failures first: missing alt text, keyboard traps, unlabeled form fields, and insufficient color contrast. These four categories aren't arbitrary — they're the barriers most commonly cited in actual demand letters, which means fixing them first directly reduces the odds of ever becoming a target.
- Publishing an accessibility statement that documents an active, ongoing remediation effort. This does two things at once: it signals genuine good-faith effort (which matters if a claim ever does arrive), and it often gives a visitor who hits a snag a channel to report it directly to you instead of to an attorney.
- Treating an accessibility overlay or widget as a starting point, not a finish line. An overlay layered on top of an unremediated site does not fix missing alt text, does not fix a keyboard trap, and does not fix an unlabeled form field. It changes the appearance of effort without changing the underlying code — and plaintiff's attorneys and their testers know the difference.
None of this is exotic engineering. It's disciplined, specific work against a known standard, done once, properly, instead of piecemeal under a legal deadline.
Where This Actually Lands
An ADA demand letter is not bad luck. It's a predictable outcome of a predictable set of technical gaps — the same handful of gaps, over and over, that a proper WCAG 2.1 AA review catches before anyone outside your company ever notices them.
Getting this exactly right — the technical audit, the prioritization, the remediation, the documentation — is genuinely hard to do well on your own, especially while running the rest of the business. It's also exactly what WCAG.World does every day: full conformance reviews, prioritized fixes starting with the barriers that actually show up in real demand letters, and the kind of documented remediation effort that keeps a second letter from ever getting written.
If you'd rather deal with this on your terms, before an envelope shows up on someone else's, start with a conversation.