What Is a VPAT? A Complete Guide for Business Owners
A Voluntary Product Accessibility Template (VPAT®) is a standardized document used to communicate how well a digital product conforms to recognized accessibility standards such as WCAG, Section 508, and EN 301 549. It helps procurement teams evaluate accessibility before purchasing software while giving vendors a consistent way to report their testing results.
If you’re buying or selling software, especially to government agencies, educational institutions, or large enterprises, you’re probably going to need one.
In this guide, we’ll explain what a VPAT is, when it’s needed, what’s included, how it’s created, and how to request one.
What Is a VPAT?
A Voluntary Product Accessibility Template (VPAT®) is a standardized document that helps software vendors communicate how well their digital products conform to recognized accessibility standards. Developed by the Information Technology Industry Council (ITI), the VPAT provides a consistent framework for documenting accessibility features, identifying areas where a product meets or falls short of specific requirements, and sharing this information with customers during the procurement process.
Today, VPATs are widely used by government agencies, educational institutions, healthcare organizations, and private enterprises around the world when evaluating software, websites, and other digital products. Rather than relying on marketing claims, procurement teams can review a VPAT to better understand a product’s accessibility before making a purchasing decision.
A VPAT is typically completed after a thorough accessibility audit and accessibility testing have been carried out. During this process, accessibility specialists evaluate the product against standards such as the Web Content Accessibility Guidelines (WCAG), documenting the results for each applicable success criterion. This helps create a transparent record of the product’s current level of accessibility.
It’s important to understand that a VPAT is not a certification or official approval of accessibility. Instead, it is a reporting template that describes how a product performs against specific accessibility requirements at a particular point in time. The accuracy and usefulness of a VPAT depend on the quality and scope of the accessibility evaluation behind it.
For this reason, organizations should ensure their VPAT is based on comprehensive testing that includes both automated tools and manual evaluation. A well-prepared VPAT not only supports procurement requirements but also demonstrates a genuine commitment to creating accessible digital experiences and maintaining ongoing WCAG compliance as products evolve.
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.
Which VPAT Template Should I Use?
Not all VPATs are the same. The Information Technology Industry Council (ITI) offers different VPAT editions to align with specific accessibility standards and regulatory requirements. Choosing the right template depends on where your product will be sold and the accessibility requirements of your customers.
Many organizations, particularly those operating internationally, complete a VPAT that covers multiple accessibility standards. This allows them to provide a single document that meets the needs of government agencies, enterprise customers, educational institutions, and organizations in different regions.
The table below outlines the main VPAT editions and when they’re typically used.
| VPAT Edition | Accessibility Standards Covered | Best For |
|---|---|---|
| WCAG | Web Content Accessibility Guidelines (WCAG) | Commercial websites, web applications, and SaaS products |
| Section 508 | U.S. Section 508 accessibility requirements | Vendors selling to U.S. federal government agencies |
| EN 301 549 | European accessibility requirements | Organizations operating within the European Union or supplying public sector bodies |
| International (INT) | WCAG, Section 508, and EN 301 549 | Global software vendors serving customers across multiple regions |
WCAG VPAT
If your organization develops websites, web applications, or Software-as-a-Service (SaaS) products, the WCAG edition is often the most appropriate choice. It reports how well your product conforms to the Web Content Accessibility Guidelines (WCAG), the internationally recognized standard for digital accessibility that forms the basis of many accessibility laws and policies worldwide.
For many private-sector organizations, demonstrating WCAG conformance is a key part of meeting customer expectations and supporting inclusive digital experiences.
Section 508 VPAT
Organizations that sell software or digital services to U.S. federal government agencies will often need a VPAT that addresses Section 508 requirements. Section 508 is a federal law requiring government agencies to procure and use accessible information and communication technology.
Even if you don’t work directly with government customers, some state agencies, educational institutions, and government contractors may also request Section 508 accessibility documentation during procurement.
EN 301 549 VPAT
If your organization serves customers in Europe, the EN 301 549 edition may be required. EN 301 549 specifies accessibility requirements for information and communication technology throughout the European Union and supports legislation such as the European Accessibility Act (EAA).
As accessibility regulations continue to evolve across Europe, many organizations are using this VPAT edition to demonstrate that their digital products align with applicable European standards.
International (INT) VPAT
Organizations with customers in multiple countries often choose the International (INT) VPAT. This edition combines several major accessibility standards, including WCAG, Section 508, and EN 301 549, into a single template.
Using an International VPAT can simplify procurement by providing enterprise customers, government agencies, and multinational organizations with one comprehensive accessibility report instead of separate documents for each standard.
Can You Cover Multiple Standards in One VPAT?
Yes. In fact, many software vendors complete a combined VPAT that evaluates their product against multiple accessibility standards simultaneously. Because WCAG forms the foundation of both Section 508 and EN 301 549 in many areas, assessing all applicable standards within a single report can reduce duplication while making it easier for customers to review accessibility information.
Before selecting a VPAT template, consider where your product is sold, the industries you serve, and any regulatory requirements your customers must meet. Choosing the appropriate edition helps ensure your accessibility documentation is relevant, accurate, and useful throughout the procurement process.
Understanding VPAT Conformance Ratings
A VPAT doesn’t simply state whether a product is “accessible” or “not accessible.” Instead, it evaluates each applicable accessibility requirement individually using standardized conformance ratings. These ratings help procurement teams, accessibility professionals, and prospective customers understand how well a product meets specific accessibility criteria and where improvements may still be needed.
The most common conformance ratings you’ll find in a VPAT are:
| Conformance Rating | Meaning |
|---|---|
| Supports | The product fully meets the accessibility requirement. |
| Partially Supports | The product meets the requirement in many situations but has known limitations or exceptions. |
| Does Not Support | The product does not meet the accessibility requirement. |
| Not Applicable | The requirement does not apply to the product or feature being evaluated. |
| Not Evaluated | The criterion was not assessed during the accessibility evaluation. |
Supports
A Supports rating indicates that the product satisfies the accessibility requirement as expected. Users with disabilities should be able to access and interact with the relevant feature without encountering barriers related to that specific criterion.
Partially Supports
A Partially Supports rating means the product meets the requirement in some areas but has identified accessibility issues that prevent full conformance. For example, most forms may be fully accessible, while a small number of legacy pages or features still require remediation.
This is one of the most common ratings in VPATs because many products are continually evolving and improving their accessibility over time.
Does Not Support
A Does Not Support rating indicates that the product fails to meet the accessibility requirement. This doesn’t necessarily mean the entire product is inaccessible, but it does identify an area where users may encounter barriers and where remediation is needed.
Not Applicable
Some accessibility criteria simply don’t apply to every product. For example, a requirement relating to multimedia captions wouldn’t be relevant for software that doesn’t contain audio or video content. In these cases, the evaluator will mark the criterion as Not Applicable.
Not Evaluated
A Not Evaluated rating means the accessibility criterion wasn’t included in the assessment. While this may occur in limited circumstances, organizations should use this rating sparingly, as leaving criteria unevaluated can reduce confidence in the overall VPAT and raise additional questions during procurement.
Remarks and Explanations
While the conformance rating provides a useful summary, the Remarks and Explanations column is often the most valuable part of a VPAT. This section gives evaluators the opportunity to explain why a particular rating was assigned and provide important context that can’t be captured by the rating alone.
For example, the remarks may describe which parts of the product conform to a requirement, identify known accessibility limitations, explain how certain features can be accessed using assistive technologies, or note whether an issue only affects specific browsers, operating systems, or workflows. Where accessibility issues exist, the remarks may also outline available workarounds or indicate that improvements are planned in a future product release.
Rather than focusing solely on whether a criterion is marked as Supports or Partially Supports, procurement teams should carefully review the accompanying remarks. They often provide the detailed information needed to determine whether identified accessibility limitations are likely to affect the organization’s users or intended use cases.
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.
Common Mistakes When Creating and Using a VPAT
A VPAT is only as valuable as the information it contains.
Below are some of the most common issues to watch for.
Using an Outdated VPAT Template
Accessibility standards and reporting requirements evolve over time, and so do VPAT templates. Using an outdated version may mean your report doesn’t align with the latest accessibility standards or procurement expectations.
Before creating a VPAT, verify that you’re using the most recent template published by the Information Technology Industry Council (ITI). This helps ensure your documentation reflects current accessibility requirements and is more likely to be accepted by customers.
Reporting on an Older Product Version
A VPAT should always identify the specific product version that was evaluated. If significant updates have been released since the assessment, the report may no longer accurately reflect the product’s current accessibility.
When reviewing a VPAT, compare the documented product version and evaluation date with the version you’re planning to purchase or deploy. If they don’t match, ask the vendor whether a more recent accessibility evaluation is available.
Relying Only on Automated Accessibility Testing
Automated accessibility testing tools are an important part of the evaluation process, but they cannot identify every accessibility issue. Many aspects of digital accessibility, such as keyboard usability, screen reader compatibility, meaningful alternative text, focus management, and logical reading order, require manual testing and human judgment.
A high-quality VPAT should be based on a combination of automated scans, manual accessibility testing, and, where appropriate, testing with assistive technologies. Relying solely on automated tools can result in an incomplete or misleading accessibility report.
Failing to Update the VPAT After Major Product Releases
Software is constantly evolving, with new features, interface changes, and functionality introduced through regular updates. Any significant product changes can affect accessibility, meaning an older VPAT may no longer represent the current user experience.
As a best practice, organizations should review and update their VPAT whenever major releases introduce new functionality or make substantial changes to the user interface. Regular reviews also demonstrate an ongoing commitment to accessibility rather than treating compliance as a one-time exercise.
Omitting Explanations for Partially Supported Criteria
A conformance rating alone rarely tells the full story. If a criterion is marked as Partially Supports, the accompanying remarks should explain which parts of the product conform, where accessibility limitations exist, and whether workarounds or remediation plans are available.
Providing clear, detailed explanations helps procurement teams make informed decisions and demonstrates transparency. Without this context, customers may assume the accessibility issues are more significant than they actually are.
Assuming a VPAT Guarantees Legal Compliance
One of the biggest misconceptions is that having a VPAT automatically means a product complies with accessibility laws or regulations. In reality, a VPAT is a reporting document—not a certification, legal guarantee, or official endorsement.
A completed VPAT simply documents the results of an accessibility evaluation at a specific point in time. Accessibility requirements continue to evolve, products change, and new issues can emerge after updates. Maintaining accessibility therefore requires ongoing testing, remediation, and regular reviews to help ensure continued conformance with standards such as WCAG and other applicable regulations.
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
Is a VPAT legally required?
Not usually. A VPAT isn't required by law in most cases, but it's frequently requested during software procurement, particularly by government agencies, educational institutions, and large enterprises. Providing one can help demonstrate your product's accessibility and streamline the purchasing process.
Does every software company need a VPAT?
No. However, if you sell software to organizations that prioritize accessibility or are subject to accessibility regulations, having a VPAT can give you a competitive advantage and make procurement easier.
How often should a VPAT be updated?
A VPAT should be reviewed and updated whenever significant changes are made to your product that could affect accessibility. Even if no major changes occur, it's good practice to revisit the document periodically to ensure it remains accurate and reflects the latest accessibility standards.
Can I create my own VPAT?
Yes, but it should be based on a thorough accessibility evaluation. While any organization can complete a VPAT, it's most credible when it's prepared using comprehensive automated and manual testing performed by experienced accessibility professionals.
Does a VPAT guarantee ADA or WCAG compliance?
No. A VPAT is a reporting document, not a certification. It describes how a product conforms to specific accessibility standards at the time it was evaluated but doesn't guarantee compliance with laws such as the ADA or confirm complete WCAG conformance.
How long does it take to complete a VPAT?
The timeframe depends on the size and complexity of the product, as well as its current level of accessibility. Completing a VPAT can take anywhere from a few days for a simple application to several weeks for large or complex software requiring extensive testing.
Should a VPAT be publicly available?
Not necessarily. Some organizations publish their VPATs on their websites to demonstrate transparency, while others provide them only upon request during the procurement process. The right approach depends on your organization's policies and customer requirements.