- The fastest way to share proof of digital accessibility is a link to your ACR plus an accessibility statement.
- An ACR (a completed VPAT) documents your WCAG conformance; a statement makes it public.
- A live tracker lets buyers see current status instead of a stale PDF.
The easiest way to share proof of digital accessibility is to give people a single link to your ACR, backed by an accessibility statement and a dated audit report. That’s the whole move. One link, three documents behind it, and you never have to scramble when procurement asks.
Let’s be clear about what “proof” means here. It isn’t a badge or a widget. It’s documentation that shows an evaluation happened, when it happened, and what it found.
What actually counts as proof
Buyers and legal teams want records they can read, not marketing claims. A trust badge means very, very little on its own.
These are the documents that carry real weight when you share proof of digital accessibility:
- An ACR, which is a completed VPAT that reports your product’s conformance against WCAG.
- An accessibility statement published on your site that states your target conformance level and how to report issues.
- An audit report from a (manual) audit, showing findings and dates.
- A remediation record or status tracker so the reader sees progress over time.
Note: default to WCAG 2.1 AA or WCAG 2.2 AA as your target. That’s what most contracts and the European Accessibility Act (EAA) expect.
How the documents compare
Each document answers a different question, so knowing which to send saves everyone time. Here is how the main proof formats line up:
| Document | Best for | Format |
|---|---|---|
| ACR (completed VPAT) | Procurement and sales review | PDF or web page |
| Accessibility statement | Public visitors and legal notice | Live web page |
| Audit report | Engineering and remediation | PDF or spreadsheet |
| Live tracker | Ongoing, current status | Shareable link |
The steps to share it cleanly
Sharing proof of digital accessibility takes a short, repeatable setup:
- Conduct a (manual) audit of your site or app against your target WCAG version.
- Turn the findings into an ACR so buyers see conformance in a standard format.
- Publish an accessibility statement that links to the ACR and gives a contact route.
- Keep a live record for tracking these documents over time so the link never goes stale.
- Send one URL when asked, instead of emailing attachments back and forth.
Why one link? Because attachments age the moment you send them. A live page always reflects your current state, and that’s what makes it easy.
Where to host the proof
Your accessibility statement lives on your own domain, usually at a /accessibility path. That page is the hub. From there, link to the ACR and note when your last audit was conducted.
If you update often, a tracker keeps the statement honest. It shows a buyer that issues found in an audit are being worked, not ignored.
An ACR without detail in the remarks column is near worthless, so make sure whoever produces yours explains each finding. That’s the difference between proof someone trusts and a document they set aside.
Ready to produce your proof
We conduct fully (manual) audits and deliver the ACR, statement language, and audit report you need to share proof of digital accessibility with confidence. Turnarounds are fast and pricing is competitive.
Send us a message through our contact page and we’ll get you a quote right away, usually within a few hours.
For a closer look at this, see our overview of accessibility statement.
