Skip to Main

How to Interpret a VPAT

A Voluntary Product Accessibility Template (VPAT) is a vendor's self-assessment of how well their product aligns with accessibility standards, primarily the Web Content Accessibility Guidelines (WCAG). While VPATs provide valuable information, they can be overwhelming and confusing. This guide breaks down the key sections of a VPAT, empowering you to make informed decisions about digital accessibility.

Product Information Page

This introductory section sets the stage for the VPAT:

  • Product Name/Version: Double-check this matches the specific product and version you're considering.
  • VPAT Version: The latest VPAT template is 2.4 (released in 2020). Older versions may lack information relevant to newer accessibility standards.
  • Evaluation Methods: Pay attention to how the vendor tested their product. Did they use automated tools, manual testing, or engage users with disabilities? This provides insight into the thoroughness of their assessment.
  • Contact Information: Note who to contact for further questions or clarification about the VPAT.

Success Criteria (The Core of the VPAT)

The bulk of the VPAT is a table listing WCAG Success Criteria and how the product fares against each. Each row represents a specific criterion, organized by WCAG's four principles: Perceivable, Operable, Understandable, and Robust (POUR). Let's break down the columns:

  • Column 1: Success Criteria
    • Lists the individual WCAG requirements (e.g., "1.1.1 Non-text Content")
    • Each criterion has a number, a short name, and a longer description in the notes section of the VPAT
  • Column 2: Conformance Level
    • This is where the vendor states if their product "Supports", "Partially Supports", "Does Not Support", or if the criterion is "Not Applicable"
    • "Supports" is the ideal - it means the product meets the criterion
    • "Partially Supports" means some parts work, but not all. Pay close attention to the vendor's explanation of what doesn't work.
    • "Does Not Support" is a serious concern, especially for key criteria
    • "Not Applicable" is fine if justified; some criteria may genuinely not be relevant to the product's nature.
  • Column 3: Remarks and Explanations
    • This is crucial. A good VPAT doesn't just have checkmarks, it explains:
      • HOW the product supports a criterion.
      • WHAT specific features or functionality make it accessible.
      • WHERE to find those features (if applicable).
      • WHY something is "Partially Supported" or "Not Supported".
      • WHY a criterion is "Not Applicable".
    • Vague remarks or no remarks at all are red flags.

Potential VPAT Follow-up

A VPAT is a starting point, not the final word on accessibility.

  • Questions for the Vendor:
    • If anything is unclear in the VPAT, ask for clarification.
    • If "Partial Support" or "Does Not Support" is noted for important criteria, ask about their roadmap for improvement.
    • If "Not Applicable" is frequent, ensure it's truly justified, not a way to avoid addressing issues.
  • Independent Evaluation:
    • If in doubt, consider having an independent accessibility audit conducted.
    • Involve users with disabilities in testing the product to get real-world feedback.
  • Ongoing Communication:
    • Accessibility isn't static. New features or updates can impact it. Keep the conversation open with the vendor about ongoing accessibility efforts.

Remember:

  • Don't be afraid to ask questions. A good vendor will welcome the opportunity to clarify and demonstrate their product's accessibility.
  • Involve users with disabilities. Their insights are invaluable in assessing whether a product truly meets their needs.
  • Accessibility is a shared responsibility. Work with vendors to make informed choices and promote a more inclusive digital world.
Back-to top