- Documentation withstands scrutiny only when it’s accurate, dated, and backed by a genuine (manual) audit, not a scan.
- An ACR, an accessibility statement, and remediation records work together as a single evidence trail.
- Vague or auto-generated records collapse the moment a demand letter or procurement reviewer asks for detail.
Accessibility compliance documentation withstands scrutiny when it accurately reflects the real state of your product and can be traced back to a fully manual evaluation. That means specifics, dates, and evidence, not marketing language. A record that says “we care about accessibility” proves nothing. A record that shows what was tested, what was found, and what was fixed proves everything.
Scrutiny comes from two directions: legal, in the form of a demand letter or lawsuit, and commercial, in the form of a procurement review. Both ask the same underlying question. Can you back this up?
What Scrutiny Actually Tests
Reviewers aren’t reading your documents for good intentions. They’re checking whether the paper matches the product. When it doesn’t, the documentation becomes a liability instead of a defense.
Here is what a serious reviewer looks for in your accessibility records:
- An ACR (completed VPAT) with real detail in the remarks and explanations column, not blank cells.
- A conformance target stated plainly, such as WCAG 2.1 AA or WCAG 2.2 AA.
- Dates showing when the evaluation happened and how recent it is.
- Evidence that testing was conducted manually, including screen reader and keyboard checks.
- A remediation history that shows issues moving from open to resolved.
If the remarks column is empty, the ACR is near worthless. A reviewer sees a template someone filled in to check a box.
The Documents That Work Together
No single file carries the weight. Your accessibility statement points the public to your position, your ACR records conformance in detail, and your remediation log shows the work behind both. Keeping tracking these documents over time is what turns a snapshot into a defensible trail.
| Document | What it proves | Common weak point |
|---|---|---|
| Accessibility statement | Your stated conformance target and contact path | Generic language with no target named |
| ACR (completed VPAT) | Item-by-item conformance against WCAG | Blank remarks column, no dates |
| Audit report | Findings from a manual evaluation | Actually a scan export relabeled as an audit |
| Remediation log | Issues found and how they were resolved | No history, nothing dated |
Why Scans Don’t Hold Up
A scan flags roughly a quarter of accessibility issues. It cannot judge whether a form is usable with a keyboard or whether an image’s alt text makes sense. So a document built on scan output looks thorough until someone asks how it was produced.
An audit report can be complete without a scan. Scan results are never complete. That difference is exactly what a reviewer probes. We use scans to complement our manual work, never to replace it.
Building Records That Last
Documentation that survives scrutiny is a process, not a one-time file. Setting up a defensible documentation trail takes a few clear steps:
- Have a fully manual audit conducted against a named WCAG target.
- Record every finding with enough detail to reproduce it.
- Complete your ACR from the audit results, filling the remarks column.
- Publish an accessibility statement that matches what the audit found.
- Log remediation as it happens and re-evaluate after major changes.
Re-evaluation matters because a site changes. New code, new design, and new content can introduce issues that dated documentation won’t cover. Records that stop a year ago invite the question of what happened since.
Where to Start
If your current documentation is thin, the fix starts with a real audit behind it. We only sell fully manual accessibility audits, and we deliver reports most clients can act on within one to two weeks. Contact us to find out your cost and timeline. We respond fast and our pricing stays competitive.
For a closer look at this, see our overview of compliance documentation tracking.
