I Got an ADA Website Demand Letter — What Do I Actually Do? (A Calm, Step-by-Step Guide for Small Business Owners)

You opened an email or a certified letter from a law firm. It says your website violates the Americans with Disabilities Act (ADA), lists some accessibility failures (usually referencing WCAG, the Web Content Accessibility Guidelines), and asks you to pay an amount to "resolve the matter." There may be a deadline.

First, breathe. This guide walks you through what the letter is, the moves that protect your position, the moves that quietly make things worse, and what a credible response actually looks like.

Important — read this before anything else. This article is general educational information, not legal advice, and reading it does not create an attorney–client relationship. If a demand letter or lawsuit has already landed, your first call should be to a qualified attorney — ideally one familiar with ADA Title III website claims. What you say, what you publish, and what you change on your site (and when) can affect your position. Use this guide to get oriented and organized; use a professional to confirm where you stand.

---

What this letter actually is

A web-accessibility demand letter is a pre-litigation claim that your website is not accessible to people with disabilities — for example, that a screen-reader user can't complete a purchase, or a keyboard user can't operate your menu. Under ADA Title III, businesses that serve the public ("places of public accommodation") are generally expected to make their goods and services accessible, and U.S. courts and the plaintiff's bar have widely treated WCAG 2.1 Level AA as the practical technical target — even though there is no single federal regulation that pins down one standard for private businesses.

Two facts surprise most owners:

• Small businesses are not immune. A five-person Shopify store can receive the same kind of letter as a national chain.
• These claims are common and rising. Per Seyfarth's ADA Title III tracker, plaintiffs filed 3,117 federal website-accessibility lawsuits in 2025, a 27% increase from 2024, and those cases were 36% of all ADA Title III federal filings. Seyfarth also notes that demand letters and state-court cases are not included in those federal counts, so the visible lawsuit total is not the whole market.

So no, you were not singled out for being uniquely terrible. You're one of many. That's not comforting, but it does mean there's a well-understood playbook.

---

The 3 moves that quietly make it worse

Before the "do" list, here are the instincts to resist.

1. Ignoring it

A demand letter is not spam, even when it feels like a shakedown. Ignoring it can lead to a filed lawsuit, which is far more expensive and harder to control than an early, attorney-led response. Silence is the riskiest option.

2. Silently "just fixing" the site yourself first

It feels productive to start editing your theme the moment the letter arrives. But what you change, and the timing of it, can matter to your legal position — and rushing can destroy useful records of the site's prior state. Whether and how to remediate before responding is a question for your attorney, not a reflex. Get the advice first; you'll fix the same things either way, just in the right order and on the record.

3. Panic-buying an accessibility "overlay" widget

This is the big one. Those "$49/month, instant ADA compliance" widgets are not a defense:

• In April 2025, the FTC's final order required accessiBe to pay $1 million and barred it from claiming that an automated product makes websites WCAG-compliant (ftc.gov).
• Overlays inject a script but don't change your underlying source code — and plaintiff-side scanners read the underlying HTML straight through them.
• Per TestParty's 2026 guide, over 40% of these lawsuits are repeat suits against companies that were previously sued, often because the real issues were never fixed.

Buying a widget to make the letter "go away" can leave you exposed to a second letter — having spent money and changed nothing that matters.

---

What your attorney actually wants (and what plaintiffs respond to)

Here's the reframe that changes everything. The question driving a credible response is rarely "is every pixel of my site perfect?" It's "what have you done about accessibility, and can you show it?"

The documentation that helps usually includes: dated records of what you tested and when, records of the code fixes you made, your published accessibility statement, and any audit results. Outcomes vary by case and jurisdiction — this is not a promise about yours. The point is that documentation lets your attorney show concrete good-faith effort instead of asking a claimant to trust a vague assurance.

