An ADA website accessibility demand letter lands in your inbox. Before you respond, you need evidence — not assurances from your overlay vendor. Here is what to do, in order.
An ADA website accessibility demand letter is not a lawsuit — not yet. It is a formal notice, usually from a plaintiff's firm, asserting that your website fails to meet the accessibility standards required under Title III of the Americans with Disabilities Act and inviting you to resolve the matter before litigation is filed. The window between receiving that letter and the next escalation is short, and how you use it determines the strength of your position.
Nothing in this post constitutes legal advice. ADA demand letters carry real legal exposure. You should retain qualified counsel as soon as you receive one. The guidance here covers the evidence-gathering step that counsel will need — it does not substitute for an attorney-client relationship.
What an ADA website accessibility demand letter actually says
Most ADA website demand letters follow a recognizable structure. They cite a specific plaintiff who uses assistive technology, identify the website by domain, allege that one or more barriers prevented the plaintiff from using the site, and reference WCAG 2.1 Level AA as the applicable technical standard. Many also quote your own accessibility statement back at you — language your site published claiming compliance, in contrast to the barriers the letter alleges.
That last detail matters. When your accessibility statement promises WCAG 2.1 AA conformance and your page still fails on rules that WCAG 2.1 AA covers, the gap between the public claim and the live page is the core of the allegation. Plaintiff firms test sites before they send letters. They already have the evidence on their side. Your first task is to understand exactly what the page was doing at the time — not what your overlay vendor's dashboard reported.
The first 48 hours: what to do before responding
The period immediately after receiving a demand letter is the most consequential. Changes made to the site after a letter arrives can complicate the record — they can look reactive, and they do not retroactively address the conditions that existed when the plaintiff encountered the site. Before anything else is changed, preserve the current state of the pages named in the letter.
- Forward the letter to counsel immediately. Do not respond, negotiate, or publicly comment before counsel has reviewed it.
- Do not make accessibility changes to the named pages yet. Premature remediation can destroy the baseline you need to document.
- Capture a timestamped, independent record of the current page state — overlay on and overlay off — so the evidence is dated before any remediation begins.
- Pull your accessibility statement. Identify every specific claim it makes. These are the claims the letter will be measured against.
- Note which overlay vendor is installed and the version active on the date of the letter, if that information is recoverable from version control or deployment logs.
Understanding the evidence gap: claim versus page
Overlays like accessiBe and UserWay operate by injecting a JavaScript widget that modifies certain DOM properties at runtime. The vendor's dashboard may report a high conformance score. What matters legally is not the score — it is whether the actual rendered page, as experienced by an assistive-technology user, satisfies the rule named in the demand letter.
OverlayRiskWitness measures this by loading the page twice in a real browser: once with the overlay blocked entirely, and once with the overlay active. Both passes run the same automated WCAG engine — axe-core from Deque — against the rendered DOM. The diff between the two runs shows, rule by rule, what the overlay actually changed and what it left unchanged. If a rule fails with the overlay on, the vendor's script had the opportunity to fix it and did not.
The overlay runs but leaves core violations in place — missing form labels, insufficient color contrast, broken keyboard focus order. The accessibility statement still promises compliance. Plaintiff counsel tests the live page and finds the rules still failing with the overlay active. That is the gap the letter describes.
Gathering website accessibility lawsuit evidence
Website accessibility lawsuit evidence needs to satisfy two requirements that informal testing does not. First, it must be reproducible: the same inputs on the same page at a documented time should produce the same output. Second, it must tie the observation to the claim — not just "the page has contrast failures" but "the contrast rule failed with the overlay active on the page whose accessibility statement promises WCAG 2.1 AA conformance."
A Risk Packet from OverlayRiskWitness is designed around this structure. Each exhibit holds the site's public claim, the axe-core result for the rule that claim covers, the finding state (held up, did not hold up, or not testable), and a UTC timestamp with a DOM snapshot hash. For 5 to 10 pages the packet runs $49. That is the documentation layer your counsel needs to assess the letter — and to assess whether your overlay is providing the protection its vendor claims.
If counsel or your internal team needs a clearer map of which WCAG criteria can be documented immediately and which still require manual review, pair the packet with our WCAG 2.2 AA checklist for sites running an accessibility overlay. It gives everyone the same framework before statement language or remediation work starts to shift.
The free witness — one page, no signup required — gives you the first finding immediately. If you need coverage across the pages named in the demand letter, the Risk Packet covers the full set with the same evidence structure on every page.
What the Risk Packet gives your counsel
When your attorney is evaluating the demand letter, the first question is factual: does the page actually fail on the rules alleged, and if so, did the overlay you installed address them? The packet provides a vendor-independent answer to that question with a documented methodology. Counsel can take the packet's finding states and cross-reference them against the letter's specific allegations without having to run their own technical investigation.
It also establishes a date. If your site is later remediated, the packet documents the state that existed before remediation. That baseline is often the most important single document in what to do after an ADA demand letter arrives: it separates what was true when the plaintiff encountered the site from what became true after you responded.
Responding to an ADA demand letter: after the evidence
Responding to an ADA demand letter is entirely a matter for counsel, and the response strategy depends heavily on what the evidence shows. If the packet reveals that the overlay genuinely fixed the rules alleged and the findings are held up, that is a different position than if the overlay left the named rules failing. Neither outcome is something to address in a letter you draft yourself — but both are far easier for an attorney to act on when the evidence is already assembled.
What to do when you get an ADA demand letter, in plain terms: stop, preserve, document, then counsel. The demand letter names a window; the packet gives your attorney something to work with inside that window. OverlayRiskWitness does the evidence step. Everything after that belongs to your legal team.
Do not contact the plaintiff's firm, comment publicly, or remediate the named pages before your attorney has reviewed the letter and the evidence. The evidence-gathering step described here is preparation for that conversation — not a substitute for it.
Frequently asked questions
- What should I do first after receiving an ADA website demand letter?
- Do not respond on instinct or forward it straight to your overlay vendor. Preserve the letter, note the deadline, and gather timestamped evidence of how your live pages actually behave on the specific claims the letter raises — before you or your counsel reply.
- Is an overlay vendor confirmation enough to answer a demand letter?
- No. A vendor email asserting compliance is not evidence of how your page behaves. Plaintiffs test the live page. You need an independent, timestamped record of the same pages against your own published accessibility claims.
- Does OverlayRiskWitness provide legal advice on demand letters?
- No. OverlayRiskWitness produces evidence — paired axe-core results, your accessibility claim quoted back, finding states, UTC timestamps, and DOM snapshot hashes. Whether that evidence matters legally is a question for your counsel.