- The record is the defense: dated documentation of audits, fixes, and monitoring is what separates a prepared company from one that looks like it did nothing.
- If a claim arrives, preserve a dated before-state first, then remediate quickly, because sequence matters.
- An accessibility statement and contact method help as good-faith evidence, but they are not a defense on their own.
An organized accessibility program record supports your defense because mootness, good faith, and follow-through are all only as strong as the dated documentation behind them. It is not a certificate and it does not make a claim disappear. What it does is prove what you did and exactly when you did it.
This is general information about documentation and preparedness, not legal advice. Talk to a qualified attorney about your specific situation.
Why documentation carries the weight
Accessibility is never one-and-done. Developers and content managers reintroduce problems every time they ship new code or upload new content. A record captures that ongoing work so it reads as a program, not a one-time scramble.
Good faith is a documentation posture. An organized, ongoing record shows a pattern of attention over time, which is a very different picture than a site that was ignored until a letter arrived.
A useful program record holds several kinds of dated proof:
- Audit reports tied to specific pages and issues.
- A monitoring cadence showing how often you re-check.
- Training given to developers and content teams.
- A running history of fixes with dates attached.
If a demand letter or claim arrives
Don’t act rashly. The first move is preservation, not repair. Capture a dated snapshot of the site’s state at the time of the claim so you can prove what the issues actually were.
Here is the order that keeps you out of trouble when a claim comes in:
- Preserve the evidence, not the website: capture dated screenshots, crawls, archived copies, and scan results of the current state.
- Remediate quickly once the before-state is documented, since fixing the live site is not destroying evidence.
- Keep remediation records tied to specific issues so you can show what changed and when.
Fast remediation before a suit is filed supports a mootness argument: the relief sought may already have been provided. But mootness only works with dated evidence. Remediating without a preserved before-state can look like scrubbing evidence and leaves you unable to prove what you fixed.
How the record maps to each stage
The table below breaks down what documentation supports at each point, from getting discovered through settlement follow-through.
| Stage | What the record supports | Key evidence |
|---|---|---|
| Before any claim | Good-faith posture | Audit history, monitoring cadence, training logs |
| Claim received | Litigation hold | Dated before-state: screenshots, crawls, scan results |
| Rapid remediation | Mootness argument | Fix records tied to specific issues, with dates |
| After settlement | Follow-through proof | Progress tracked against agreed scope inside the window |
Settlement follow-through is a deadline problem
The non-monetary terms are the hidden cost. Forced audits, quarterly user testing, and ongoing reporting obligations can exceed the settlement figure. Plaintiffs re-check after settlement, and the 12 to 24 month window carries breach risk.
Meeting those terms is a deadline-and-evidence problem: track progress against the agreed scope and hold proof you met it before the window closes. Keeping a structured history of these documents over time makes that far easier when a re-check comes.
Where an accessibility statement fits
An accessibility statement and a contact method help in negotiation and as good-faith evidence. They are not a defense, and phone support alone does not cure an inaccessible site. Treat the statement as one dated entry in the record, not as protection by itself.
Get help building the record
If you want a dated, organized program record built on real audit work, reach out to us and we’ll respond quickly with your cost and timeline.
For a closer look at this, see our overview of website compliance accessibility consultant.