You've Received an ADA Web Accessibility Demand Letter

A letter arrives. It names your website, cites the Americans with Disabilities Act, describes barriers a named plaintiff says they encountered, and proposes a number to make it go away. It probably arrived by email, probably to a general inbox, and it is probably the first time anyone at your organization has thought hard about web accessibility.

This is written for the next few days. It is not legal advice — get a lawyer, genuinely, and read the section on that below. It is the operational and technical picture, from a firm that has been brought in on the remediation side of a lot of these.

What the letter actually is

Most web accessibility demand letters are pre-litigation settlement demands. A law firm, usually working with a repeat plaintiff, asserts that your site is a place of public accommodation under Title III of the ADA, that it presents barriers to a person with a disability, and that you should pay a sum and fix the site rather than be sued.

Three things are true about this at once, and holding all three is how you make good decisions:

The legal theory is real. Title III has been applied to websites by multiple federal circuits. There is no federal web standard for private businesses, which sounds like it helps you and does not — courts have generally landed on WCAG Level AA as the reference point anyway, because it is the only widely recognised technical standard available.

The barriers are usually real too. This is the part organizations resist hardest. The letter is often generated after an automated scan, and the specific findings are frequently thin, sometimes wrong, occasionally about pages that no longer exist. But when we audit a site that has received one of these, we almost always find that the underlying claim — that a screen reader user cannot complete a core task — is correct. The letter is opportunistic. That does not make it inaccurate.

The business is being targeted for being reachable, not for being the worst. You were not singled out because your site is unusually bad. You were found by a scan, or because you are in an industry with a run of filings, or because your site has a form somebody could not submit. Plenty of worse sites got no letter this week.

The first week

Do not reply immediately. Not because you are hiding, but because an early reply written by whoever opened the email tends to contain admissions, promises about timelines nobody has scoped, or an argument about whether the ADA applies. All three cost you later.

Preserve the site as it is. Take a full crawl or archive of the pages named, and record the date. Not to hide anything — the opposite. You want a defensible record of what the site looked like on the date of the letter, because you are about to change it, and "they fixed it after we complained" and "that was never broken" are very different conversations. A wget mirror or a commercial archiving service both work. Keep it with the letter.

Find out who owns what. By the end of week one you should know: who hosts the site, who can deploy to it, which parts are third-party (booking engine, payments, chat widget, scheduling, PDFs), and which vendor contracts govern those. In our experience this is the single biggest source of week-two surprises. The part of the site the letter complains about is very often the part you do not control.

Get an honest baseline. Not the scan in the letter — a real audit of the flows that matter, with assistive technology, done by someone who will tell you the bad news. You cannot negotiate a remediation timeline for work nobody has scoped. You also cannot tell whether the letter's specific claims are accurate, which matters for the conversation your lawyer is about to have.

You can start this yourself the same afternoon. Put the mouse away and try to complete your most important task — buy, book, apply, contact — using only the keyboard. That fifteen minutes will tell you more about your exposure than the letter does.

Get a lawyer, and get the right kind

This document does not substitute for counsel and neither does your instinct. Some specifics worth knowing before that call:

• Your general counsel or corporate attorney may not have done one of these. Web accessibility demands are a specific practice area with a small number of firms who handle volume on both sides. Ask directly whether they have handled ADA Title III web matters, and how many.
• Insurance may cover it. Check your general liability and any EPLI or cyber policy for defense coverage. Organizations routinely discover this in month three rather than week one, after spending money they did not need to.
• The fix and the settlement are separate tracks. Counsel handles the second. The first is yours regardless of how the second turns out, which is the point most people miss — see below.

The four expensive mistakes

Installing an overlay. The reflex when a letter arrives is to buy the thing that promises instant compliance. Accessibility overlays and widgets do not produce WCAG conformance, are rejected by much of the disability community, and — this is the part that matters here — have themselves been named in accessibility litigation. Some demand letters now specifically cite the presence of an overlay. You are being asked to demonstrate good faith; installing a product that the disability community regards as harmful does the opposite. We have written separately on why overlays don't work.

