- A strong record is a dated, ongoing set of documents that shows your accessibility work over time, not a one-time report.
- The core pieces are audit reports, ACRs, remediation logs, and re-test results tied to specific dates and code changes.
- Tracking these documents in one place gives you evidence for buyers, regulators, and legal defense.
A strong record of digital accessibility compliance is a dated, organized collection of audit reports, ACRs, remediation logs, and re-tests that shows continuous effort over time. It is proof of what you tested, what you fixed, and when. One report sitting in a folder is not a record. A record is the paper trail.
Why a Record Matters More Than a Single Report
Accessibility is not a finish line. Your code changes, your content changes, and WCAG conformance can slip with every deploy.
A single audit captures one moment. A record shows a pattern of diligence, which is exactly what a buyer’s procurement team or a plaintiff’s attorney looks for.
Think of it as a mirror you check regularly, not a photo you took once. The value comes from consistency.
What Belongs in the Record
Every document you keep should tie back to a date and, ideally, a specific version of your site or app. The documents that form the backbone of a compliance record are these:
- Full (manual) audit reports, with the WCAG version and conformance level stated.
- ACRs (completed VPATs) that reflect your current accessibility, with real remarks in the explanations column.
- Remediation logs showing which issues were fixed, by whom, and when.
- Re-test or verification results confirming fixes held.
- User testing notes from people who rely on assistive technology.
- Policy documents, training records, and your public accessibility statement.
If your ACR has nothing in the remarks column, it carries little weight. The detail is what makes the record credible.
How to Build the Record Step by Step
Building a defensible record follows a repeatable order. Here is the sequence we recommend for creating and maintaining one:
- Conduct a full (manual) audit of your highest-traffic and highest-risk pages to establish a baseline.
- Request an ACR based on that audit so the findings are documented in a standardized format.
- Log every issue and assign it an owner and a target date.
- Remediate in priority order, fixing the most severe access problems first.
- Re-test the fixed items and record the verification date.
- Repeat on a schedule and after any significant code, design, or content change.
The last step is where most records fall apart. Set a cadence, quarterly or after major releases, and hold to it.
One-Time vs. Ongoing: What Each Approach Produces
The difference between a one-off audit and a maintained record is stark once you compare what each leaves you with:
| Factor | One-Time Audit | Ongoing Record |
|---|---|---|
| Coverage over time | Single snapshot | Continuous history |
| Legal usefulness | Limited, quickly dated | Shows good-faith diligence |
| Buyer confidence | Partial | Strong |
| Reflects current code | Only at test date | Updated after changes |
Keep It Organized
A record only helps if you can produce it fast. Storing your findings and tracking these documents over time in one place beats scattering PDFs across email threads.
Whatever system you use, keep documents dated, versioned, and searchable. When a buyer or attorney asks, you want to answer in minutes, not days.
Where to Start
If you don’t have a baseline yet, begin with a full (manual) audit and build outward from there. We deliver audits for most clients within 1 to 2 weeks and can produce the ACR to match.
Send us a message through our contact page and we’ll get you a quick quote with a clear timeline and competitive pricing.
For a closer look at this, see our overview of website compliance accessibility consultant.