Voluntary Product Accessibility Template (VPAT) and Accessibility Conformance Report (ACR) documents are increasingly important for procurement teams that evaluate software and digital services.
What are VPAT and ACR?
A VPAT is a standardized template created by the Information Technology Industry Council (ITIC). Vendors use it to document how their products conform to accessibility requirements such as WCAG 2.2, Section 508, or EN 301 549. When the template is completed for a specific product, it becomes an Accessibility Conformance Report (ACR).
Why procurement teams need them
Organizations that procure software, platforms, or digital content often have legal or policy obligations to buy accessible products. Reviewing an ACR helps you:
- Understand how well a product meets accessibility standards
- Compare vendors objectively against the same criteria
- Identify potential barriers for employees or customers with disabilities
- Document due diligence for compliance purposes
Structure of a VPAT / ACR
A typical VPAT/ACR includes:
- Product name and version, vendor contact information, and evaluation date
- The accessibility standard(s) used as benchmarks (e.g., WCAG 2.2, Section 508)
- A table of success criteria with conformance levels: Supports, Partially Supports, Does Not Support, or Not Applicable
- Notes describing how the product meets or fails each criterion, including any known workarounds
Different VPAT editions correspond to different standards: VPAT 2.4 Rev 508 (Section 508), VPAT 2.4 Rev WCAG (WCAG 2.2/2.1), and VPAT 2.4 Rev EU (EN 301 549). Many vendors complete multiple editions if their product is sold internationally.
Interpreting conformance levels
An ACR is not a simple pass/fail. Supports means the feature fully meets the criterion; Partially Supports indicates minor issues or limitations; Does Not Support signals serious accessibility barriers. Not Applicable is used when a criterion doesn’t apply (e.g., if the product has no time-based media). Look beyond the summary—read the notes to understand impact.
Tips for requesting and reviewing a VPAT / ACR
- Request the most recent ACR and check the evaluation date.
- Confirm which standards and versions were used (WCAG 2.2 vs 2.1).
- Ask whether the report was prepared by an independent accessibility specialist.
- Review notes for context and ask follow-up questions about “Partially Supports” or “Does Not Support” entries.
- Test critical user flows yourself or ask for a demonstration.
- Consider requiring re-testing or updated documentation with major releases.
Creating a VPAT / ACR for your product
If you sell software or digital services, you may need to provide an ACR to potential customers. To create one:
- Conduct a thorough accessibility audit aligned to WCAG 2.2 (ideally by an independent expert).
- Select the relevant VPAT edition(s) based on your market and compliance obligations.
- For each criterion, describe how your product supports it, note any exceptions, and provide recommended workarounds where possible.
- Include a date and contact information so procurement teams can ask questions.
- Keep your ACR up to date with each major release.
Conclusion
VPATs and ACRs facilitate informed procurement decisions and encourage vendors to improve accessibility. Whether you’re buying or selling digital products, understanding how to interpret and create these documents is essential. For h
elp performing the underlying audit or preparing a compliant report, explore our WCAG accessibility audit & compliance support service.