What Is a VPAT? A Complete Guide for Business Owners
If you’re in the business of developing software, applications, and other products with online functionality, and want to comply with Section 508 requirements, there are a few things you should know about VPAT compliance.
In this guide, we outline everything you need to know about VPAT accessibility conformance, including how VPATs apply to your business, why they matter, and how to complete them accurately.
Let’s dive right in and start with the basics.
What Is a VPAT?
Maintained by the ITIC, a VPAT is a standardized framework used to evaluate how accessible a digital product or service is.
Organizations use VPATs to document accessibility support against standards such as:
- WCAG
- Section 508
- EN 301 549
The document helps buyers, procurement teams, and partners assess whether a product meets their accessibility requirements. It also demonstrates transparency and a commitment to creating more inclusive digital experiences.
VPAT vs ACR: What’s the Difference?
Although the terms “VPAT” and “ACR” are often used interchangeably, they are not technically the same thing.
A VPAT (Voluntary Product Accessibility Template) is the standardized template developed by the Information Technology Industry Council. Companies use this framework to evaluate and document how their products align with accessibility standards.
An ACR (Accessibility Conformance Report) is the completed document created using the VPAT template. It contains the actual accessibility findings, including which criteria a product supports, partially supports, or does not support.
In simple terms:
- The VPAT is the template
- The ACR is the finished report
This distinction matters because many organizations ask vendors for a “VPAT” when they are actually requesting the completed ACR document.
Understanding the difference can help reduce confusion during procurement processes and accessibility reviews, especially when accessibility documentation is required for enterprise or government contracts.
Who Needs a VPAT?
VPATs were originally most closely associated with organizations selling products or services to U.S. federal agencies. Today, VPATs are useful for any organization that wants to demonstrate a stronger commitment to accessibility conformance and enhance the credibility of its digital offerings.
Any organization that develops or sells digital products can benefit from VPAT accessibility conformance.
VPATs are commonly created for:
- Software and SaaS platforms
- Websites and web applications
- Mobile apps
- Digital documents and PDFs
- Interactive kiosks and voice response systems
- Devices such as tablets and smartphones
A VPAT is especially valuable for organizations working with government entities, educational institutions, healthcare providers, and large enterprises, where accessibility documentation is often required during vendor evaluations.
It’s also important to understand that a VPAT does not act as a certification of full accessibility compliance. Instead, it documents a product’s current level of accessibility support against standards such as Section 508 or WCAG. This transparency helps buyers understand where a product meets requirements, partially supports them, or may still have accessibility gaps.
Why VPATs Are Important
For many organizations, a VPAT helps demonstrate a proactive approach to accessibility and can reduce legal and reputational risk associated with inaccessible digital experiences. They can also strengthen trust with customers and improve competitiveness during procurement processes, where accessibility documentation is increasingly expected.
Most importantly, VPATs give buyers the information they need to make informed comparisons between products and choose solutions that better support inclusive access for all users.
VPAT 2.5 Sections Explained
VPAT 2.5 is structured around different accessibility standards and regulations. When completing a VPAT, organizations select the edition that best matches the markets, industries, or compliance requirements relevant to their product.
The four main VPAT 2.5 sections are:
Section 508
Section 508 is a U.S. federal accessibility law that requires federal agencies to use information and communication technology (ICT) that is accessible to people with disabilities.
Organizations that sell digital products or services to the U.S. government are often asked to provide VPAT documentation showing how their offerings align with Section 508 requirements.
Revised Section 508
The Revised 508 standards are the updated version of the original Section 508 requirements. Introduced to modernize accessibility regulations, the revised standards align much more closely with the Web Content Accessibility Guidelines (WCAG) 2.0.
Today, most modern VPATs referencing Section 508 are based on the revised standards rather than the original version.
WCAG
The Web Content Accessibility Guidelines (WCAG) are internationally recognized standards for digital accessibility, developed by the World Wide Web Consortium.
WCAG focuses on making websites, applications, and digital content more accessible for people with disabilities. The guidelines are organized around four core principles: content should be:
- Perceivable
- Operable
- Understandable
- Robust
Many organizations use the WCAG VPAT edition because WCAG standards are widely referenced in global accessibility legislation and procurement requirements.
EN 301 549
EN 301 549 is the European accessibility standard for ICT products and services. It was developed to support accessibility requirements across the European Union.
This standard applies to a wide range of digital technologies, including:
- Websites
- Software
- Mobile apps
- Hardware
- Telecommunications products
Organizations operating in European markets or working with public sector entities in the EU may need VPAT documentation aligned with EN 301 549 requirements.
Which VPAT Section Should You Use?
The correct VPAT accessibility section depends on where your organization operates and who your customers are.
For example:
- U.S. federal vendors often focus on Revised Section 508
- Global digital products commonly align with WCAG
- European public sector procurement may require EN 301 549 documentation
Many organizations complete VPATs that address multiple standards at the same time to simplify accessibility reporting across different markets.
How to Get a VPAT for Accessibility Conformance
A VPAT template can be downloaded directly from the Information Technology Industry Council website and used to evaluate your products against major accessibility standards.
However, completing a VPAT accurately requires more than simply filling in a document. The process involves testing digital products against detailed accessibility criteria and understanding how different standards apply to websites, software, mobile apps, and other ICT products.
Unless your team already has experience with accessibility testing and compliance reporting, working with an accessibility professional is often the better option. Incorrect or incomplete VPATs can create confusion during procurement reviews and may expose organizations to unnecessary legal or reputational risk.
The VPAT accessibility conformance process typically involves three key stages:
- Conducting an accessibility audit. Evaluate your digital products or services against relevant standards such as WCAG or Revised Section 508 to identify accessibility barriers and compliance gaps.
- Improving accessibility compliance. Address identified issues wherever possible to improve the overall accessibility of the product before documenting results.
- Completing the VPAT report. Record the findings in the appropriate VPAT template, including areas of full support, partial support, exceptions, and additional accessibility notes.
If you need assistance with the VPAT certification process, AccessibilityChecker.org can help. Click here to find out more.
How to Fill Out a VPAT
As mentioned above, you can either hire an expert to assist you with the VPAT accessibility process or you can do it yourself.
- A VPAT should only be completed by someone who is familiar with accessibility laws and standards for high accuracy.
- A VPAT contains template guidelines and instructions. Be sure to check for any guidelines that are specific to your type of organization. This could include using specific terminology.
- Along with indicating whether a product meets a particular accessibility requirement, it’s also important to provide a description that backs this claim. Be detailed, but to the point.
- If there are any criteria that your product does not meet, be honest and outline the steps your organization is taking to rectify any shortfalls where possible.
- If product features or functionality change, it’s important to update your VPAT and include a revised evaluation date.
- Consider posting your completed VPAT on your website, while also ensuring the document is accessible to online users.
- Remove any VPAT document instructions from the template before submitting it.
Conclusion
If accessibility and legal compliance are important to your organization, VPATs make a lot of sense. What’s more, it can help your ICT products and services stand out – clients will always value honesty and transparency.
And if you don’t have enough accessibility knowledge to complete a VPAT yourself, there are experts available to assist you with this process.
VPAT FAQs
A VPAT (Voluntary Product Accessibility Template) is a document used to show how a digital product or service conforms to accessibility standards such as Section 508, WCAG, and EN 301 549.
VPATs are commonly required for vendors selling digital products or services to U.S. federal agencies, educational institutions, healthcare organizations, and large enterprises.
A VPAT is the blank accessibility reporting template, while an ACR (Accessibility Conformance Report) is the completed document containing the actual accessibility evaluation results.
The VPAT template itself is free to download. However, professional accessibility audits and VPAT completion services can range from approximately $1,500 to $10,000+ depending on the size and complexity of the product.
VPAT 2.5 supports several major accessibility standards, including Section 508, WCAG 2.0/2.1/2.2, and EN 301 549.