All About VPATs and ACRs - What is a VPAT, and why does it matter?
People with disabilities deserve full access to digital spaces. Yet many websites still create unnecessary barriers. A Voluntary Product Accessibility Template (VPAT) is a formal document that records how well your website or digital product meets recognized accessibility standards.
VPATs are typically completed by compliance specialists and web accessibility experts. They assess your product against established guidelines and document any gaps clearly.
For organizations subject to Section 508 of the Rehabilitation Act, completing a VPAT is a legal requirement. But even if you are not legally required to do so, filling one out sends a clear signal: your organization takes digital inclusion seriously.
Why it makes a difference
- Compliance ready - Meets Section 508, WCAG, EN 301 549 and other legal requirements.
- Inclusive by design - Ensures all users can access your product equally.
- Builds Trust - Demonstrates a genuine commitment to accessibility.
Key Takeaways
- A VPAT is a reporting template; an ACR is the actual deliverable. The VPAT is the blank standardized form. Once filled out with real accessibility testing results, it becomes an Accessibility Conformance Report (ACR). When customers ask for your VPAT, they want the completed ACR.
- Digital accessibility is a global legal requirement. Countries including the U.S., EU nations, Canada, the UK, India, and Australia all have accessibility mandates. For U.S. federal vendors, Section 508 compliance and a VPAT are essentially non-negotiable.
- A VPAT must be based on real testing, not assumptions. Without an actual accessibility audit covering manual checks, automated scans, and assistive technology testing, the claims in your ACR lack credibility and can create legal and procurement risks.
- You do not need a perfect product to publish a VPAT. Most ACRs include known accessibility gaps. What matters is transparent documentation of barriers, affected users, and a clear remediation plan. Buyers trust honesty over inflated scores.
- A strong VPAT is a business asset. Beyond compliance, a well-prepared ACR helps win government and enterprise contracts, speeds up procurement cycles, reduces legal exposure, and signals a genuine commitment to inclusive design.
What is a VPAT?
VPAT stands for Voluntary Product Accessibility Template. It is a standardized document. Vendors use it to report the accessibility conformance of their digital products.
Products covered include websites, mobile apps, software, hardware, and electronic content. A VPAT tells buyers how accessible a product is.
Conformance is measured against global accessibility standards. These include WCAG (Web Content Accessibility Guidelines), Section 508, and EN 301 549.
The VPAT template is created and maintained by the Information Technology Industry Council (ITI). The current version is VPAT 2.5.
IMPORTANT NOTE: Governments and enterprises now require proof of accessibility. A VPAT is the industry-standard way to provide it.
What is an ACR?
ACR stands for Accessibility Conformance Report. It is the filled-out version of a VPAT template.
An ACR documents a product's accessibility conformance at a specific point in time. It shows which accessibility standard the product was evaluated against. It also shows the level of support provided for each requirement.
Procurement teams, government agencies, and enterprise buyers rely on an ACR. They use it to decide if a product is accessible before purchasing.
Every ACR is based on a VPAT. But not every completed VPAT is accurate. It must be backed by real accessibility testing.
What is the difference between VPAT and ACR: How Do They Differ??
| Term | What It Is | How It Is Used |
|---|---|---|
| VPAT | The blank standardized template | Downloaded from the ITI website |
| ACR | The filled-in, completed VPAT | Shared with buyers and procurement teams |
When a customer asks for your VPAT, they actually want your ACR. They want the completed report, not the blank template.
Where can I get the VPAT template?
You can download the VPAT template from the official ITI website at itic.org.
Always use the most current version. The current VPAT version is VPAT® 2.5Rev (April 2025). It is maintained by the Information Technology Industry Council (ITI).
Choose the template edition that matches your market:
- WCAG Edition for general digital accessibility reporting
- Section 508 Edition for U.S. federal and state procurement
- EN 301 549 Edition for European public sector procurement
- International Edition for multi-region or global product sales
BarrierBreak helps organizations create procurement-ready VPATs and ACRs aligned with these standards
Why create a VPAT ACR?
An Accessibility Conformance Report explains how accessible your digital product is. It is based on an accessibility evaluation conducted on a specific date.
It outlines the accessibility standard used. It shows how well your product supports each requirement. For many organizations, an ACR is a required part of procurement.
Here’s why it’s needed:
- Win Government & Enterprise Contracts: Many public sectors and large corporations require a completed ACR. It is a necessary part of the procurement process.
- Streamline Sales Cycles: A ready-to-share document prevents delays. Thus, procurement officers can easily check if your software or hardware meets accessibility requirements.
- Build Brand Trust: Providing a transparent account of your product's accessibility features builds customer trust and demonstrates your commitment to inclusive digital access.
- Reduce Legal Risk: Understanding your product’s accessibility helps reduce legal and compliance risks.
- Identify Areas for Improvement: Testing and filling out an ACR often reveals areas where your product can improve. It provides clear direction for building more accessible features.
What types of VPATs exist, and what is the current version?
A VPAT is available in four editions. Each one matches different accessibility standards and markets.
| VPAT Type | Best For | Standards Covered |
|---|---|---|
| VPAT 2.5 WCAG Edition | General business use and private-sector accessibility reporting | WCAG 2.0, 2.1, and 2.2 |
| VPAT 2.5 Section 508 Edition | U.S. federal and state government procurement | Revised Section 508 and WCAG 2.0 |
| VPAT 2.5 EN 301 549 Edition | European public sector procurement | EN 301 549 and WCAG 2.1 |
| VPAT 2.5 International Edition | Global and multi-region product sales | WCAG 2.2, Section 508, as well as EN 301 549 |
The International Edition is generally the best choice for products sold across various regions. It combines all major accessibility requirements in one report.
The current version is VPAT 2.5, maintained by the Information Technology Industry Council (ITI), and highly recommended to follow this one.
How to create an ACR (Accessibility Conformance Report)?
1. Choose the Right VPAT Edition
- WCAG Edition – Best for websites and general digital content.
- Section 508 Edition – Used for U.S. government procurement.
- EN 301 549 Edition – Used for the European market.
2. Conduct an Accessibility Audit
- WCAG 2.1 or 2.2 Level AA
- Automated accessibility scans
- Manual accessibility testing
- Screen reader checks
- User experience testing
You can test internally or hire accessibility experts.
3. Add Product Information
- Company name
- Product name and version
- Report date
- Product description
- Main product functions
- Testing methods used
4. Assign Conformance Levels
- Supports – The feature meets the standard.
- Partially Supports – Some accessibility barriers exist.
- Does Not Support – The feature does not meet the standard.
- Not Applicable – The requirement does not apply.
- Not Evaluated – Used for Level AAA criteria.
5. Add Clear Remarks
- Accessibility barriers found
- Known limitations
- Workarounds for users
- Planned fixes if available
- Feature details for supported items
Clear remarks improve trust and accuracy.
6. Format the Final ACR
- A PDF document
- A web page
- A machine-readable report
7. Share the ACR
- Procurement teams
- Government agencies
- Enterprise buyers
- Accessibility reviewers
BarrierBreak delivers expert-led VPAT and ACR creation with native screen reader testing and real user testing. Our reports are accurate and trusted by procurement teams.
Who needs to create a VPAT?
A VPAT is needed by organizations that sell digital products. It helps buyers review accessibility before making a purchase.
Software and SaaS Vendors
Software vendors need a VPAT to prove accessibility compliance. Large buyers often request it during procurement reviews.
- SaaS platforms
- Business software
- Mobile apps
- Web applications
EdTech Providers
EdTech vendors need a VPAT to show products support all learners. Schools and universities often review accessibility before buying software. Educational institutions using software usually request VPATs from vendors.
- Learning management systems
- Student portals
- Digital classroom tools
Healthcare Technology Providers
Healthcare software vendors need a VPAT to meet buyer accessibility expectations. Healthcare organizations must ensure tools work for all users. VPATs help buyers assess accessibility risks.
- Patient portals
- Healthcare systems
- Medical software platforms
Financial Technology Providers
For Fintech companies VPAT is an important tool. They use it to communicate accessibility information about their financial offerings. Banks and institutions review accessibility during vendor selection.
- Banking apps
- Payment systems
- Financial service platforms
A VPAT helps prove digital accessibility standards are met.
E-commerce Platform Providers
Platform providers need a VPAT to show accessible shopping experiences. Businesses want accessible tools for their customers. VPATs are requested from vendors by retailers who use their platforms.
- Store-building platforms
- Shopping cart software
- Marketplace tools
Organizations Selling Custom Software
Organizations need a VPAT when licensing software externally. Buyers need proof the product meets accessibility standards.
- Custom enterprise platforms
- Licensed internal tools
- Proprietary software systems
Inclusion-Focused Organizations
Some organizations create VPATs to show accessibility leadership. It proves transparency and strengthens stakeholder trust.
How can a VPAT help you in Procurement?
A VPAT helps procurement teams review product accessibility before purchasing. It supports informed decisions and reduces accessibility risks.
Below are the major ways VPAT helps in procurement.
Supports Vendor Evaluation
A VPAT helps screen vendors early in the buying process. Procurement teams can review accessibility before moving forward. This helps remove products that do not meet accessibility standards.
Makes Product Comparison Easier
A VPAT uses a standard reporting format. It allows for a fair comparison of multiple vendors. Teams can review accessibility results side by side.
Reduces Legal and Compliance Risks
Accessibility results in a VPAT show how well a product meets standards. Organizations can confirm compliance expectations. This reduces future legal and regulatory concerns.
Strengthens Procurement Requirements
Accessibility reports can be required during the Request for Proposal (RFP) process. Thus, clear expectations are set from the beginning. Vendors remain accountable for future accessibility updates.
Helps Plan Accessibility Improvements
A VPAT shows known accessibility gaps clearly. This helps teams plan fixes before signing contracts. Fixes or alternatives can be discussed with vendors.
Supports Equal Access
Accessibility findings in the VPAT show how users interact with the product. Procurement teams can select more inclusive technology. This improves access for people with disabilities.
How does the Accessibility Audit support the VPAT?
An accessibility audit gives your VPAT real substance. It helps ensure your accessibility claims are based on how your product works for people with disabilities, not assumptions.
- Establishes the baseline: Your product is evaluated against WCAG, Section 508, and EN 301 549 using expert testing and assistive technologies.
- Spots accessibility barriers: The audit uncovers issues that may impact people with visual, hearing, cognitive, or motor disabilities.
- Supports remediation: Audit findings give your team the opportunity to address critical accessibility issues before the VPAT report is finalized.
- Improves reporting accuracy: Once improvements are made, the updated findings are documented in the VPAT, ensuring your Accessibility Conformance Report accurately reflects your product's accessibility status.
- Builds buyer confidence: A well-audited VPAT helps buyers, compliance teams, and procurement reviewers make informed decisions.
With expert led audits and real user insights BarrierBreak helps you create VPATs and ACRs that stand up to scrutiny and support faster procurement.
An accessibility audit gives the factual data needed to complete a VPAT correctly. While a VPAT is a standard reporting document, the audit provides the testing results and evidence behind it. Without an audit, the VPAT may include unsupported or inaccurate claims.
1. Confirms Accessibility Conformance Levels
- WCAG 2.2
- Section 508
- Fully supports the requirement
- Partially supports the requirement
- Does not support the requirement
This makes the VPAT more accurate and reliable.
2. Provides Evidence for the VPAT
- Code-level issues
- Keyboard navigation problems
- Screen reader barriers
- Other user experience obstacles
These findings help create the "Remarks and Explanations" section in the Accessibility Conformance Report (ACR). They also give customers a chance to fix accessibility issues before the final ACR is prepared.
The audit gives detailed proof and context instead of general statements.
3. Reduces Legal and Procurement Risks
- Legal complaints
- Accessibility compliance issues
- Failed procurement reviews
- Loss of business opportunities
Why Should an Accessibility Expert Create the VPAT?
Having an accessibility expert create a VPAT helps ensure the report is accurate and useful during procurement. Experts understand accessibility standards in detail. They can properly assess how suitably a product meets those requirements.
This reduces risk, improves credibility. It helps organizations make meaningful accessibility improvements.
1. Ensures Technical Accuracy
Creating a VPAT is a highly technical process. An accessibility expert knows how to test products against standards such as:
- WCAG 2.2
- Section 508
- EN 301 549
They can correctly determine whether a feature:
- Supports accessibility requirements
- Partially supports them
- Does not support them
This helps create a reliable Accessibility Conformance Report (ACR) instead of a report based on assumptions or incomplete testing.
2. Reduces Legal and Financial Risk
If accessibility claims are exaggerated or incorrect, the company may face:
- Legal complaints
- False advertising claims
- Accessibility-related lawsuits
- Compliance issues under laws like the ADA or the European Accessibility Act (EAA)
A third-party accessibility expert provides an unbiased assessment. Their evaluation is based on actual testing.
This helps protect the organization from unnecessary legal and financial risk.
3. Helps Speed Up Procurement
Many government agencies and enterprise buyers require a complete and professional VPAT before purchasing a product. An expert-created VPAT can help organizations:
- Build trust with buyers
- Avoid delays during vendor reviews
- Meet procurement requirements faster
- Improve chances of winning contracts
4. Creates a Clear Improvement Plan
An accessibility expert also identifies
- Accessibility bugs
- Usability barriers
- Areas that need remediation
This gives development and QA teams a clear roadmap for fixing issues before the final ACR is completed.
BarrierBreak help organizations create accurate VPATs through detailed accessibility testing and expert guidance. Our team identifies accessibility issues, supports compliance with standards like WCAG and Section 508, and helps reduce procurement and legal risks.
How often should I update my VPAT?
You should update your VPAT at least once every 12 months. However, some situations require an immediate update instead of waiting for the yearly review.
1. Update It Every Year
Most government agencies and procurement teams prefer VPATs that are less than 12 months old. Regular updates help:
- Keep the report current
- Build trust with buyers
- Avoid questions about outdated accessibility information
2. After Major Product Changes
A VPAT should be updated whenever the product goes through significant changes. Changes, like the ones below affect accessibility and may require a new evaluation.
- A redesigned interface
- New features
- Changes in workflows
- Updates to the user experience
3. After Accessibility Fixes or Remediation
If your team completes an accessibility remediation cycle, the VPAT should also be refreshed. This ensures the report reflects:
- Newly fixed accessibility issues
- Improved conformance levels
- Updated accessibility support
Updating the VPAT after remediation gives buyers a more accurate picture of the product.
4. When Accessibility Standards Change
Accessibility standards and legal requirements continue to evolve. You may need to update your VPAT when:
- New WCAG versions are released
- Accessibility laws or regulations change
- Procurement requirements are updated
5. After a Third-Party Accessibility Audit
If the previous VPAT was created internally, an updated report supported by an independent accessibility audit can add more credibility. Third-party validation helps:
- Strengthen buyer confidence
- Improve procurement success
- Provide a more objective accessibility assessment
What does the VPAT include?
A VPAT report gives a clear, structured view of how accessible your product is. Here are the five key sections:
| Section | What It Contains |
|---|---|
| Product Information | Product name, version, description, and vendor contact details |
| Accessibility Standards | The standards evaluated: WCAG 2.1 Level AA, Section 508, EN 301 549 |
| Evaluation Methods | How the product was tested: manual review, automated scans, assistive technology testing |
| Conformance Tables | Detailed results for each requirement: Supported, Partially Supported, Not Supported, or Not Applicable |
| Remarks and Explanations | Plain-language notes on limitations, workarounds, and known issues |
What do Supported, Partially Supported, and Does Not Support mean in a VPAT?
A VPAT uses conformance levels to describe how well a product meets each accessibility requirement. There are four possible levels.
| Conformance Level | Meaning | Example |
|---|---|---|
| Supports | Fully accessible with no barriers | Keyboard users can navigate all menus and complete forms |
| Partially Supports | Accessible in most cases, but some gaps exist | Screen reader reads most content but misses some form labels |
| Does Not Support | Requirement is not met; users face a barrier | Users cannot complete a key task independently |
Vendors must provide proper explanations for "Partially Supports" or "Does Not Support." It's important to outline exactly what works, what fails, and the user impact. For more details on compliance reporting, review the Section 508 Vendor Claims Overview.
Why do we need Remarks in a VPAT?
Remarks and explanations give context to the accessibility ratings in a VPAT. A rating like "Partially Supports" does not explain the actual accessibility experience on its own.
Remarks help procurement teams and legal reviewers understand:
- What accessibility features work properly
- Which issues still exist
- How those issues affect users with disabilities
- Whether any alternatives or workarounds are available
They are also required when a criterion is marked as "Partially Supports" or "Does Not Support" in an Accessibility Conformance Report (ACR).
For example, remarks may explain that a screen reader cannot detect a submit button. Similarly, it may explain that keyboard users cannot access a feature.
Clear explanations build trust because buyers can see that the organization is being transparent about known accessibility limitations and remediation plans.
Remarks also help reduce legal and procurement risks. They document what the product can and cannot support instead of relying on unclear claims.
Which global standards does a VPAT support?
A VPAT supports major global accessibility standards used for digital products, software, and Information and Communication Technology (ICT).
When the VPAT is fully completed, it becomes an Accessibility Conformance Report (ACR).
Main Accessibility Standards Supported by a VPAT
1. Web Content Accessibility Guidelines (WCAG)
WCAG is the most widely recognized international accessibility standard for websites, software, and digital content. VPAT templates currently support:
- WCAG 2.0
- WCAG 2.1
- WCAG 2.2
2. Revised Section 508
Section 508 is a U.S. federal accessibility requirement. It requires government agencies and vendors to ensure that ICT products and services are accessible to people with disabilities.
3. EN 301 549
EN 301 549 is the European accessibility standard for ICT products and services. It is important for organizations operating in Europe and for compliance with the European Accessibility Act (EAA).
4. VPAT INT Edition
The VPAT INT Edition combines the following into one document. Thus, it makes it easier to support global procurement and accessibility requirements.
- WCAG
- Section 508
- EN 301 549
FAQ
-
Yes. A VPAT can directly support business growth, especially if you target government, enterprise, or education markets.
Here is how a VPAT helps:
- Qualify for government contracts: Federal, state, and local agencies require Section 508 compliance and accessibility documentation as part of procurement.
- Build buyer confidence: A VPAT shows how people with disabilities can actually use your product. This builds real trust.
- Speed up procurement decisions: Procurement teams with a clear ACR move faster. Less back-and-forth means faster sales cycles.
- Lower procurement risk: Accessible products face fewer legal challenges. A VPAT makes accessibility transparent, not assumed.
- Competitive advantage: Vendors with strong accessibility documentation consistently win more contracts.
BarrierBreak helps organizations turn accessibility into a clear, documented advantage for business growth.
-
The right VPAT type depends on where you sell and which legal requirements you need to meet.
If you sell to Choose this VPAT U.S. federal or state agencies Section 508 Edition VPAT Global enterprises or SaaS buyers WCAG Edition VPAT European public sector EN 301 549 Edition VPAT Multiple regions or global markets International Edition VPAT (recommended) When in doubt, choose the International Edition VPAT. It satisfies requirements across the U.S., EU, and most global markets in a single report.
-
Creating a VPAT report is a structured process. Each step ensures your accessibility conformance is accurately documented.
- Define the scope. Identify which product areas will be evaluated. Select the relevant VPAT version.
- Test for accessibility. Use manual and automated methods. Include testing with assistive technologies such as JAWS, NVDA, and VoiceOver.
- Map findings to conformance levels. Rate each requirement as Supported, Partially Supported, or Not Supported under the applicable global standard.
- Add remarks. Explain accessibility issues, known limitations, and any workarounds or fixes planned.
- Review and validate. Check the report for accuracy and completeness. Expert review adds credibility.
- Publish as an ACR. The final output is your Accessibility Conformance Report. Share it with procurement teams and buyers.
A typical VPAT creation process, including audit and documentation, takes 2 to 4 weeks. This depends on product complexity and testing scope.
-
An ACR can be self-authored or created by a third-party accessibility expert. Each approach has trade-offs.
Approach Pros Cons Best for Self-Authored Lower cost, product knowledge, and faster May be seen as less objective by buyers Internal teams and small deals Third-Party Higher credibility, accuracy, and better documentation Higher cost; requires coordination Government and enterprise sales Hybrid Balanced: internal knowledge plus expert validation Requires internal effort to draft the initial report SaaS and tech companies selling into government, healthcare, and higher education, where strict compliance verification is required. -
Procurement and accessibility teams use the ACR VPAT to evaluate the accessibility and risk level of a product.
They mainly review:
- Evidence and transparency: Buyers check whether the conformance ratings include clear explanations and supporting details. Vague statements may reduce trust in the report.
- Accessibility risks: Teams review which features are inaccessible and whether those issues create legal, compliance, or usability concerns.
- Remediation plans: If accessibility gaps exist, procurement reviews whether the organization has a clear plan and timeline to fix them.
- Product comparison: The ACR helps buyers compare multiple products using the same accessibility criteria and reporting format.
-
Yes. Without a VPAT, your product can face procurement delays, missed business opportunities, and increased accessibility risk.
Here are the specific risks:
- Procurement disqualification: Government agencies, universities, and enterprises often require a VPAT during vendor selection. Without one, your product may be removed from consideration.
- Competitive disadvantage: Competitors with accessibility documentation have a clear edge in procurement evaluations.
- Legal exposure: Organizations without an ACR may face accessibility-related legal challenges. This is especially true in regulated sectors.
- User exclusion: Without an accessibility evaluation, people with disabilities may face barriers when using your product.
- Unidentified compliance risks: Unaddressed accessibility issues can become costly to fix later, especially after a product has been widely deployed.
-
Yes, the product areas covered in the VPAT must be audited before the report is created. Accessibility claims should always be based on real testing results.
For large or complex products, organizations commonly use these strategies:
- Audit core workflows: Instead of reviewing the full system at once, teams may focus on important user flows or specific modules. The VPAT must clearly mention the limited scope being covered.
- Audit separate components individually: Different product areas, such as an admin panel, user portal, or public website, can be tested and documented through separate VPATs.
- Use manual and automated testing: Accessibility testing should include both automated tools and manual checks to verify actual accessibility support.
This process helps create accurate and defensible accessibility ratings in the VPAT.
BarrierBreak helps organizations define the right accessibility audit scope. This ensures your VPAT is accurate, credible, and buyer-ready.
-
No, you do not need to fix every issue before publishing your Accessibility Conformance Report (ACR). Most VPATs include some known accessibility gaps because the document is meant to show the current accessibility status of a product.
If every issue were already fixed, there would be little need for detailed remarks and explanations in the report.
However, fixing critical accessibility issues before creating the ACR is strongly recommended. It improves usability, reduces legal risk, and supports procurement success.
If issues still remain, they should be documented transparently in the ACR, including:
- The accessibility barrier
- Which users are affected
- The conformance level
- Any workaround or remediation timeline
Organizations should also maintain an accessibility improvement plan to continue improving the product over time. Honest reporting and clear remediation plans help build trust with buyers and procurement teams.
-
ADA Title II does not explicitly require a VPAT. But it does require digital accessibility conformance with WCAG 2.1 Level AA.
A VPAT is the industry-standard way to document that conformance. It is commonly requested in procurement and risk management processes under ADA Title II requirements.
We advise organizations not to wait until a VPAT is requested. Having one ready demonstrates accessibility maturity. It also makes compliance conversations much easier when opportunities arise.
ADA Title II applies to state and local governments and their digital services. Ensuring WCAG 2.1 Level AA compliance is a legal requirement. It is also a best practice for all public-facing digital products.
-
Yes. If you are selling to a U.S. federal agency, you will almost always need a VPAT.
Federal agencies must comply with Section 508 of the Rehabilitation Act of 1973. This law requires agencies to ensure that the ICT they procure is accessible to people with disabilities.
A VPAT provides that clarity. It documents how your product supports users who rely on assistive technologies. Without a VPAT, your product could face procurement delays. It could also put the entire sales opportunity at risk.
Key things to know about federal agency procurement and Section 508:
- Section 508 applies to all federal agencies and their technology purchases
- A Section 508 Edition VPAT is the correct template to use
- The ACR must reflect real testing, not self-certified claims
- Federal contracting officers review ACRs as part of their acquisition process
BarrierBreak specializes in Section 508 compliance testing and VPAT creation for vendors selling to U.S. federal agencies. We help you move through federal procurement with confidence.
