- A dated accessibility paper trail, audits, scans, fixes, and monitoring records, is what supports mootness and good-faith arguments if a claim comes.
- The sequence matters: preserve a dated before-state first, then remediate quickly.
- An accessibility statement and contact method help in negotiation as good-faith evidence, but they are not a defense.
An accessibility paper trail helps with ADA website defense because the record, not the website itself, is what proves what you fixed and exactly when. Mootness, follow-through, and good faith are only as strong as the dated documentation behind them. This article is general information about documentation and preparedness, not legal advice.
Why documentation is the defense
Large companies have mostly remediated, so small and medium businesses are now the primary targets. The vulnerability is the awareness gap: sites with high automated-scan error counts get found.
Plaintiff firms use free scan tools as a triage layer to find targets. Scan-detectable errors are what get you discovered in the first place. That is why the fix sequence and the record around it both matter.
An organized, ongoing program record is what separates a defensible company from one that looks like it did nothing. Good faith is a documentation posture, not a feeling.
What belongs in the paper trail
The strongest records are dated, specific, and tied to concrete issues rather than vague claims of effort. A useful accessibility paper trail includes these items:
- Audit reports and an ACR that show what was evaluated and against which version of WCAG.
- Scan results captured with dates, showing error counts before and after work.
- Remediation records tied to specific issues, so you can prove what changed and when.
- A monitoring cadence and training logs that show the program is ongoing.
- Screenshots, crawls, or archived copies that capture the site’s state at a point in time.
Keeping a running history of these documents over time is far easier than reconstructing it under pressure after a letter arrives.
How to prioritize remediation
There is a two-step order that reflects how risk actually works. Here is the sequence we recommend for remediation:
- Eliminate scan-detectable issues first, because the scan layer is how you get found.
- Fix real user paths second, because that is what a real claim gets built on.
Both steps generate records. Both records belong in the paper trail.
If a demand letter or claim arrives
Don’t act rashly. The core obligation is to preserve the evidence, not the website.
Capture a dated record of the site’s state at the time of the claim: screenshots, crawls, archived copies, and scan results. This is the litigation hold obligation.
Then remediate quickly. Fixing the live site is not destroying evidence as long as you documented the before-state first. Fast remediation before a suit is filed supports a mootness argument, because the relief sought may already have been provided.
Reverse the order and you have a problem. Remediating without a preserved before-state can look like scrubbing evidence, a spoliation risk, and leaves you unable to prove what the issues were. Preserve first, then fix.
Preserve first, then fix: the two orders compared
| Order | What you can prove | Risk |
|---|---|---|
| Preserve dated before-state, then remediate | What the issues were and when you fixed them | Supports mootness and good faith |
| Remediate without a preserved before-state | Little; no record of prior state | Looks like scrubbing evidence (spoliation) |
Settlement terms and the compliance window
The non-monetary terms are the hidden cost. Forced audits, quarterly user testing, and ongoing monitoring and reporting can exceed the settlement figure.
Plaintiffs re-check after settlement, so the 12 to 24 month compliance window carries breach risk. Meeting the terms is a deadline-and-evidence problem: track progress against the agreed scope and hold proof you met it before the window closes.
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 a phone line alone does not cure inaccessibility.
Treat the statement as one document in a larger record, not a shortcut around remediation.
Keep the record going
Accessibility is never one-and-done. Developers and content managers reintroduce access issues, so maintenance and monitoring matter as much as the initial fix.
If you want help building audits and a dated program record you can stand behind, reach out to us and we’ll get you a quick quote. We deliver audits for most clients within 1 to 2 weeks after they contact us.
For a closer look at this, see our overview of website defense attorneys.
