VPAT and ACR explained: what they are and how to write an honest one
If a government agency, university or large company asks for your VPAT, here is what they mean, which edition to use, how to fill it in, and what buyers should look for when they receive one.
The short version
| VPAT | Voluntary Product Accessibility Template. A free, blank form from the Information Technology Industry Council (ITI) that turns accessibility standards into a list of criteria to test your product against |
|---|---|
| ACR | Accessibility Conformance Report. The VPAT after you have tested your product and filled it in. The ACR is the document a buyer actually receives |
| Current version | VPAT 2.5Rev, dated April 2025 |
| Four editions | WCAG (includes WCAG 2.2), 508 (Revised Section 508, the U.S. federal standard), EU (EN 301 549) and INT, which combines all three |
| Ratings | Supports, Partially Supports, Does Not Support, Not Applicable, each with a remarks column to explain the result |
| Who approves it? | No one. ITI does not review, approve or certify VPATs, and there is no pass or fail score. The vendor is responsible for the accuracy of what it writes |
General information, not legal advice. Check the buyer’s solicitation for the exact edition and any review requirements, and speak to an attorney about contract or compliance questions.
Why buyers ask for one
Before a government agency or large organization buys software, a website platform or a content tool, it needs to know whether people with disabilities can use it. An ACR is the standard way for a vendor to answer that question in a format buyers recognize. Federal buyers use ACRs during market research and when they evaluate proposals, and many state and local governments and universities follow the same practice in their own purchasing.
The ADA Title II web rule makes this practical for local governments. It covers content and tools provided through vendors and contractors, so a city that uses an online payment portal or a meeting-agenda tool is responsible for how that tool works for the public. Asking the vendor for an ACR is a sensible first step. For the rule itself, see the ADA Title II guide.
VPAT or ACR: what is the difference?
The VPAT is the empty template. When you test your product and fill in the results, the completed document is an ACR. People use the two terms interchangeably, which is why a request for “your VPAT” usually means “your completed report.” The name and form are registered service marks of ITI, so keep the template as published and do not alter it without ITI’s written permission.
Which edition should you use?
- WCAG edition: reports against the W3C Web Content Accessibility Guidelines, including WCAG 2.2. The usual choice for websites and web apps.
- 508 edition: reports against the Revised Section 508 standards. Federal solicitations usually ask for this one.
- EU edition: reports against EN 301 549, the European procurement standard.
- INT edition: covers all three in one document. It is longer, so use it only when buyers in more than one region ask for it.
Read the solicitation. If it names an edition, use that one.
How to write an honest ACR
1. Define the scope
Name the product, the exact version, the date and what you tested: the web app, the mobile app, the help documents, the support site. An ACR that covers only part of a product should say so.
2. Test every criterion
Run an automated scan first. It reliably finds things like missing alt text, unlabeled form fields, low contrast and invalid structure. Then test by hand, because many criteria cannot be decided by software. Use only a keyboard to reach every control. Try a screen reader on your main workflows. Zoom to 200% and check a phone-sized window. Ask whether the alt text is actually meaningful.
3. Rate each row and explain it
Use one of the four ratings for each criterion and write remarks that a buyer can act on. For Partially Supports and Does Not Support, say what fails, where, and what a user can do instead. Remarks are the most useful part of the report.
4. Date it, version it and keep the evidence
Keep your scan reports, test notes and screenshots with the ACR. Update it after each major release, because a report for last year’s version tells a buyer little about this year’s product.
Common mistakes
- Marking everything Supports. Almost no real product supports every criterion. A report with no gaps and no remarks looks untested.
- Vague remarks such as “meets this criterion.” Say how.
- A stale report written for an older version of the product.
- Leaving out parts of the product, such as the mobile app, PDFs, help center or checkout.
- Copying a competitor’s report or last year’s without retesting.
- Treating an automated scan as the whole test. A scan is evidence for some rows, not for all of them.
If you are the buyer: what to check
- Edition, version and date: is it the edition you asked for, for the product version you will actually receive?
- Scope: does it cover the parts of the product you will use?
- Remarks: are the Partially Supports rows explained, with workarounds?
- A plan: does the vendor say when known gaps will be fixed? Ask for it in writing.
- Your own test: try one or two key workflows with a keyboard before you rely on the report.
Free tools
The VPAT template is free from ITI and does not require membership. Section508.gov also offers an ACR Editor that produces reports in OpenACR, a portable machine-readable format. Neither one tests anything for you. They only structure the results.
Where WCAGScan helps
A WCAGScan report lists each issue with its WCAG success criterion, level and the affected element, and the checklist labels each item as automated, partly automated or manual. That gives you dated evidence for the criteria software can decide. The WCAGScan desktop app can draft a VPAT-style Accessibility Conformance Report from your scan results, so you start from real findings instead of a blank template. The draft is a starting point. You still need to test by hand, complete the remarks and review every rating before you send it to a buyer. See pricing.