Download the template from ITI’s official VPAT page. That page supplies the current templates and instructions. This guide helps you prepare the information; it does not replace ITI’s reporting form.
Choose the edition around the request
On narrow screens, scroll the table horizontally to read all columns.
| Edition | Main reporting focus | Question to resolve before testing |
|---|---|---|
| WCAG | Web Content Accessibility Guidelines | Which WCAG version and conformance level does the buyer request? |
| 508 | Revised Section 508 Standards | Which product components and applicable ICT provisions must be evaluated? |
| EU | EN 301 549 | Which standard version and requirements does the buyer specify? |
| INT | Combined international coverage | Does the request call for several standards in one report? |
ITI explains that different editions incorporate different WCAG versions. Do not assume that choosing a more recent template automatically changes the standard specified by the customer. Confirm the reporting edition and standards together.
Prepare a product record
Identify the product being sold, its version or release, the modules included, and the configurations that matter to the buyer. A platform may include separate experiences for administrators, end users, and people reading exported documents. Make those boundaries explicit.
Prepare a short scope record with the product owner before the evaluation. Include authenticated access, relevant user roles, third-party components, supported configurations, and exclusions. Where the buyer expects broader coverage than existing evidence provides, identify the additional work rather than silently stretching the report’s scope.
Assemble the evidence before completing the tables
Bring together findings, test environments, evaluation dates, and any verified remediation results. An internal engineering team, accessibility specialist, or external evaluator may contribute evidence. The report needs to describe the work actually performed.
The government’s ACR preparation guide explains the title-page information and reporting columns. Keep the product description and evaluation-methods section precise enough that a reviewer understands what the ratings refer to.
On narrow screens, scroll the table horizontally to read all columns.
| Working material | How it supports the report |
|---|---|
| Product and scope record | Defines the version, functionality, and boundaries being described |
| Evaluation notes | Explains the methods and configurations used |
| Issue records | Identifies barriers and affected functionality |
| Retest evidence | Shows which corrections have been verified |
| Open questions | Identifies missing information that must be resolved before finalizing claims |
Write useful remarks
A buyer needs to understand where a limitation occurs and what it affects. A remark such as “some issues remain” provides little help. A more useful structure identifies the affected function, describes the barrier, and explains any verified alternative.
For example, an illustrative remark might say: “The [control] in [workflow] does not expose [required information] in [tested configuration]. Other evaluated instances [verified behavior].” Complete each field from the evaluation. Do not copy an example into a report without confirming that it describes the product.
Use the template’s conformance terms according to their definitions. Ratings summarize evidence for a criterion; they should not be selected to make the document look more favorable.
Check the completed report
Before sharing the ACR, verify that the product version, scope, methods, ratings, and remarks agree. Resolve unexplained blanks and confirm that any excluded functionality is described clearly. Follow the chosen template’s completion instructions and preserve its required structure.
Keep a record of who approved the report and which evidence supports it. When a product release changes the evaluated behavior, review whether the report still describes what customers receive.
Review a completed example
CompliCorp’s sample VPAT/ACR shows anonymized ratings and explanatory remarks. It is a reporting example, not a blank template or evidence about your product.
If you need help connecting a customer request to evaluation and reporting, explore our VPAT testing and ACR services. Share the product version, requested standards, existing evidence, and procurement deadline to define the engagement.
VPAT is a registered trademark of the Information Technology Industry Council.