- The record is the defense: dated audits, scan results, and remediation logs prove what you fixed and exactly when.
- Preserve a dated before-state first, then remediate fast, that sequence supports a mootness argument.
- An accessibility statement and contact method help as good-faith evidence, but they are not a legal defense.
Before an ADA website demand letter arrives, the documentation you want on hand is a dated, organized record of your accessibility work: audits, scan results, remediation logs, and proof of an ongoing program. That record is what separates a company that can show good faith from one that looks like it did nothing. This is general information about documentation and preparedness, not legal advice.
Why documentation matters more than the website itself
Plaintiff firms use free scan tools as a triage layer to find targets. High automated-scan error counts are how small and medium businesses get discovered in the first place.
Large companies have mostly remediated, so SMBs with an awareness gap are now the primary targets. The scan layer is how you get found. The record is how you respond.
Here is what a defensible documentation set includes:
- Dated audit reports tied to specific WCAG success criteria.
- Scan results captured over time, with the tool and date noted.
- Remediation logs that connect each fix to the issue it resolved.
- A monitoring cadence and training records for developers and content managers.
- Screenshots or archived copies showing the site’s state at a given date.
Preserve first, then fix
If a demand letter or claim shows up, don’t act rashly. The obligation is to preserve the evidence, not the website.
Capturing a dated record of the site’s state at the time of the claim is your litigation hold. Fixing the live site afterward is not destroying evidence, as long as the before-state was documented first.
Preserving a dated before-state before an ADA website claim involves a clear sequence:
- Capture screenshots, crawls, archived copies, and scan results dated to the claim.
- Store those records somewhere stable and unaltered.
- Remediate quickly, logging each change against the issue it addresses.
- Keep remediation records tied to specific issues and dates.
Remediating without a preserved before-state can look like scrubbing evidence, which carries spoliation risk. It also leaves you unable to prove what the issues actually were.
Fast remediation before a suit is filed supports a mootness argument, the claim can be argued moot if the relief sought has already been provided. But mootness only works with dated evidence: the preserved before-state plus remediation records prove what you fixed and when. Teams that keep a running history of tracking these documents over time are in a far stronger position when this happens.
How the pieces fit together
Here is how common documents map to what they support:
| Document | What it captures | What it supports |
|---|---|---|
| Dated audit report | Issues by WCAG criterion | Good-faith posture, remediation scope |
| Scan results over time | Machine-detectable error counts | Before-state evidence, discovery risk |
| Remediation log | Fixes tied to issues and dates | Mootness, follow-through proof |
| Archived copies/screenshots | Site state at a date | Litigation hold, spoliation defense |
| Accessibility statement | Commitment and contact method | Negotiation, good-faith evidence |
About the accessibility statement
A statement with a contact method helps in negotiation and as good-faith evidence. It is not a defense, and phone support alone doesn’t cure inaccessibility.
Treat it as one part of the record, not as protection on its own. The substance is the accessibility work behind it.
Ongoing posture is the point
Accessibility is never one-and-done. Developers and content managers reintroduce problems, so maintenance and monitoring keep the record current.
Good faith is a documentation posture. An organized, ongoing program record, audits, monitoring cadence, training, and fixes over time, is what stands up when questions come.
If a settlement follows, the non-monetary terms are the hidden cost. Forced audits, quarterly user testing, and ongoing reporting can exceed the settlement figure, and plaintiffs re-check during the 12 to 24 month compliance window. Meeting those terms is a deadline-and-evidence problem: track progress against the agreed scope and hold proof before the window closes.
Get your record in order
The best time to organize this documentation is before any letter arrives. If you want a dated audit and a record you can maintain, send us a message and we’ll respond quickly with your cost and timeline, usually within a few hours.
