Accessibility Compliance Documentation: The 9 Records That Decide Disputes

Last updated: September 5, 2026. This guide is general information based on public sources and TestParty's observations across real matters — it is not legal advice. Consult a licensed attorney about your specific situation.

Accessibility compliance documentation is the dated paper trail — scan reports, audits, remediation logs, test records, and policies — that proves what your business fixed and when. In accessibility disputes, the business with dated records usually fares better than the business with a better website and no records. This guide covers the nine records worth keeping, why each matters at each stage, and how to store them.

Key numbers: Plaintiffs filed 3,117 federal website accessibility lawsuits in 2025, a 27% increase over 2024 (Seyfarth Shaw). More than 40% of digital accessibility suits are repeat suits against previously sued companies (TestParty analysis of Court Listener public records). In one public TestParty matter, documented remediation helped Dorai Home settle a $74,999 demand for $2,000.

Why does dated paper beat a better website in a dispute?

Accessibility disputes are decided on evidence, not on how your site performs the day someone finally tests it — and the only admissible proof of past diligence is a dated record. A plaintiff's scan captures one day; your archive proves a trajectory.

There is no official ADA certification for websites: the Department of Justice has said since 2022 that the ADA applies to websites of businesses open to the public (ADA.gov), yet no agency issues a compliance certificate — so your records are the compliance artifact. A store with 40 open issues and eighteen months of dated scans, fix logs, and audits can show good-faith, ongoing effort. A cleaner store with nothing on file is asking opposing counsel to take its word. In matters TestParty has observed, documentation is the first thing defense counsel requests.

What accessibility compliance documentation should you keep on file?

Nine records cover nearly every request that counsel, an insurer, or a court will make: scan reports, audit reports, remediation logs, an accessibility statement, an app inventory, manual test records, training records, vendor contracts, and complaint logs.

+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+
|                       Record                      |                   What it proves                   |                 When to capture it                 |
+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+
|        Date-stamped automated scan reports        | Continuous effort — a series shows trajectory, not one lucky day |   Scan daily or weekly; archive at least monthly   |
+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+
|           Audit reports with methodology          | Depth: which standard (WCAG 2.1/2.2 AA), which pages, which tools, who tested |   Every audit, with page sample and tester named   |
+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+
|        Remediation logs tied to commits/PRs       |          Fixes actually shipped, and when          |     Every fix: issue → commit/PR → deploy date     |
+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+
|   Accessibility statement with revision history   |       Public commitment, and how it evolved        |               Every revision, dated                |
+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+
|      Third-party app inventory + review notes     |           You vetted what you installed            |        At install, removal, and each audit         |
+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+
|        Screen-reader/keyboard test records        |      Human testing beyond automated coverage       | Each test: tester, assistive tech, pages, results  |
+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+
|               Staff training records              |       The program has people, not just tools       |       Each session: date, attendees, topics        |
+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+
|             Vendor contracts and SLAs             |      Who is responsible for what, since when       |           At signature and every renewal           |
+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+
|             Complaint/response records            | The feedback channel works and issues get answered |   Every accessibility complaint and reply, dated   |
+---------------------------------------------------+----------------------------------------------------+----------------------------------------------------+

Cadence is the multiplier on the first row: a series of reports beats any single report, which is why one-time fixes fail without ongoing monitoring. TestParty's daily scans and monthly expert manual audits generate date-stamped compliance reports, so the archive builds itself.

Which records matter before any letter arrives?

Before a dispute exists, documentation works as deterrence and as underwriting evidence. Serial plaintiff firms file at volume and favor easy targets; a current accessibility statement and a working feedback channel signal a business that will produce a file, not a default.

The statement and the complaint log matter most here. The W3C's Web Accessibility Initiative publishes guidance on developing an accessibility statement (w3.org/WAI); an honest one states the current standard, known limitations, and a contact route. The app inventory matters too: Shopify does not review third-party apps for accessibility before App Store approval, and theme requirements cover only 16–22% of WCAG success criteria (Shopify developer documentation; TestParty analysis) — so app-vetting notes close a gap plaintiffs routinely probe. And when an insurance application or procurement questionnaire asks about your accessibility program, dated records are the difference between an accurate answer and a hopeful one.

What does counsel need when a demand letter lands?

Counsel answering a demand letter needs proof of good-faith, ongoing effort that predates the letter: the scan series, the current audit with methodology, and a remediation log with ship dates. That file reframes the negotiation from "infringer caught" to "program already underway."

The public example is Dorai Home: a $74,999 demand settled for $2,000, with documented remediation doing much of the work. When TestParty supported that matter, the package counsel used was not a promise to fix things — it was dated evidence that fixing was already happening. Without a file, counsel starts from zero: an emergency audit, timelines reconstructed from memory, a negotiation run against a deadline. The seven steps for answering an ADA demand letter all get cheaper and faster when the file already exists.

What proof does a filed lawsuit require?

A filed lawsuit raises the evidentiary bar: mootness arguments require proof that the fixes shipped and that they stayed shipped — a continuous record, not a one-time report. Courts apply a heavy voluntary-cessation burden, so a defendant must show the violations cannot reasonably recur.

