AccessRecord

What is a VPAT? A plain guide for software vendors (2026)

By Nabin Karna · Published

A buyer has asked for your VPAT. This guide explains what that document is, who writes it, which version to use, and what the person reading it will actually check. It is written for software and edtech vendors who have never produced one.

The short answer

A VPAT (Voluntary Product Accessibility Template) is a free template published by the Information Technology Industry Council (ITI). It lists the requirements of the main accessibility standards and gives you a column to say how well your product meets each one, plus a column to explain.

Once you fill it in for a specific product, it becomes an Accessibility Conformance Report (ACR). In ITI's own words: "A version of the VPAT which has been completed for a specific product is an ACR" (ITI, VPAT page). In practice, buyers say "send us your VPAT" when they mean the completed report. Both words describe the same thing you are being asked for.

Why buyers ask for one

Public bodies and universities have legal duties to buy technology that people with disabilities can use, and an ACR is the standard way to show them where your product stands.

None of these documents makes a product accessible. A buyer wants an ACR because it is the quickest honest summary of what works, what partly works, and what does not.

The four VPAT 2.5Rev editions, and which one to use

The current template is VPAT 2.5Rev, dated April 2025. ITI publishes it in four editions (ITI):

EditionStandard it reports againstWCAG version insideUse it when
VPAT 2.5 WCAGW3C WCAG2.0, 2.1 and 2.2You sell to schools, colleges and companies that ask for WCAG conformance. This is the usual choice for edtech and SaaS.
VPAT 2.5 508Revised Section 508 Standards2.0You sell to US federal agencies, or a solicitation names Section 508.
VPAT 2.5 EUEN 301 5492.1You sell into EU public procurement.
VPAT 2.5 INTAll three of the above2.2You sell internationally and want one report.

Two practical rules. First, if a solicitation names an edition or a standard, use that one. Second, if you have a free choice, report against WCAG 2.2 Level A and AA. WCAG 2.2 became a W3C Recommendation in October 2023 (W3C, WCAG 2.2) and is built on WCAG 2.1. A report that covers 2.2 still answers a buyer whose requirement is 2.1, which is the ADA Title II standard. Buyers notice an old WCAG version. In AccessRecord's review of the 471 tool listings in the public Edu App Center catalog (data checked 11 October 2026), 33 of the 64 listings that named a WCAG version still cited WCAG 2.0.

What goes inside an ACR

Every edition has the same skeleton:

The four conformance levels are Supports, Partially Supports, Does Not Support and Not Applicable. ITI notes that "Partially Supports" replaced the older "Supports with Exceptions" at the request of the US Access Board.

The Remarks column is where a report earns trust. "Supports" with no remark tells a reviewer nothing. "Partially Supports: the chart builder's drag-and-drop has no keyboard alternative; data can be entered in the table view instead; fix planned for 5.3" tells them exactly what they need to know.

There is no VPAT certification

This is the most common misunderstanding, and ITI answers it directly: "there is no VPAT certification", and ITI "does not review or approve VPATs". There is no submission process, no logo, and no pass or fail. You complete the report as the product owner and publish it or send it to whoever asks (ITI FAQ).

Two consequences follow:

Who should write it

ITI says the manufacturer is "likely the best source" for the testing behind the report. ITI does not require third-party review, but notes that a solicitation may, so follow its terms. In practice there are three routes:

  1. In-house, if someone on the team can test with a keyboard, a screen reader and zoom, and knows WCAG well enough to judge each criterion.
  2. An accessibility auditor tests the product and writes the report from the findings.
  3. A hybrid: an auditor tests, and your team maintains the report as the product changes.

Costs and timelines for each route are in How to get a VPAT or ACR for your product.

What a procurement reviewer checks first

Reviewers rarely read every row. These are the things they look at first, and the things that get a report sent back:

  1. Is it for this product and this version? A report for "Platform" when they are buying "Platform Mobile" is a different product.
  2. Is it recent? A report dated before your last major release describes software you no longer ship.
  3. Which standard? WCAG 2.0-only reports are increasingly questioned.
  4. How was it tested? "Automated scan" alone is a red flag. Automated tools find only some issues.
  5. Are the remarks honest? A report where every row says "Supports" reads as unexamined. Specific "Partially Supports" entries with a workaround and a plan usually read better.
  6. Can they find it? Section508.gov advises vendors to "make it easy to find your product's ACR on your company's website", for example on the product page.

Common mistakes

Publishing and keeping it current

Once written, an ACR has to live somewhere a buyer can find it, and it has to stay true to what you ship. A PDF attached to an email does neither. That is the problem AccessRecord is built for. It publishes the report as a public page at a stable link, pinned to the product version it describes, and shows when a release has moved past it. You can see what that looks like in the worked example.

Whatever tool you use, the checklist is the same: name the version, date the report, state how you tested, write specific remarks, publish it where buyers look, and re-issue it when the product changes.

Sources

Data behind several of these guides: The State of Edtech VPATs 2026.