/
What is a VPAT (Voluntary Product Accessibility Template)?

What is a VPAT (Voluntary Product Accessibility Template)?

  • Ready for review
    • Feb 05, 2026

    Technically, A VPAT is a document that lists the criteria to meet to be accessible. It is an empty template. When it is filled out, it is called an Accessibility Conformance Report (ACR). Most people call an ACR a VPAT. To learn how vendors should be filling out a VPAT, read the instructions at the beginning of the VPAT. The most current VPAT to be used is on the ITIC website, under Resources.

    A VPAT is an overview of the accessibility compliance of a product. Usually, the most objective (and most accurate) VPAT is one generated by a third party assessment company, though most VPATs are generated by the vendor that is selling the product or service. 

    A VPAT is NOT an accessibility audit report of a product – although, it is necessary to conduct an accessibility audit of the product to write an accurate VPAT. Without an accessibility audit, a VPAT is just a guess about the product’s accessibility compliance. 

    Vendors need to fill out the template completely. After each criterion, under the “Conformance Level” column, they should use the terms “Supports”, “Partially Supports” “Does Not Support” or “NA”. Under “Remarks and Explanations”, information should be provided on why the product does or does not meet the criterion.

    VPAT criteria are mapped to Web Content Accessibility Guidelines (WCAG 2.0). Originally, WCAG was meant to be used to evaluate Web accessibility. Language is now added in to apply to other kinds of Information and Communication Technology (ICT). There are three levels of conformance in a VPAT. At this time, only levels A and AA on a VPAT need to be marked as “Supports”. Here’s what the builders of WCAG (the WC3 Working Group) say about level AAA: “It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content”

    Do not assume that a VPAT is accurate, especially in the case where a VPAT has been written by the product’s vendor. There are some other red flags to look out for in a VPAT:

    • The VPAT is not 2.0 or above.

    • Cells without content in the table section.

    • Terminology such as “Passes” and “Fails”. The author of the VPAT should use the standard terminology “Supports”, “Partially Supports” “Does Not Support” and “NA”

    • A lot of “NAs”. Many VPATs say “NA” instead of “Does Not Support”.

    • All “Supports”. It is very unlikely that a product is completely accessible.

    • One VPAT for multiple products.

    • An inaccurate or unclear description of the product.

    • Dated more than a year ago. VPATs should be updated when a product is updated.

    • Does not contain details of testing undertaken (under “Evaluation Methods”).

    • Only automated testing listed in “Evaluation Methods”.

    • Missing or inaccurate contact information.

    • “Not evaluated” in the Level A or AA section. This can only be used for Level AAA.

    VPAT Criteria and What They Mean

    The main criteria in a VPAT are listed below. The many sub-criteria are not listed here. Download a VPAT from the link above to find links to extended explanations of criteria and sub-points of criteria.  The page the links go to has links on How to Meet the criteria and Understanding the criteria.

    • Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

    • Guideline 1.2 Time-based Media: Provide alternatives for time-based media. (Such as video, audio, etc.)

    • Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

    • Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background.

    • Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard.

    • Guideline 2.2 Enough Time: Provide users enough time to read and use content.

    • Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures

    • Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.

    • Guideline 3.1 Readable: Make text content readable and understandable.

    • Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways.

    • Guideline 3.3 Input Assistance: Help users avoid and correct mistakes.

    • Guideline 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.

    Resources:

    Web Content Accessibility Guidelines (WCAG) 2.0
    https://www.w3.org/TR/WCAG20/

    How to Read a VPAT, Accessibility Oz https://www.accessibilityoz.com/2019/09/how-to-read-a-vpat/