VPAT (Voluntary Product Accessibility Template)

What is a VPAT?

A VPAT (Voluntary Product Accessibility Template) is a standard document where a software vendor describes how their product meets accessibility standards. The completed document is called an Accessibility Conformance Report (ACR). VPATs are mainly used in US federal procurement so that agencies can evaluate accessibility before buying a product.^[1]

Why are VPATs important?

Despite the word "voluntary," providing a VPAT is effectively required for any vendor selling to US federal agencies. Federal procurement rules say agencies must consider accessibility before purchasing technology.

But VPATs have spread far beyond US government procurement. Enterprise buyers in higher education, healthcare, banking, and insurance now routinely ask for VPATs during their buying process. If your organization sells SaaS or digital products to large institutions, expect a VPAT request.

Which VPAT edition should you use?

The current VPAT comes in four versions, each covering different standards:

• VPAT 2.5 508 — Covers US Section 508 (which references WCAG 2.0 AA)
• VPAT 2.5 EU — Covers European standard EN 301 549 (which references WCAG 2.1 AA)
• VPAT 2.5 WCAG — Covers WCAG directly (2.0, 2.1, or 2.2 at Level A and AA)
• VPAT 2.5 INT — Covers all three standards in one document^[2]

The INT edition is growing in popularity. It lets vendors address US, EU, and WCAG requirements in a single document, which simplifies procurement for organizations with international customers.

What does a completed VPAT contain?

A filled-in VPAT (the ACR) follows a fixed structure:

• Product description — Name, version, and a brief summary
• Evaluation methods — How the testing was done: automated tools, manual testing, assistive technology testing, and whether a third party was involved
• Standards tables — The core of the document. For each WCAG rule or requirement, the vendor rates their product using one of five values:
  • Supports — Fully meets the requirement
  • Partially Supports — Some parts meet it, some do not
  • Does Not Support — Most parts do not meet it
  • Not Applicable — The requirement does not apply
  • Not Evaluated — No assessment was done
• Remarks — Specific details, known issues, or workarounds for each row

How reliable are VPATs?

VPATs are self-reported. No third party is required to verify the claims. Quality varies widely. Some vendors run thorough testing with real assistive technology. Others mark rows as "Supports" without adequate evaluation.^[3]

IT and procurement teams should treat a VPAT as a starting point, not proof. Ask vendors how they tested, who did the testing, and when. Request a demo using a screen reader. If the VPAT says "Supports" for keyboard access, try it yourself.

Legal teams should ensure vendor contracts include accessibility obligations. A VPAT alone does not guarantee ongoing compliance.

How is a VPAT different from an accessibility statement?

Both documents describe how accessible a product is, but they serve different purposes:

• A VPAT is a structured, procurement-focused document. It follows a fixed template and is aimed at buyers evaluating a purchase.
• An accessibility statement is a public-facing page for end users. It describes the accessibility status of a website and provides a way to report problems.

VPATs come from US procurement culture. Accessibility statements come from EU and UK regulation. Organizations selling globally may need both.

How Askem Helps

A VPAT needs accurate, current data to be credible — and that data has to come from real testing. Continuous WCAG monitoring tools give organizations a live picture of what their product supports and where gaps exist. For SaaS vendors and enterprise platform teams preparing or updating a VPAT, tools like Askem provide documented evidence of conformance testing through automated reports. When issues are found and fixed, the next scan cycle confirms the fix, keeping the VPAT data current rather than frozen at the point of an initial accessibility audit.

Sources

1. ITI (Information Technology Industry Council) — VPAT templates and guidance: https://www.itic.org/policy/accessibility/vpat
2. ITI — VPAT 2.5 INT template: https://www.itic.org/dotAsset/b282cb33-5b9d-4f0d-a5e3-9c0d93c0c9b8.doc
3. US General Services Administration — IT Accessibility — Using VPATs: https://www.section508.gov/buy/request-accessibility-information/