Understanding Voluntary Product Accessibility Templates (VPAT)

A VPAT (Voluntary Product Accessibility Template) is a standardized document that outlines how well a digital product meets accessibility standards like the Web Content Accessibility Guidelines (WCAG). It’s often used during procurement to help organizations determine whether a product can be used by people with disabilities. Once the VPAT is filled out with product-specific information, it becomes an Accessibility Conformance Report (ACR), which formally documents the product’s accessibility.

This page includes resources for:

Accessibility Disclaimer

VPATs (or ACRs) can help understand a product’s accessibility claims but do not guarantee full compliance or real-world accessibility. They are a starting point and should be used as a reference, not a definitive measure of accessibility.

Think of it as a helpful summary, not proof. If accessibility is important for your purchase or required, it’s a good idea to ask questions or request a demo to see how the product works in real-life situations.

Filling out a VPAT

Someone familiar with digital accessibility within the organization, such as an accessibility specialist or a reputable third-party accessibility auditor, should fill out the VPAT. Download the 508 VPAT from the Information Technology Industry Council (ITI) website. The General Services Administration site provides instructions on creating an Accessibility Conformance Report, and the Information Technology Industry Council (ITI) offers VPAT training modules. An accessibility statement does not replace our requirement for a completed VPAT or ACR.

A VPAT consist of the following four sections:

  1. Product Information: This section includes the name, product version and company information
  2. Standards Covered: This section includes WCAG 2.1, Section 508, EN 301 549, etc.
  3. Evaluation Methods Used: This section details how the product was tested (manual, automated, user testing)
  4. Conformance Levels: This section indicates to what level the product supports the criteria
    • Does Not Support
    • Supports
    • Partially Supports

Reviewing a VPAT

Each VPAT includes rows such as:

  1. Criteria: Includes specific requirements, like “1.1.1 Non-TEXT Content” from the Web Content Accessibility Guidelines (WCAG).
  2. Conformance Level:
    • Not Applicable – Does not apply to this product
    • Supports – Fully meets the requirement
    • Partially Supports – Some issues exist
    • Does Not Support – Significant barriers exist
  3. Remarks: Offers context, explains limitations or how the product meets the standard
  • Scan for red flags: Lots of “Does Not Support” or vague language.
  • Focus on critical features: Does the core functionality work for all users?
  • Check the Remarks section: “Partially Supports” can mean different things — read carefully.
  • Be cautious of vague answers: Responses like “Supports with exceptions” need clarity.
  • VPATs can be outdated. Always check the date of publication.
  • Most are self-reported by vendors; they may not be independently verified.
  • A VPAT alone does not guarantee WCAG or Section 508 compliance.
  • Accessibility varies between product versions or platforms (e.g., web vs mobile).
  • VPATs may not cover third-party features or plugins.
  • Use VPATs as a starting point but always follow up with your own accessibility testing or an audit.