1. Web Ambassador's Network
  2. Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

A Voluntary Product Accessibility Template (VPAT) is a standardized document that technology vendors use to explain how accessible their products are. 

Once completed, the VPAT becomes an Accessibility Conformance Report (ACR)—a critical tool for organizations evaluating whether digital products meet accessibility requirements.

Watch a VPATs 101 video

Why It Matters

VPATs help buyers—especially in education, government, and enterprise sectors—understand how well a product aligns with accessibility standards like Section 508 (U.S. federal law), the Web Content Accessibility Guidelines (WCAG), and EN 301 549 (used in the EU). For institutions like ours, having this information is often a required step in purchasing or renewing software, platforms, and digital tools.

Who Uses VPATs?

VPATs are most commonly provided by vendors of:

  • Software and web platforms
  • Mobile and desktop applications
  • Hardware and interactive technologies
  • Any digital product used in communication, learning, or administration

What’s Included in a VPAT?

A completed VPAT (or ACR) typically contains:

  • Product name and version
  • Date and method of accessibility evaluation
  • Details of how the product meets (or doesn’t meet) each accessibility criterion
  • A standardized table with levels like Supports, Partially Supports, or Does Not Support, plus explanatory notes

Benefits of a VPAT

  • Informed Purchasing: Helps buyers compare products based on accessibility
  • Transparency: Encourages vendors to disclose accessibility limitations and strengths
  • Compliance: Satisfies documentation requirements for accessibility policies and procurement standards
  • Risk Management: Reduces legal and reputational risk by selecting inclusive technologies

Additional Guidance

When evaluating a digital product or service, don’t stop at just requesting a VPAT. Use it as the starting point for a deeper conversation. Here are some key questions to ask vendors:

  • Do you have a current VPAT/Accessibility Conformance Report (ACR)?
    Ask for the most recent version and check the date—it should reflect current standards (WCAG 2.1 or higher).
  • Who completed your accessibility evaluation?
    Was the VPAT created by an internal team or a third-party accessibility specialist?
  • Which accessibility standards does your product follow?
    Look for references to WCAG 2.1/2.2 Level AA, Section 508, and EN 301 549 if applicable.
  • Have any accessibility issues been identified? If so, what is your roadmap to address them?
    A transparent vendor will acknowledge limitations and share a plan for improvement.
  • Do you provide accessible documentation, support, and training?
    Accessibility doesn’t stop at the product—it also includes user support.
  • Is your team available to assist with accessibility questions or customization post-implementation?
    Ongoing support is key, especially if accessibility fixes require configuration on the client side.

A VPAT may look like a technical grid, but it’s designed to help you make informed decisions. Here’s how to read and interpret the key elements:

  • Conformance Level
    Each criterion will be marked as one of the following:
    • Supports – Fully meets the requirement
    • Partially Supports – Some features work, others may not
    • Does Not Support – Feature or content is not accessible
    • Not Applicable – The feature does not apply to the product
  • Explanatory Notes
    The vendor should provide remarks that explain why something is partially or not supported. These notes help you evaluate risk and remediation effort.
  • Coverage of Relevant Standards
    Ensure the VPAT addresses the standards that apply to UL Lafayette, which is WCAG 2.1 Level AA.
  • Currency & Accuracy
    Look at the date of the report and the evaluation method used (automated vs. manual, internal vs. third-party). Older or vague reports may not reflect real-world usability for people with disabilities.

While they're often used interchangeably, there's a technical difference. 

Watch a video to learn more.