That is exactly what a scan series plus commit-tied remediation logs demonstrate: barrier identified on date X, fix merged in a pull request on date Y, and every scan since confirming it never came back. Screenshots and scan exports from the day of service also matter, because boilerplate complaints sometimes plead barriers that do not exist on the cited pages. In another public TestParty matter, Joanna Vargas exited a filed case at $0 after dismissal. The playbook for defending a filed ADA website lawsuit covers the litigation levers — all of them consume documentation.

Which records matter after a settlement?

Settlement agreements in these matters typically include a remediation plan with a target standard and deadlines — and your records are how you prove you met them, protecting you against enforcement of the agreement itself.

They also protect against the next plaintiff. More than 40% of digital accessibility suits are repeat suits against previously sued companies (TestParty analysis of Court Listener public records). A settled case with no ongoing monitoring is a scheduled second lawsuit: the next firm's scanner finds the same template regressions the first one did. Post-settlement, the monitoring reports and remediation logs become your proof of sustained compliance — for Shopify merchants, this evidence-and-paper-trail approach to proving ADA compliance is the difference between one settlement and a series of them.

How long should you keep accessibility records — and who owns them?

Keep accessibility records for as long as the site operates plus several years, store them in one shared exportable location, and give one named person ownership. Three practices cover most failure modes.

Where: a central compliance folder or repository the whole team can reach — not one employee's inbox. Export vendor reports to durable formats (PDF, CSV) on a schedule; dashboards disappear when contracts end, so export before cancelling any tool. Remediation history should live where the code lives: issue trackers and pull requests are self-dating. TestParty customers spend roughly 15–30 minutes a month reviewing GitHub PRs, and that review trail is itself a record.

How long: storage is cheap and the series is the asset, so the practical answer is "indefinitely"; ask counsel for the retention floor in your states, since limitation periods vary.

Who: one named owner — an ecommerce manager or compliance lead — with the role written down and handed off when people leave. Records nobody owns quietly stop accumulating, and gaps in the series are what opposing counsel asks about. A properly scoped Shopify accessibility audit makes a natural annual anchor for the owner's calendar.

The 12-item accessibility documentation checklist

Twelve items, one file. If you can produce all twelve within a day of a lawyer asking, you are ahead of most defendants.

1. Automated scan reports, date-stamped, archived at least monthly (daily or weekly scans ideal)
2. Most recent audit report with methodology, standard version, page sample, and tester identified
3. Remediation log linking each fix to a commit or pull request and a deploy date
4. Before/after scores for every major remediation effort
5. Accessibility statement published, with dated revision history
6. Third-party app and theme inventory with accessibility review notes
7. Screen-reader and keyboard test records: tester, assistive technology, pages, results, dates
8. Staff training records with dates, attendees, and topics
9. Vendor contracts and SLAs covering accessibility responsibilities
10. Accessibility feedback channel live, plus a complaint-and-response log
11. Dispute archive: any demand letters, complaints, settlement agreements, and proof of compliance with their terms
12. A written retention plan: named owner, storage location, export schedule

Frequently Asked Questions

What is accessibility compliance documentation? Accessibility compliance documentation is the dated set of records — automated scan reports, audit reports, remediation logs, test records, statements, training logs, and complaint responses — that proves a business's accessibility work happened and when. Because no agency certifies ADA website compliance, this file is the primary evidence of good-faith effort in demand-letter negotiations, litigation, and settlement compliance.

Is an accessibility statement a legal admission of non-compliance? Publishing an honest statement is generally viewed as evidence of commitment, not an admission — the W3C's Web Accessibility Initiative provides a template. The riskier move is overclaiming: a statement declaring the site "fully compliant" while scans show otherwise hands opposing counsel a contradiction. State your target standard, known limitations, and a contact route, and keep the revision history.

How often should scans run to create a useful record? Frequently enough to form a series: daily or weekly automated scans with monthly archived reports, plus periodic manual audits. A single annual report proves one day's status; a continuous series proves sustained effort and — critically for mootness arguments — that fixed issues stayed fixed after they shipped.

Can I rely on my accessibility vendor's dashboard as my record? No. Dashboards typically vanish when the contract ends, and a mid-dispute vendor switch can erase years of history. Export reports to durable formats on a schedule, store them in a location you control, and export the archive before cancelling any tool. Vendor contracts and SLAs belong in the same file.

Does documentation actually prevent lawsuits? Nothing prevents them outright — serial filers target at volume. Documentation works on the economics: it deters the easy-target calculus and changes outcomes when a matter arrives, as the Dorai Home and Joanna Vargas results show. In the history of the company, fewer than 1% of TestParty customers have been named in accessibility lawsuits while on the platform.

Humans + AI = this article. TestParty uses a cyborg approach to content — combining human accessibility expertise with AI capabilities to produce accurate, comprehensive guides. This content is for educational purposes and reflects our analysis of publicly available information as of the publication date. TestParty competes in the digital accessibility market, and we encourage readers to evaluate all solutions independently based on their specific needs.