Skip to content

00 / Notes / 002 / 2026-11-09

What a VPAT is and who asks for one

A VPAT is ITI’s accessibility reporting template. Who asks for one, which edition to send, how to read the conformance terms, and what it does not prove.

A buyer writes: “Please send your VPAT.” Here is what they want, why, and what to send back.

The document

VPAT stands for Voluntary Product Accessibility Template. It is a free template published by the Information Technology Industry Council (ITI), which describes it as a tool to help companies explain how their products and services support accessibility standards.

The template is the blank form. Once it is completed for a specific product, ITI calls the finished document an Accessibility Conformance Report, or ACR. Buyers say “VPAT” for both and want the finished report.

“Voluntary” describes the template, not the request. The Section508.gov FAQ is plain: using the VPAT itself is not required, but completing an ACR is not voluntary if you want the government to consider buying your product.

Version and editions

ITI lists VPAT 2.5Rev, released in April 2025, as the latest version. It comes in 4 editions, and ITI’s advice is to choose by the standards that apply to your product, customer, or market.

EditionReports againstSend it when
508WCAG 2.0 and the Revised Section 508 standardsThe buyer is a U.S. federal agency
WCAGWCAG 2.0, 2.1, and 2.2The buyer cites WCAG alone
EN 301 549WCAG 2.0 and 2.1, plus EN 301 549The buyer cites the European standard
INTAll of the aboveOne report has to serve several markets

Check 2 things before you download.

First, the WCAG tables in the 508 edition stop at 2.0, because the federal standards incorporate WCAG 2.0 at Level A and Level AA. A buyer who needs WCAG 2.1 AA needs the WCAG or INT edition.

Second, official pages disagree on the version. The Section508.gov how-to, reviewed in June 2026, still calls 2.4 the current version and says any 2.x is acceptable, provided a federal seller uses the 508 or INT edition. ITI owns the template, so unless a solicitation names a version, download the latest there.

Who asks

Federal buyers. Section 508 applies to all federal agencies when they develop, procure, maintain, or use information technology, and the FAR requires ICT acquisitions to meet the accessibility standards unless an exception or exemption applies. Section508.gov tells agencies to require an ACR for each ICT item and says the report must be complete to be considered for award.

Primes. The sample contract language Section508.gov gives agencies puts the report on the contractor: an ACR, before acceptance, for each ICT item that is developed, updated, or configured for the agency. If you build part of what a prime delivers, expect the prime to ask you for yours.

State and local governments have the same question under a different rule. The ADA Title II rule sets WCAG 2.1, Level AA as the technical standard for their web content and mobile apps, including content a contractor or vendor posts for them. The compliance dates are April 26, 2027 for entities with a population of 50,000 or more, and April 26, 2028 for smaller entities and special districts. An agency working toward those dates needs to know where its vendors stand, and the WCAG edition fits the question.

Enterprise procurement. ITI’s description is not specific to government. It calls the template a common way for technology companies and buyers to understand and compare product accessibility, and notes that a VPAT may be requested or required as part of a procurement process.

What a good one contains

The Section508.gov how-to lists 7 fields for the title page, including the product name and version, the report date, contact information, and the evaluation methods and tools used. Then comes a conformance level for every criterion in the applicable tables, with remarks required on every line marked Partially Supports or Does Not Support.

Beyond that, I look for 3 things: the assistive technology used in testing, by name; remarks that say where a failure occurs and what a user cannot do; and a report file that is itself accessible.

How to read the terms

Section508.gov defines them this way:

  • Supports. At least one method meets the criterion without known defects, or meets it with equivalent facilitation.
  • Partially Supports. Some functionality does not meet the criterion.
  • Does Not Support. The majority of functionality does not meet the criterion.
  • Not Applicable. The criterion is not relevant to the product.
  • Not Evaluated. Allowed only in the Level AAA table. On any other line it means the product was not tested there.

Partially Supports covers everything from one unlabeled button to failures across nearly half the product. The remarks column is the only place the difference shows, so read it first. Then check each Not Applicable against the product. The Section508.gov guide to vendor claims warns that it should not be confused with non-conformance.

What it does not prove

  • Nobody certifies it. ITI does not review, approve, or certify completed reports, and says there is no official certification, approval, or pass/fail rating. Third-party review is optional unless a buyer requires one.
  • It describes one version on one date. Section508.gov says an updated report may be required every time the product changes.
  • It is not a test. Section508.gov tells purchasers to run independent validation testing whenever possible, and has agencies reserve the right to test before award.
  • It reports criteria, not use. Every line can read Supports while a person using a screen reader still struggles to finish the task. Conformance is checked criterion by criterion. Usability is checked with people.

An honest report with gaps is still worth sending. Section508.gov says a product is still considered for purchase when it does not meet every standard.

Answering the request

  1. Ask which standard and edition the buyer needs, and whether the solicitation names a version.
  2. If you have a report for the version you ship today, send it. If the product has changed since the report date, say so.
  3. If you have none, test first. The report is a record of testing, and the template is the easy part.
  4. Mark Supports only where you tested.

About this note

I checked the official sources linked here on 2026-11-17. AI tooling supports the work; I review and own the result.

Next step

My full audit tests against WCAG 2.1 AA by hand with assistive technology and delivers a completed VPAT 2.5 report: 3 weeks, fixed at $15,000. See the 3 accessibility audit tiers.