Guide
What is a VPAT? Accessibility conformance reports explained
Last updated: 29 June 2026
If a customer — especially a government agency, university, or large enterprise — has asked you for a "VPAT," it means they want documented proof of how accessible your product is before they buy. This guide explains what a VPAT is, when you need one, and how to approach it honestly. (General information, not legal advice.)
What a VPAT is
A VPAT (Voluntary Product Accessibility Template) is a standardized document, created by the Information Technology Industry Council (ITI), that a vendor fills out to state how their product conforms to accessibility standards — criterion by criterion. The completed document is often called an Accessibility Conformance Report (ACR), though most people just say "VPAT."
For each applicable requirement, you mark a conformance level — typically Supports, Partially Supports, Does Not Support, or Not Applicable — and add remarks explaining how (or where the gaps are).
The four editions
The template comes in editions so you can report against the standard your buyer cares about:
- WCAG edition — reports against WCAG (e.g. 2.1 / 2.2 A, AA).
- Section 508 edition — for US federal procurement (the Revised 508 Standards).
- EN 301 549 edition — the European standard (relevant to the EAA).
- INT (International) edition — combines all three, for selling across regions.
Since all of these build on WCAG, getting your WCAG conformance in order is the foundation for any edition. See WCAG vs EAA and Section 508 compliance for how the standards relate.
When do you need one?
- Selling to government — Section 508 procurement usually requires it.
- Selling to universities, healthcare, or big enterprises — increasingly part of vendor security/accessibility reviews.
- RFPs — many now ask for an ACR up front.
How to prepare one honestly
- Test first, then document. A VPAT is only as credible as the testing behind it. Audit against the relevant WCAG criteria before you fill anything in.
- Be accurate, not optimistic. Overclaiming "Supports" everywhere is risky — buyers re-test, and an inaccurate ACR damages trust. "Partially Supports" with honest remarks is fine and common.
- Cover the real product. Test the actual flows users rely on, not a marketing page.
- Keep it current. Re-issue after significant releases.
- Get expert review for high-stakes ACRs. A specialist or accessibility consultant adds credibility.
Where WCAGwise fits
WCAGwise helps with the testing that should come before a VPAT: Scan your site free to find machine-detectable WCAG issues and exactly where they are, so you know which criteria you "Support" vs "Partially Support." Then do manual testing for the rest. To be clear: WCAGwise is an audit aid — it does not generate or replace an official VPAT/ACR, and it's not a legal guarantee.