- A mootness argument works only when you have dated evidence of the site’s state at the time of the claim, plus records showing exactly what you fixed and when.
- Preserve first, then remediate. Fixing the live site before capturing the before-state can look like scrubbing evidence.
- This is general information about a documentation posture, not legal advice.
Accessibility documentation supports a mootness defense by proving that the relief a plaintiff asked for was already provided, backed by a dated record of what the site looked like at the time of the claim and what you changed afterward. The documentation is the point. Without it, a mootness argument has nothing to stand on.
Note: This is general information about preparedness, not legal advice. Talk to your attorney about your specific situation.
What mootness actually depends on
A claim can be argued moot when the thing the plaintiff sought has already been delivered. In web accessibility terms, that means the issues named in the demand were remediated before a suit progressed.
But a verbal “we fixed it” carries no weight. What carries weight is a paper trail tied to specific issues, with dates.
Mootness only works with dated evidence. The preserved before-state plus remediation records tied to named issues prove both what you fixed and exactly when you fixed it.
Preserve first, then fix
When a demand letter or claim arrives, the first move is not to rush code changes. It’s to capture the site’s condition at that moment. This is your litigation hold obligation.
Preserving the evidence before you touch the live site takes a few concrete steps:
- Capture dated screenshots of the pages and flows named in the claim.
- Save a full crawl or archived copy of the site as it currently stands.
- Run and store scan results so the automated error counts are on record.
- Log the date and source of every artifact you collect.
Once the before-state is documented, remediate quickly. Fixing the live site is not destroying evidence as long as you captured what came before. Remediating without that preserved before-state is what creates spoliation risk, and it leaves you unable to prove what the issues even were.
Preserve versus remediate, side by side
The two actions serve different purposes, and the order between them is what protects you:
| Action | Purpose | Timing |
|---|---|---|
| Preserve the before-state | Proves what the issues were on the claim date | First, immediately on receiving a claim |
| Remediate the live site | Provides the relief the plaintiff sought | Second, after preservation |
| Record the fixes | Ties each change to a specific issue and date | During and after remediation |
Why the record is the defense
Good faith is a documentation posture. An organized, ongoing program record separates a company that looks prepared from one that looks like it did nothing.
That record covers more than a single incident. Accessibility is never one-and-done, because developers and content managers reintroduce problems over time, so an audit history, a monitoring cadence, and training logs all matter. Keeping a running history of your fixes and reviews, as we describe in our writing on tracking accessibility work over time, is what keeps mootness, follow-through, and good faith arguable.
A few documents make this posture concrete:
- An audit report identifying issues against WCAG conformance, so you know what to fix and can show your scope.
- Dated remediation records mapping each fix to a specific issue.
- Scan results captured at the time of any claim, since scan-detectable errors are how sites get discovered in the first place.
- A monitoring log showing you check the site on a regular schedule.
One caution: an accessibility statement and a staffed contact method help in negotiation and as good-faith evidence, but they are not a defense, and phone support alone does not cure an inaccessible site.
Get the documentation in place
The strongest posture is built before a letter ever arrives. A dated audit and an ongoing record give you something real to point to.
Contact us to find out your cost and timeline. We deliver fully (manual) audits for most clients within 1 to 2 weeks, and we’re happy to talk through your situation.
For a closer look at this, see our overview of compliance documentation tracking.
