- Dated documentation is what separates a defensible accessibility program from one that looks like it did nothing.
- If a claim arrives, preserve the before-state first, then remediate quickly.
- Mootness, good faith, and settlement follow-through all depend on records tied to specific issues and dates.
Every accessibility program needs a paper trail because the record is the defense: dated audits, remediation logs, monitoring cadence, and preserved snapshots are what prove you acted, when you acted, and what you actually fixed. Without documentation, even genuine remediation work is invisible when it matters most. This article is general information, not legal advice.
Why the Record Matters More Than the Work
Here’s the uncomfortable truth: fixing accessibility issues without documenting the fixes leaves you unable to prove anything later. Good faith is a documentation posture. An organized, ongoing program record, including audits, a monitoring cadence, training, and fixes over time, is what separates a company that can show its work from one that appears to have ignored accessibility entirely.
Small and medium businesses are now the primary targets of website accessibility claims. Large companies have mostly remediated. The vulnerability for SMBs is the awareness gap: high automated-scan error counts sitting in plain view. Plaintiff firms use free automated scanning tools as their triage layer to find targets. Scan-detectable errors are what get you discovered in the first place, which is why the two-step remediation sequence matters: eliminate scan-detectable issues first, then fix user flows second. The scan layer is how you get found. The flow layer, checkout, forms, account creation, is what a real claim gets built on.
Preserve First, Then Fix
If a demand letter or claim arrives, don’t act rashly. The sequence matters, and getting it backwards creates risk. Preserve the evidence, not the website. Capture a dated record of the site’s state at the time of the claim, then remediate quickly. Fixing the live site is not destroying evidence as long as the before-state was documented first. Remediating without a preserved before-state can look like scrubbing evidence, which is spoliation risk, and it leaves you unable to prove what the issues actually were.
- Capture the before-state: dated screenshots, crawls, archived copies, and scan results. This is the litigation hold obligation.
- Remediate quickly, logging each fix against a specific issue with a date.
- Retain both sets of records together so the before and after tell one story.
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 tied to specific issues prove what you fixed and exactly when.
What a Program Paper Trail Contains
Think of the paper trail as layers of dated proof, each answering a different question a lawyer, buyer, or regulator might ask.
| Record | Question It Answers | Cadence |
|---|---|---|
| (Manual) audit report | What issues existed and where | Annually or after major changes |
| Remediation log | What was fixed, by whom, and when | Continuous |
| Monitoring records | Whether new issues are being caught | Monthly or quarterly |
| Training records | Whether the team knows how to avoid regressions | Ongoing |
| Preserved snapshots | What the site looked like on a given date | At claim, at milestones |
A (manual) audit is the anchor document. Automated scans catch a minority of issues, so an audit conducted by human evaluators is what establishes the real baseline your remediation log builds on.
Settlements Are a Deadline-and-Evidence Problem
If you settle, the non-monetary terms are the hidden cost. Forced audits, quarterly user testing, and ongoing monitoring and reporting obligations can exceed the settlement figure. Plaintiffs re-check after settlement, and the 12 to 24 month compliance window carries breach risk. Meeting settlement terms means tracking progress against the agreed scope and holding proof you met it before the window closes.
And remember, accessibility is never one-and-done. Developers and content managers reintroduce issues with every new template, plugin, and content upload. A few habits keep the record alive:
- Date every audit, scan result, and fix.
- Tie each remediation entry to a specific issue, not a vague “improved accessibility” note.
- Keep monitoring on a set cadence and log the results even when they’re clean.
- Publish an accessibility statement with a contact method. It helps in negotiation and as good-faith evidence, but it’s not a defense, and phone support alone doesn’t cure inaccessibility.
If you need a (manual) accessibility audit to anchor your paper trail, contact us. We offer fast turnarounds, competitive pricing, and audit reports clear enough to build your documentation around.
