The short answer
VPAT stands for Voluntary Product Accessibility Template. It is a free document template published by the Information Technology Industry Council (ITI), a technology trade association. It lists accessibility requirements as rows in a table, with columns for how well your product meets each one and your explanation.
Once a vendor fills in the template for a specific product, the finished document is called an Accessibility Conformance Report, or ACR. In practice, most people say “VPAT” for both the blank template and the completed report. When a buyer asks for “your VPAT,” they mean your completed ACR.
Why buyers ask for one
Public-sector agencies, universities, healthcare systems and many large companies have to consider accessibility when they buy software. In the United States, Section 508 of the Rehabilitation Act requires federal agencies to consider the accessibility of the technology they procure, and many state agencies and universities have similar policies. The VPAT gives every vendor the same format to describe their product, so a procurement team can compare answers side by side.
That is why the request usually arrives mid-deal, next to the security questionnaire. Someone in purchasing or IT accessibility has a checklist, and an ACR is one of the boxes.
Which edition do you need?
ITI publishes the VPAT in four editions. They share the same structure but cover different standards:
- WCAG edition. Reports against the Web Content Accessibility Guidelines (WCAG 2.0, 2.1 or 2.2). This is the most common request for web and mobile software.
- 508 edition. Reports against the Revised Section 508 standards used by US federal agencies. Those standards incorporate WCAG 2.0 Level A and AA for web content and software, plus extra sections for hardware, documentation and support services.
- EU edition. Reports against EN 301 549, the European accessibility standard for ICT.
- INT edition. Combines all three, for vendors selling into several markets with one document.
If your buyer didn’t specify, the WCAG edition at Level AA is the usual starting point for software, because the other standards build on WCAG for web and app content. The current template version is VPAT 2.5.
What’s inside an ACR
- Product information: name, version, report date, a short description, and a contact for accessibility questions.
- Evaluation methods: how you checked the product, such as keyboard testing, screen reader checks, or automated tools.
- Applicable standards: which standard and levels the report covers.
- Conformance tables: one row per success criterion, each with a conformance level (Supports, Partially Supports, Does Not Support or Not Applicable) and remarks.
- Legal disclaimer: optional, written by the vendor.
The tables are where buyers spend their time. A row that says “Partially Supports” with a clear remark is more useful to them than a wall of “Supports” with no explanation. See how to choose conformance levels for examples.
What a VPAT does and doesn’t prove
A VPAT is a self-description. ITI does not review, approve or certify completed reports, and there is no official VPAT registry. The document is only as accurate as the people who wrote it.
Honesty matters more than a perfect score. Buyers expect gaps. What hurts trust is a report that claims full support and then fails a five-minute keyboard check.
Who usually writes it
At a small or mid-size software company, the ACR usually lands on a product manager or engineering lead, with input from whoever knows the front end best. Larger companies often hire an accessibility consultancy to audit the product and write the report, which means a quote, a testing engagement and a wait before anything reaches the buyer.
If your team already knows the product well, a credible self-reported VPAT is achievable in an afternoon. Our five-day plan for responding to a VPAT request walks through it.
VPAT Draft Desk asks one plain question per criterion and sets your answers into a report procurement teams know how to read.
Start your VPATQuick answers
Is a VPAT required by law?
The template itself isn’t required by any law. Buyers request it because their own procurement rules require them to evaluate accessibility, and the VPAT is the common way to do it.
How often should we update it?
Whenever a release meaningfully changes the interface, and at least once a year. Buyers look at the report date and product version on the cover.
Can we send a VPAT for an older version?
You can, but say so on the cover and expect questions. A report for the version the buyer will actually use is far more persuasive.