- Real proof of accessibility compliance is documentation, not a badge or a scan score.
- The core records are a manual audit report, an ACR (completed VPAT), and an accessibility statement.
- Proof has to be dated, accurate, and kept current as your site changes.
You establish proof of accessibility compliance by producing documentation that shows what was tested, how it was tested, and what the results were. That means a manual audit report against WCAG, an ACR (a completed VPAT), and a public accessibility statement. A scan result or a self-declared badge is not proof. It’s a claim.
Here’s the thing buyers, courts, and procurement teams all want: evidence someone qualified evaluated your product against a real standard. So let’s walk through what that evidence looks like.
What Actually Counts as Proof
Proof is a record. It names the standard, the scope, the method, the date, and the findings. Without those pieces, a document means very, very little.
The strongest records answer the questions a skeptical reader asks: which pages, which WCAG version, tested by whom, and when.
These are the documents that establish proof of accessibility compliance:
- A manual audit report against WCAG 2.1 AA or WCAG 2.2 AA, listing issues by success criterion with locations and remediation guidance.
- An ACR, which is a completed VPAT that reports your conformance in a standardized format buyers recognize.
- An accessibility statement published on your site describing your conformance target, known issues, and a contact method.
Notice what’s not on that list: a scan score. A scan flags roughly a quarter of issues and can’t judge things like keyboard operability or screen reader output. Use scans to complement a manual audit, never to replace one.
Audit Report vs. ACR vs. Statement
These three documents do different jobs, and you generally want all three. One reports the technical findings, one communicates conformance to buyers, and one speaks to the public.
| Document | What it proves | Primary audience |
|---|---|---|
| Manual audit report | Exactly which WCAG criteria pass or fail, and where | Your dev and design teams |
| ACR (completed VPAT) | Overall conformance in a standardized format | Procurement and enterprise buyers |
| Accessibility statement | Your commitment, target, and contact path | The public and users |
The Order of Operations
Proof is built in sequence. You can’t write an accurate ACR before you know your findings, and you can’t know your findings without a real evaluation.
Building a defensible record of accessibility compliance follows a clear order:
- Conduct a manual audit against your chosen WCAG version and level.
- Remediate the issues the audit surfaced, prioritizing the most severe first.
- Re-test to confirm fixes and document the closed items.
- Produce an ACR reflecting the current, accurate state.
- Publish an accessibility statement and note the date of your last evaluation.
An ACR is only worth something if it’s accurate. If the remarks and explanations column is empty, the document is near worthless. Our breakdown of what makes a template turn into a real conformance report covers why that column carries the weight.
Keeping Proof Current
Proof is a snapshot, not a permanent certificate. Every code edit, design change, or content upload can introduce new issues, so a document from two years ago proves very little about today.
These practices keep your proof from going stale:
- Re-audit after any significant redesign or platform migration.
- Date every document so readers know its currency.
- Log issues and fixes over time; our approach to watching these records evolve makes that manageable.
- Update your accessibility statement whenever your conformance status changes.
What Doesn’t Establish Proof
Let’s be clear about the shortcuts that don’t hold up. A self-issued badge proves nothing because no one checked it. A scan report proves partial coverage at best. And an automated fix layer isn’t evidence of conformance, nor does it survive scrutiny from a buyer who knows what to ask.
Certification is another common confusion. There’s no official government seal for websites, so no vendor can hand you one. What you can hold is credible, dated documentation from a qualified evaluation, and that’s what carries weight.
Get Documentation You Can Stand Behind
If you want proof that holds up with buyers and reviewers, start with a manual audit and build the ACR and statement from its findings. We only sell fully manual audits, and we deliver for most clients within 1 to 2 weeks. Contact us for a quick quote on your cost and timeline.