In other words: a business that can show an honest accessibility statement, a dated remediation log, and a clear direction of travel is in a far stronger position than a nice-looking site with no records. Demonstrated good-faith effort, on paper, is the asset. No tool, including ours, can promise an outcome with any plaintiff, court, or regulator — but building that record is the credible path.

---

The step-by-step: your first 30–60 days

Most demand letters give a window — often 30–60 days — to respond. Here is a sensible sequence. Adjust it to whatever your attorney advises; their guidance overrides this list.

Days 1–2 — Stabilize.

• Don't respond to the sender yet. Don't post anything new on social media about it.
• Contact a qualified attorney. Forward them the letter.
• Preserve records: save the letter, note the date received, and avoid wholesale site changes until you've had advice.

Days 3–10 — Find out where you actually stand.

• Assess your key pages and journeys (home → product/service → cart/contact → checkout/submit). You want a clear picture of the real, machine-detectable barriers and the human-judged ones.
• Crucial honesty: a clean automated scan is not a clean bill of health. Deque's automated coverage report found that automation identified 57.38% of total issues in its audit sample, while still covering only 16 of 50 WCAG 2.1 Level AA success criteria. Keyboard traps, invisible focus, poor alt text, contrast judgement, reflow and error-message quality still need a person running the real journeys.

Days 10–30 — Fix the real barriers and document everything.

• Work top-down: critical issues first (a checkout you can't complete on a keyboard, a cart button with no accessible name), then serious, then moderate.
• Log every fix with a date, the WCAG criterion, and who did it. This dated log is your single most valuable piece of evidence. Date entries when the work actually happened — never back-date.
• Publish an honest accessibility statement with a real, monitored feedback contact. Never publish "100% compliant" or "fully accessible" — over-claiming is itself a risk the FTC and plaintiffs scrutinize. The credible statement says: "this site is partially conformant with WCAG 2.1 AA; here's what we've tested, here's what's outstanding, here's our plan, here's how to reach us."

Days 30–60 — Respond through counsel, with proof.

• Your attorney handles the response and any negotiation, ideally attaching the dated record of what you tested, fixed, and planned. That record is what turns "we did nothing" into "we acted in good faith, here's the evidence."

---

A faster way to produce the exact record counsel asks for

The hard part for most owners isn't finding problems — free scanners do that and dump a wall of error codes. The hard part is the three things free tools don't give you: a prioritised, developer-ready fix list, the manual tests automation can't run (captured as evidence), and a dated good-faith Defense File to hand your attorney.

That gap is exactly why we built the ADA Web-Accessibility Defense Kit — a $149 one-time tool that runs entirely in your browser (nothing is uploaded). You paste a page's HTML, run seven guided manual tests, log each fix with a date, and it generates a developer remediation report (element → problem → fix → WCAG reference), an honest accessibility statement, a VPAT-style conformance summary, and one combined, dated Defense File. It's a fraction of a single professional audit ($1,500–$10,000+), and it comes with a 30-day money-back guarantee.

To be completely clear, because honesty is the whole point of this category: the Kit is a self-assessment tool, not legal advice, not an audit, and not a guarantee of compliance. It documents your good-faith effort and shows you the real barriers to fix. The step it cannot replace is a review by a qualified accessibility professional and/or your attorney — and if a letter has already landed, that attorney comes first.

You can also try the free in-browser checker to see your highest-risk barriers before deciding anything.

---

The bottom line

A demand letter is a serious prompt, not a verdict. Don't ignore it, don't quietly hack at the site, and don't buy a widget that doesn't fix your code. Talk to an attorney, find out where you really stand (manual tests included), fix the real barriers, publish an honest statement, and — above all — keep a dated record of what you did. That documented good-faith effort, confirmed by a professional, is the credible path through this.

---

Sources: FTC final order requiring accessiBe to pay $1M (April 2025); Seyfarth / adatitleiii.com 2025 federal filing data (March 2026); DOJ ADA web-accessibility guidance; Deque automated-coverage report. Educational only, not legal advice.