What Happens After You Receive an ADA Website Demand Letter

When an organization receives an ADA website demand letter, the moment feels urgent in a way that distorts judgment. The letter is not yet a lawsuit. No complaint has been filed. No court is involved. But neither is it something that can be safely ignored or quickly settled without consequence. Many organizations misread the letter as either a hollow threat to be dismissed or a shakedown to be resolved with a check and a promise. Both responses are mistakes, because both misunderstand what the letter actually signals and what the examining party will look for next.

What a Demand Letter Is Actually Asserting

A demand letter alleges that a website contains barriers that denied access to a disabled user. It identifies specific deficiencies — often drawn from automated scanning or manual testing — and asserts that those deficiencies constitute a violation of applicable law. It is an assertion, not a finding. No court has evaluated the claim. No adjudicative body has weighed in.

But embedded in that assertion is an implied question the organization must be prepared to answer: what did you know, when did you know it, and what did you do about it. The letter does not ask this question directly. It does not need to. The question becomes operative the moment the organization is on notice that someone is examining its accessibility posture. The letter initiates scrutiny. The organization's compliance history — or its absence — is what that scrutiny will find.

What Plaintiff Counsel Evaluates Before Filing

Before deciding whether to file suit, plaintiff counsel assesses the strength of the potential case. This assessment is not primarily based on whether barriers exist on the website. Barriers can be verified independently through automated tools and manual testing, and in most cases, some barriers will be present. The more consequential question is whether the organization has a defensible record of accessibility effort or whether its compliance history is effectively blank.

Organizations with continuous monitoring records, documented remediation histories, and attributed decision-making present a harder litigation target. They can demonstrate that accessibility was an institutional concern before the letter arrived, that findings were identified and tracked, that remediation was assigned and completed by specific individuals, and that the process was ongoing rather than reactive. This does not make them immune to claims, but it materially changes the risk calculus for a plaintiff considering whether to file.

Organizations that have no records, or records that consist only of point-in-time audit reports conducted months or years apart, present an easier target. The absence of continuous documentation suggests that accessibility was not an operational priority. A single audit report, however thorough, demonstrates a moment of attention. It does not demonstrate a pattern of diligence. The decision to file or settle is frequently a record availability question before it is a legal question.

Why a Remediation Promise Is Not a Defense

The most common organizational response to a demand letter is to commit to fix the issues identified. The organization engages an accessibility vendor, commissions a new audit, and begins remediating the specific barriers cited in the letter. This response is understandable. It demonstrates good faith and forward motion. But it is structurally insufficient as a defense against the claim being asserted.

A promise to remediate does not address the period during which barriers allegedly existed. It does not establish whether the organization was previously aware of those barriers. It does not demonstrate institutional attention to accessibility over time. It addresses the future while leaving the past entirely undefended.

Plaintiff counsel is not primarily interested in what the organization will do next. They are interested in what it did before the letter arrived. A commitment to improve is not evidence of prior effort. It is, in many cases, an implicit acknowledgment that prior effort was absent. The remediation promise closes the gap going forward but leaves the historical gap — the gap that the demand letter is actually targeting — fully exposed.

What a Defensible Record Actually Looks Like

A defensible record is not a collection of reports assembled after a demand letter arrives. It is not a folder of PDF audits conducted at irregular intervals. It is not a statement of policy or a commitment to conform to WCAG guidelines at some future date.

A defensible record is a continuous history created in the ordinary course of operations. It documents when scans were run and what they found. It records how findings were logged and assigned. It tracks what remediation steps were taken and by whom. It preserves how those steps were reviewed and verified and when issues were formally closed.

Each element of this history must be attributable to specific individuals, dated at the time of action, and preserved in a form that cannot be selectively edited after the fact. The integrity of the record depends not only on its content but on its continuity and immutability. A record that can be retroactively altered is not a record that can withstand scrutiny.

The record is defensible not because it shows a perfect compliance history. No organization maintains a website with zero accessibility issues at all times. The record is defensible because it demonstrates that the organization was paying attention, identifying issues as they arose, responding appropriately to what it knew, and maintaining institutional accountability for the process. The standard is not perfection. The standard is demonstrable, ongoing effort.

The Period Before the Letter Is What Matters

Organizations that receive a demand letter and begin building accessibility records at that point have understood the problem too late. Not too late to improve their posture going forward — that work is always worth doing — but too late for the period in question. The compliance record that matters in response to a demand letter is the record that existed before the letter arrived.

Records created after notice of a claim carry a different evidentiary weight than records created in the ordinary course of business. They may reflect genuine effort, but they cannot demonstrate prior awareness or prior action. They document response, not practice. The distinction matters because the claim being asserted is not that the organization failed to respond to the letter. The claim is that barriers existed, that users were denied access, and that the organization either knew or should have known.

Organizations that have maintained continuous, attributed, and immutable records of accessibility monitoring and remediation are in a fundamentally different position than those who have not. The difference is not in what they can claim. It is in what they can demonstrate.

A demand letter is an early moment in a process that may or may not escalate. What determines the trajectory is rarely the severity of the barriers alleged. It is the depth and credibility of the organization's compliance history. That history cannot be created in response to scrutiny. It must exist before scrutiny arrives.