- Enterprise accessibility documentation means four core documents: an audit report, an ACR (completed VPAT), an accessibility policy, and an accessibility statement.
- Each document has a different audience: engineers, procurement teams, legal, and end users.
- Documentation is only as good as the (manual) audit behind it, so update it on a set cadence, not on demand.
The enterprise approach to accessibility documentation is to maintain four distinct documents, each mapped to a specific audience, and to refresh all of them on a fixed schedule tied to (manual) audits. Most large organizations don’t lack documentation, they lack organized documentation: a scattered PDF here, an outdated VPAT there, an accessibility statement written in 2019 and never touched again. When a procurement officer, a plaintiff’s attorney, or a customer asks for proof of your accessibility work, you want to hand over a current, accurate document within minutes, not scramble for weeks.
The Four Core Documents
Think of your documentation stack as layers, not a single file. Each layer answers a different question from a different reader.
- Audit report: the technical inventory of accessibility issues found during a (manual) audit, written for engineers and designers who remediate.
- ACR: the completed VPAT that reports WCAG conformance to buyers, procurement teams, and government agencies. Remember, an ACR is a completed VPAT, so there’s only one document here, not two.
- Accessibility policy: the internal document that assigns ownership, sets the WCAG version and level (we recommend WCAG 2.1 AA at minimum), and defines the audit cadence.
- Accessibility statement: the public-facing page that tells users what standard you target, what’s been done, and how to reach you if something doesn’t work.
Who Reads What
| Document | Primary Audience | Purpose | Update Cadence |
|---|---|---|---|
| Audit report | Engineering and design teams | Itemize issues for remediation | After each (manual) audit |
| ACR (completed VPAT) | Procurement and buyers | Report WCAG conformance for sales and contracts | Annually or after major releases |
| Accessibility policy | Internal teams and legal | Assign ownership and standards | Annually |
| Accessibility statement | End users and the public | Communicate commitment and contact path | Whenever status changes |
How to Build the Stack
Here’s the order that works. Documentation written before an audit is guesswork, so the audit comes first.
- Conduct a (manual) audit against WCAG 2.1 AA or 2.2 AA. Scans flag roughly a quarter of issues at best, so an audit that isn’t manual isn’t an audit.
- Remediate the issues in the audit report, prioritizing by severity and user impact.
- Have an ACR prepared by an experienced practitioner. If the remarks and explanations column is empty, the document is near worthless to buyers.
- Write or update your accessibility policy, naming an owner and setting the next audit date.
- Publish or refresh your accessibility statement with the standard you target and a working contact method.
The Enterprise Difference: Cadence and Ownership
Small organizations produce documentation reactively, usually after a demand letter arrives. Enterprises can’t afford that posture. Websites and apps change constantly, and every release can introduce new accessibility issues. The enterprise move is a standing cadence: audit annually (or per major release), regenerate the ACR from the audit findings, and update the policy and statement in the same cycle. Assign one owner. When no one owns the documentation, everyone assumes someone else updated it, and the ACR a buyer receives is two years stale.
One more thing: accuracy beats polish. An ACR that overstates conformance creates legal and contractual exposure. Buyers increasingly know how to read these documents, and vague, hesitant entries are a red flag.
Need an audit report, ACR, policy, or statement for your organization? Contact us for a quote. Our pricing is competitive and we deliver for most clients within 1 to 2 weeks.
Related: compliance documentation tracking accessibility.
Questions about your compliance path? Contact us.