Fixing only what the letter lists. The letter is a sample, usually automated, usually partial. Remediating exactly those items and nothing else produces a site that is still inaccessible, a settlement you cannot honestly certify against, and a live risk of a second letter from a different plaintiff about a different page. Fix the classes of problem, not the instances.

Going quiet. Non-response converts a settlement demand into a filed complaint, and a filed complaint is public, more expensive, and much harder to resolve quietly. Counsel decides the timing and the words; the decision to engage at all is not really a decision.

Promising a date nobody scoped. "We will be fully WCAG 2.1 AA conformant within 90 days" is the sentence that turns a one-off settlement into an ongoing compliance obligation you then breach. Scope first, commit second, and commit to something achievable — a sequenced plan with dates per phase is far more credible, and far safer, than a single heroic deadline.

What settlements usually require

Terms vary enormously and yours will be whatever your counsel negotiates. But the shape recurs:

• A conformance target, nearly always WCAG 2.1 Level AA, sometimes 2.2.
• A timeline, commonly twelve to twenty-four months, often phased, with the highest-impact user journeys first.
• Third-party content addressed, which is the clause that catches people. If your booking engine is inaccessible and the vendor will not fix it, you may be contractually obliged to replace it.
• An accessibility policy and a feedback mechanism — a published statement with a working way to report a barrier and a commitment to respond.
• Training for the people who publish content, because the most common failure mode after remediation is a staff member uploading an untagged PDF into a site that was conformant last week.
• Periodic testing and reporting, sometimes by an agreed third party.
• A payment, usually the smallest line in the long-run cost.

That last point is the one to internalise. The money is rarely what hurts. The remediation programme you just agreed to is what hurts, and you will be doing it under a deadline with a lawyer watching instead of on your own schedule.

The thing nobody wants to hear

You have to fix the site either way.

Whatever happens with this letter — settled, defended, dismissed, withdrawn — the website still cannot be used by some of the people it is for. That was true before the letter arrived and is unaffected by the outcome. If you settle, you have a deadline. If it goes away entirely, you have a site with the same barriers and now documented knowledge of them, which is a materially worse position if a second letter arrives.

The organizations that come out of this well treat the letter as an unwelcome forcing function for work they needed anyway. The ones that come out badly treat it as a legal problem to be minimised, spend the money on defence and an overlay, and receive another letter eighteen months later.

What the work actually looks like

Roughly, and assuming a mid-sized site:

Weeks 1–4 — audit and inventory. Every property in scope, including vendor portals and document libraries. Testing against WCAG 2.1 AA with assistive technology, not just a scanner. Output is a findings list tied to specific criteria, ranked by who it blocks and how completely.

Weeks 4–12 — the component layer. Most of the value. Fixing a button component, a form pattern, a modal and a navigation once fixes them on every page that uses them. Sites built on a design system remediate dramatically faster here than sites built page by page over a decade.

Ongoing — content and documents. PDFs are usually the long tail and frequently the worst of it. This is where a phased commitment earns its keep: nobody remediates fifteen years of untagged PDFs in ninety days, and a settlement that requires it was badly negotiated.

Ongoing — governance. Training, acceptance criteria in the development process, accessibility language in procurement so the next vendor does not recreate the problem, and a monitoring cadence that catches regressions.

Costs vary by an order of magnitude depending on how the site was built. We have written honestly about what remediation actually costs, including why quotes for the same site differ so wildly.

If you are reading this and have not received a letter

Then you have the thing everyone in the paragraphs above would trade real money for: the ability to do this on your own schedule, at your own pace, without a deadline written by someone else's lawyer.

Start with the free checker or spend fifteen minutes doing the keyboard test described above. Neither costs anything and both will tell you whether this is a live problem for you.

---

This article is general information, not legal advice, and does not create a client relationship. Accessibility law is fact-specific and moves. Get counsel who has handled these before making decisions about a letter you have received.