- A dated record of your site’s state, plus remediation tied to specific issues, is what supports a mootness argument in an ADA website claim.
- Preserve the evidence first, then fix fast, remediating without a documented before-state can look like spoliation.
- An accessibility statement and contact method help as good-faith evidence, but they are not a defense.
Documentation helps because the strongest arguments in an ADA website claim, mootness and good faith, are only as strong as the dated records behind them. Without proof of what your site looked like and what you fixed, you have an argument with nothing under it. This is general information, not legal advice.
Why small and medium businesses get targeted
Large companies have mostly remediated. Small and medium businesses are now the primary targets, and the vulnerability is the awareness gap.
Plaintiff firms use free automated checkers as a triage layer to find targets. High scan-detectable error counts are what get a site discovered in the first place.
Free scanning tools of the kind plaintiff firms rely on flag these issues in this order:
- Scan-detectable errors, missing alt text, unlabeled form fields, low contrast, that surface on a quick automated pass.
- User-path problems, the harder issues a real claim gets built on once you’re already discovered.
That ordering is also how you should prioritize remediation: eliminate scan-detectable issues first, then fix user paths second. The scan layer is how you get found, the user-path layer is what a claim gets built on.
What to do if a demand letter arrives
Don’t act rashly. The instinct to quietly fix everything and move on is the exact instinct that can hurt you later.
Preserve the evidence, not the website. Capture a dated record of the site’s state at the time of the claim before you change anything.
Here is what a preserved before-state should include:
- Dated screenshots of the pages named in the claim.
- A crawl or archived copy of the site as it existed that day.
- Scan results showing the automated error counts at that moment.
- Notes tying each captured issue to where it appears.
Then remediate quickly. Fixing the live site is not destroying evidence as long as the before-state was documented first. If you’re tracking these documents over time, the capture and the fix records live in one place.
How the record supports mootness and good faith
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 sequence matters: preserve first, then fix. Remediating without a preserved before-state can look like scrubbing evidence, that’s spoliation risk, and it leaves you unable to prove what the issues actually were.
The preserved before-state plus remediation records tied to specific issues prove what you fixed and exactly when. That pairing is the whole argument.
| Document | What it shows | What it supports |
|---|---|---|
| Dated before-state capture | Site condition at time of claim | Litigation hold, spoliation defense |
| Remediation records tied to issues | What was fixed and when | Mootness argument |
| Ongoing program log (audits, monitoring, training) | Sustained effort over time | Good-faith posture |
| Accessibility statement and contact method | Willingness to assist | Good-faith evidence in negotiation |
Settlement terms and the compliance window
The non-monetary terms are the hidden cost. Forced audits, quarterly user testing, and ongoing monitoring obligations can exceed the settlement figure.
Plaintiffs re-check after settlement. The 12 to 24 month compliance window carries breach risk, so 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.
What an accessibility statement actually does
An accessibility statement with a contact method helps in negotiation and as good-faith evidence. It is not a defense, and a phone line alone doesn’t cure an inaccessible site.
Treat the statement as one entry in an organized program record, not as a shield. Good faith is a documentation posture: audits, monitoring cadence, training, and fixes logged over time are what separate a defensible company from one that looks like it did nothing.
The record is the defense
Accessibility is never one-and-done. Developers and content managers reintroduce problems, so maintenance and monitoring keep the record current instead of frozen at one audit.
Mootness, follow-through, and good faith all rest on dated documentation. If you want help building an audit and monitoring record you can stand behind, reach out to us and we’ll respond fast with a clear quote and timeline.
For a closer look at this, see our overview of ada compliance.
