What to Do When a Business Gets an Accessibility Demand Letter
A demand letter alleging a website is not accessible is alarming, but it is not a judgment. This post covers what such a letter is, the steps worth taking in the first week, and the ones to skip.
Updated with additional research.
This post is general information, not legal advice. An attorney decides how a specific letter should be handled.
A demand letter can arrive by email or certified mail, from a law firm the business has never heard of, on behalf of a plaintiff it has never met. It states that the website violates the Americans with Disabilities Act, cites barriers a screen reader user allegedly encountered, and requests remediation, sometimes alongside a settlement figure.
The letter is designed to alarm. Some of that alarm is warranted and some is not. Knowing the difference shapes the next few weeks.
What the Letter Is
The Department of Justice takes the position that Title III covers goods and services offered on the web, and the ADA Title III post covers where courts differ. So the underlying claim cannot be assumed baseless.
No published data counts demand letters or tracks how they end. Seyfarth Shaw counted 3,117 federal website accessibility lawsuits in 2025, but its method left out demand letters and state-court cases. Those suits made up about 36% of all federal ADA Title III filings that year, and New York federal courts led with 1,021 of them. The counts show how active this area is. They say nothing about how any single letter ends. A letter opens a negotiation more often than it starts a lawsuit.
A letter wants one of two outcomes: a payment, or a commitment to fix specific issues. Sometimes it wants both. The letter is a starting point, not a verdict.
The First Week
Ignoring a letter rarely helps. A claim left unanswered does not go away, and the situation tends to get harder to resolve.
Communication with the sender is best routed through counsel, since an informal apology or promise to fix things could affect a negotiating position. Whether and how to reply is a question for a lawyer.
The right attorney has handled ADA Title III website claims, not only general business litigation. The area is narrow enough that specific experience matters.
A quick technical fix can wait until the actual problems are known. Overlay vendors sell quick fixes in this situation. The FTC ordered accessiBe to pay $1 million over unsupported claims that its tool made websites WCAG-compliant. The Overlay Fact Sheet, a statement from accessibility practitioners, says no overlay can make a site fully compliant with any accessibility standard. The overlay post goes into detail.
Reading the Letter Closely
Some letters come from firms that send many near-identical letters. That is not a reason to dismiss one, but it helps calibrate the response.
The page addresses, dates, and described barriers in a letter can be compared against the current site, which is a useful first check before anything else happens. A letter naming specific, plausible barriers, such as missing form labels, no keyboard access to a booking widget, or images with no alternative text, reads differently from one with generic language that could apply to almost any site. The specific one calls for a specific, evidence-based response. For a generic one, an attorney can ask early whether the plaintiff can substantiate the claim beyond the template.
Either way, the sequence is the same: get counsel, get an audit, and let the evidence drive the negotiation instead of the tone of the letter.
What an Audit Adds
Once counsel is retained, the practical next step is usually an accessibility audit that documents the site’s state against WCAG success criteria. That means automated scanning plus manual testing by someone who knows the standard, not a scanner report alone. WebAIM notes that automated checks cannot catch every WCAG failure.
An audit serves two purposes. It tells the attorney what is true, which shapes the negotiation. It also produces a remediation roadmap the site would need regardless of how this letter resolves, because the underlying obligation continues after the letter is answered.
Audit findings are mixed. Some claims in a letter are accurate, some are exaggerated, and occasionally one does not match the current site, because the plaintiff’s testing may be months old or used an unusual browser and assistive technology combination.
What Does Not Help
Quick “make it go away” responses do not help: installing a widget, publishing a generic accessibility statement with no remediation behind it, or paying the requested amount without verifying what is alleged. Each treats the letter as the problem.
The opposite instinct also fails. Assuming a letter is meritless because it feels like a shakedown ignores the data. Some demand letters are opportunistic, but WebAIM’s 2026 scan found detectable WCAG failures on 95.9% of one million home pages. That scan used automated checks on top-ranked sites, not small businesses or letter recipients, so it shows how common failures are rather than what any one letter alleges.
After This One Resolves
Whatever the outcome, the underlying gap needs a fix, not a settlement-driven patch. The small business owner’s guide to website accessibility covers what accessibility work involves, apart from any legal situation. I recommend WCAG 2.2 AA as the target, since it also meets 2.1 AA, the version cited in current regulations.
The COREaccess™ Accessibility Leadership System covers the audit, remediate, train and monitor framework. A business dealing with a letter now can book a 15-minute conversation once counsel is retained.