A VPAT (Voluntary Product Accessibility Template) is a standardized form vendors use to document how their tech product meets accessibility standards.
The resulting filled-out document is the ACR (Accessibility Conformance Report), a detailed report showing support for criteria like WCAG or Section 508.
You use the VPAT (template) to create the ACR (final report).
The terms are often used interchangeably, but technically, the VPAT is the tool, and the ACR is the outcome/report itself.
When a buyer asks for a VPAT, they usually want the completed ACR to evaluate the product's accessibility compliance.
VPAT isn't only digital; it's a standard template for documenting accessibility for Information and Communication Technology (ICT), which includes software, websites, mobile apps, hardware, and even support documentation, focusing on conformance to digital standards like WCAG and Section 508.
While centered on digital accessibility, it provides a structured way to report on the accessibility of various ICT products, helping buyers assess conformance for procurement.
A VPAT standardizes the reporting of accessibility for a broad range of ICT products, moving beyond just web pages to encompass the entire digital ecosystem a user interacts with, making it a crucial tool for procurement in government and business.
Websites & Software: The most common use, detailing how well they meet standards.
Mobile Apps: Accessibility features in applications.
Hardware: Physical technology products.
Electronic Content & Documentation: Accessible PDFs, manuals, and help files.
Standards: Reports conformance to Section 508, WCAG, and EN 301 549.
ICT is a broad term for all technologies used to handle information, including hardware (computers, phones, networks), software, and services that help us create, process, store, share, and access digital data and communicate.
It's the backbone of the digital world, covering everything from the internet and smartphones to cloud computing, e-commerce, and digital learning tools, integrating computing with telecommunications to connect people and machines.
Key Components of ICT:
Hardware: Computers, servers, mobile devices, networks, routers, satellites.
Software: Operating systems, applications, management tools.
Services: Internet access, telecommunications, data management, e-commerce.
What it is: A blank, standardized template created by the Information Technology Industry Council (ITI).
Purpose: To guide vendors in assessing and describing their product's digital accessibility against specific standards (like Section 508, WCAG, EN 301 549).
Analogy: Think of it as a blank report card for digital accessibility features.
What it is: The completed VPAT document, filled with specific findings about a product's digital accessibility.
Purpose: To provide transparency to buyers (government, businesses) about a product's digital accessibility status, highlighting what's supported, partially supported, or not supported.
Key Info: Includes details on criteria, workarounds, and blockers, allowing for informed procurement decisions.
We follow a structured five-step process to ensure your Accessibility Conformance Report is accurate, helpful, and reflects the best version of your product:
What is a VPAT?
A Voluntary Product Accessibility Template (VPAT) is a standardized form used to document how accessible a digital product is. It helps buyers understand if your software meets accessibility standards.
What is an ACR?
An Accessibility Conformance Report (ACR) is the completed version of a VPAT. The VPAT is the blank template; the ACR is the final, signed document describing your product's specific compliance level.
Why does my company need an ACR?
Most public sector organizations and large corporations require an ACR during procurement to prove your commitment to accessibility.
Which standard do you test against?
We typically test against WCAG 2.1 or 2.2 (Level A and AA) and include Revised Section 508 standards for U.S. federal requirements.
Does an ACR mean my product is "certified" accessible?
Not exactly. An ACR is a snapshot of your product's current state. It is a transparent disclosure of what works and what needs improvement, rather than a "pass/fail" certificate.
How long does the process take?
The timeline depends on complexity, but a standard audit and report typically take 2 to 4 weeks.
What do you need from me to get started?
The first step is a brief introductory conversation to discuss your product's scope. After that, we'll need access to your testing environment and a list of core user workflows.
Who performs the audit?
We conduct the audit using a mix of automated tools and manual testing to ensure we catch barriers that software alone might miss.
What happens if my product has accessibility "fails"?
That is perfectly normal. We will document these in a prioritized report. You then have an optional window to fix these issues so the final ACR reflects your improvements.
How often should I update my ACR?
You should update your ACR after major releases or redesigns. Many companies choose to refresh their report once a year.
Can you help me fix the issues you find?
Our reports include technical guidance for your developers. While we don't write the code, we do provide a verification spot-check for any fixes you make during our process to ensure they meet the standards.
Is the final report public?
That is up to you. You can post it publicly for transparency or provide it only upon request during the sales process.
Whether you need government contracts or just a better product, a VPAT ensures digital accessibility for everyone - not just a checkbox.
First step is a conversation!
