Received an ADA Website Demand Letter? What To Do as a Small Business

First, what you're actually holding

An ADA website demand letter is a pre-suit notice, usually from a plaintiff's firm, alleging that your website fails Title III of the Americans with Disabilities Act because someone with a disability could not use it with assistive technology — a screen reader that hit unlabelled buttons, a checkout that could not be completed with a keyboard, images with no alternative text. The letter names a sum to make it go away and sets a deadline.

It feels personal. It almost never is. Many of these claims come from serial filers — firms that file hundreds of near-identical cases, often after an automated scanner flags a handful of issues. Knowing that changes how you respond: this is a process to work through calmly, not an accusation to argue with emotionally.

The volume is real, which is why your letter exists at all. Industry trackers recorded more than 5,000 digital accessibility lawsuits across federal and state courts in 2025, and website cases made up roughly 36% of all ADA Title III federal filings that year (Seyfarth's ADA Title III blog). Demand letters that never reach court outnumber the filed cases many times over. You are not an outlier; you are on a list.

What to do in the first week

The single biggest mistake is doing nothing. If a letter turns into a filed lawsuit and you miss the response window — in US federal court that is typically 21 days after being served — the plaintiff can seek a default judgment and you lose automatically, without anyone ever weighing the merits. So the clock matters even when the letter feels like spam.

A sensible order of operations for what to do with an ADA demand letter:

• Do not contact the plaintiff or their lawyer directly. Anything you say, including a defensive "we're already compliant", can be used against you.
• Do not ignore it, and do not delete it. Diarise every date in the letter.
• Get it in front of a qualified ADA web accessibility lawyer. A specialist who knows the firm sending your website accessibility legal notice will know its usual settlement range and tactics — that knowledge alone is worth the consultation.
• Preserve evidence. Take a dated snapshot of the site as it stands. If you remediate later, you'll want a clear before-and-after record.
• Tell your insurer. Some general liability and cyber policies respond to accessibility claims. Late notice can void the cover.

Notice what's missing from that list: rushing to settle, and rushing to buy a quick fix. Both come later, and both go better once you know the true state of your site.

Why the overlay widget won't save you

If your first instinct is to drop in an "accessibility widget" — the little wheelchair icon that promises instant compliance — pause. An overlay widget is not legal protection, and the data is blunt about it. TestParty's analysis of court records found that over 1,000 businesses, more than a quarter of all digital accessibility lawsuits, were sued despite having an overlay installed. In the first half of 2025 alone, roughly 22.6% of web accessibility lawsuits targeted sites that already ran one (Accessibility.Works).

The reason is mechanical, not marketing spin. Overlays sit on top of your page; they don't repair the underlying HTML where most defects live. Screen readers frequently conflict with them, and plaintiff attorneys scan the raw code, not the overlay-modified version — so the widget is invisible to the people testing you and ineffective for the people who need access. The regulators agree: in January 2025 the US Federal Trade Commission fined overlay vendor accessiBe $1 million for deceptive claims that its tool could make any site WCAG 2.1 AA compliant within 48 hours. A widget can be one small layer of help; it is not a defence, and buying one after a letter arrives can read as an admission you knew there was a problem.

The standard you're actually being measured against

There is no separate "ADA code" for websites. In practice, courts and settlements treat the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as the technical benchmark, with 2.2 AA emerging. That gives you something concrete to aim at instead of a vague legal cloud.

It also tells you why scanners and overlays fall short. Automated tools detect only around 30–40% of WCAG issues — WebAIM's research puts it in that range — because most success criteria require human judgement. Can a sighted-keyboard-only user reach every control in a logical order? Does a screen reader announce form errors usefully? Do colour contrasts hold up, do videos carry captions, does the focus indicator never disappear? A machine can't reliably answer those. A person testing with assistive technology can. That is the difference between looking compliant and being usable.

The WCAG manual audit is the real fix

This is the part that genuinely moves your risk: a WCAG manual audit after the demand letter, run by a human who tests your site the way your visitors do. Not a scanner PDF — a structured assessment that combines automated coverage with keyboard and screen-reader testing, mapped against WCAG 2.1 AA, prioritised by severity, and tied to specific fixes in your code or content.

Done properly, an audit gives you three things at once. It tells your lawyer the honest state of play, so any response to the ADA demand letter is built on facts rather than hope. It produces a remediation plan you can actually execute and evidence later. And it often reveals that the plaintiff's list — frequently a scanner's greatest hits — covers only a fraction of what's there, which is precisely why a real audit, not the widget, is what closes the gap.

Most settlements require documented remediation within 90 to 180 days alongside any payment, so the work has to happen regardless. The businesses that come out of this cheaply are the ones who started the audit early and could show genuine progress while negotiating, rather than promising a fix they hadn't begun.

What it tends to cost — and where the cost actually hides

Honest numbers help you make decisions, so here is the range the sources support. For a small business, the ADA website lawsuit settlement cost commonly lands between £/$5,000 and $15,000, with companies under roughly $1m in revenue often settling for $3,000–$8,000 (TestParty; Accessible.org). Many smaller firms settle for less. Early settlement is frequently the most cost-effective route, but it almost always means paying the plaintiff's legal fees on top of the settlement figure.

The trap is treating the settlement number as the whole bill. It rarely is. Settlements routinely bolt on mandatory remediation, third-party audits, user testing, and ongoing reporting to the plaintiff's counsel — and those monitoring obligations can cost more over time than the original payment. Add your own legal fees and internal hours, and total exposure on a contested matter can climb well past the headline figure. The cheapest version of this story is the one where your site was already close to WCAG 2.1 AA before any letter arrived.

After the dust settles: make it stick

Remediating once and forgetting is how businesses end up on a repeat list — of the 2025 digital accessibility lawsuits, more than 1,400 targeted companies that had already faced a claim. Accessibility is a property of a living site: new pages, new plugins, a redesign, a marketing landing page thrown up in a hurry, and the failures creep back.

So the durable answer is to fold accessibility into how the site is built and maintained — semantic, standards-based markup; alt text and captions as part of publishing, not an afterthought; periodic re-testing rather than a one-off scramble. That is quieter and far cheaper than a second letter. It's also simply a better website: the same work that satisfies WCAG makes your pages faster to navigate, easier to find, and usable by more of your customers.

Where SOLMONARC fits — and where we don't

We're a UK software and web studio, not a law firm. If you've been served, your first call is a qualified accessibility lawyer; we'll happily work alongside whoever you choose. What we do is the technical half they can't: a genuine manual WCAG 2.1 AA audit of your actual site, a prioritised remediation plan, the engineering to fix it properly in the code, and re-testing so you can show the work was done.

And if an audit shows your site is in decent shape and a focused round of fixes will clear it, we'll tell you that plainly — you don't need a rebuild to answer a demand letter, and we won't sell you one. The point is to get you out of the firing line and keep you out, not to turn a stressful letter into a larger invoice.