Reviewed November 5, 2026

After the Demand Letter: The Remediation Paper Trail That Matters

Responding to an ADA Title III demand letter about a website is stronger when the business can document remediation: a dated accessibility audit, a log tying each barrier to a fix and a completion date, and retesting that confirms the fix in production. In litigation and settlement discussions, the paper trail is often as important as the fixes themselves, because it shows good faith and a working process.

The demand letter arrives with a list of barriers, a deadline, and a settlement figure. The panicked store fixes the homepage over a weekend, tells the lawyer it is handled, and then discovers the question that actually gets asked: show us. Dates, audit, tickets, retests. The fix existed. The evidence did not.

Accessibility work that cannot be documented is, in a dispute, nearly indistinguishable from accessibility work that was never done. Build the paper trail while you build the fixes.

What the record should contain

Start with the audit: dated, scoped to templates and key flows rather than a single automated scan, and listing barriers in WCAG terms with success criteria cited. Automated scans find a fraction of issues, and Seyfarth Shaw's ADA Title III tracking commentary has made the point for years that scan only compliance claims collapse quickly. A record that begins with an honest audit reads differently from one that begins with a widget receipt.

Then the remediation log: each barrier, the owner, the fix description, the date it shipped to production, and the retest result. Screenshots before and after are cheap and persuasive. So is the commit or release reference. The log does not need to be beautiful. It needs to be contemporaneous, because records written the week of a response carry a smell everyone in the room recognizes.

What this does not do

Documentation does not erase liability for the period the barriers existed, and no honest advisor will promise that a good log ends a case by itself. Plaintiffs' firms filing serial Title III suits, the pattern Seyfarth's annual filings analysis counts in the thousands, choose targets partly on how a business responds. A documented, dated remediation program is the strongest available signal that this defendant fixes things systematically, which changes settlement posture even when it changes nothing about the past.

It also does not substitute for the fixes. A beautiful log describing barriers that a five minute keyboard test still finds is worse than no log, because it converts a capability problem into a credibility problem. Paper follows production, never the reverse.

Keep the trail alive after the letter closes

Most remediation programs die at settlement. The log stops, the theme updates, an app injects a new barrier, and eighteen months later a second letter arrives at a business that now has to explain why its documented process produced no documents for a year and a half.

Fold the record into operations: an accessibility check line in the release process, a quarterly sample audit of the main templates, and the log updated as fixes ship. The cost is an hour a quarter. The asset is a continuous record that any future letter meets on day one, which is when records matter most and when they can no longer be created honestly.

Frequently asked questions

Does fixing my website after a demand letter end the case?

Not automatically. Plaintiffs can still pursue claims about the period of non compliance and often seek fees and a compliance commitment. Prompt, documented remediation usually improves settlement terms and reduces exposure, which is why speed plus records is the standard advice.

What should a remediation log include?

Each barrier found, the WCAG criterion it maps to, who owns the fix, what changed, the date it reached production, and how it was retested. Before and after evidence such as screenshots strengthens each entry. Keep entries dated as work happens.

Is an automated scan report enough documentation?

No. Automated tools detect only a subset of barriers, commonly estimated at a third or less of issues, and miss keyboard, focus, and many screen reader problems entirely. A credible record pairs scan output with manual testing of the key flows.

How long should I keep accessibility records?

Keep them as a standing business record, at least several years, and keep adding to them as the site changes. A continuous trail is worth far more in a second dispute than a single burst of documentation from the first one.