Skip to main content
Your browser is too old to display this site correctly. Please update to the latest Chrome, Edge, Firefox or Safari.
Compliance Documentation

VPAT Center

Voluntary Product Accessibility Templates (VPAT) and Accessibility Conformance Reports (ACR): the documents that unlock enterprise and government sales. Everything you need to read, write, and generate them.

VPAT 2.5Section 508EN 301 549WCAG 2.x

Last reviewed: September 9, 2026

What is a VPAT?

A Voluntary Product Accessibility Template (VPAT) is a standardised document created and maintained by ITI (Information Technology Industry Council) that vendors complete to report how their product or service conforms to accessibility standards.

A completed VPAT is called an Accessibility Conformance Report (ACR). The ACR is the document customers read; the VPAT is the template. The current version is VPAT® 2.5Rev (April 2025), published in four editions: WCAG, Revised Section 508, EU (EN 301 549), and INT, which combines all three.

Important: A VPAT is a legal declaration. Intentionally false conformance claims may violate the False Claims Act (US federal contractors) or procurement laws in other jurisdictions. Always base claims on real test results.

Who Needs a VPAT/ACR?

US Federal Government Vendors

Federal agencies must meet Section 508 when they buy ICT, so they routinely ask vendors for an ACR (usually built on the VPAT) in procurement RFPs.

EU Public Sector Contractors

EN 301 549 conformance documentation required for EU public procurement contracts.

Enterprise SaaS Sales

Fortune 500 and large enterprise buyers routinely require a current VPAT before signing software contracts.

Education Technology (EdTech)

Schools, universities and state education agencies often ask for a VPAT when buying software, to check it against their own accessibility obligations.

Healthcare Software

Hospitals and healthcare systems often ask for a VPAT when buying software, as evidence for their own accessibility obligations.

Financial Services

Banks and financial institutions require ACRs from vendors to satisfy their own regulatory obligations.

VPAT 2.5 Sections Explained

Each row in a VPAT corresponds to a specific standard requirement. Here are the main sections:

Understanding Conformance Values

Supports

The functionality fully meets the criterion without exception.

Partially Supports

Some functionality meets the criterion; exceptions are noted.

Does Not Support

The criterion is not met. A remediation plan should be provided.

Not Applicable

The criterion does not apply to this product or feature.

Not Evaluated

Not tested. Should be minimised; avoid in submitted ACRs.

How to Write a VPAT, Step by Step

  1. 1

    Run a full accessibility audit

    Use AccessiSight to scan all key user flows. Record results per WCAG criterion with evidence.

  2. 2

    Map findings to VPAT sections

    Each WCAG SC maps to a VPAT row. For each, assign: Supports / Partially Supports / Does Not Support / N/A.

  3. 3

    Write remarks for all non-Supports rows

    Explain what fails, which user group is affected, and your remediation plan with target date.

  4. 4

    Have legal review the final document

    A VPAT is a legal document. False or misleading conformance claims can create liability.

  5. 5

    Publish and version-control the ACR

    Publish on your website and link from your accessibility statement. Update with every major release.

Frequently Asked Questions

What's the difference between a VPAT and an ACR?

A VPAT (Voluntary Product Accessibility Template) is the blank standardised template published by ITI. An ACR (Accessibility Conformance Report) is what you get once a vendor fills that template in for a specific product: the completed, customer-facing document. In short: VPAT is the template, ACR is the completed report. The two terms are often used interchangeably in practice, but technically a company writes an ACR using the VPAT template.

Is a VPAT legally required?

Not universally, but it's required in specific contexts: US federal agencies must consider Section 508 when buying ICT, so they routinely ask vendors for an ACR (usually built on the VPAT) in RFPs. EU public buyers commonly ask for EN 301 549 conformance information. Outside government procurement, VPATs aren't legally mandated, but Fortune 500 and other large enterprise buyers commonly require a current one before signing a contract. Whether or not it's legally required in your case, a VPAT is a legal declaration once written. Intentionally false conformance claims can violate the False Claims Act (for US federal contractors) or equivalent procurement laws elsewhere.

Generate Your VPAT Automatically

Run a scan first, then generate a WCAG 2.2 / Section 508 / EN 301 549 VPAT from its results in one click. Export as PDF.

Not legal advice. This guide is educational and does not constitute legal advice. A VPAT/ACR is your own statement about your product; make sure it is accurate and reviewed before you share it.