Cost
Free
/ Free tool · VPAT / ACR

Generate a VPAT-format conformance report.

When a US buyer asks for a VPAT, they mean an Accessibility Conformance Report over the WCAG criteria. Fill in what you know, mark what you have evaluated, download the document, free.

Adjust individual criteria (optional)

Set a different conformance level or add remarks for any WCAG 2.1 criterion. Everything you leave alone uses the default answer above.

Fill in the product details and your VPAT-format report appears here, ready to copy or download.

/ VPAT guide

What a VPAT is, who asks for one, and what makes it believable.

A VPAT is a blank template. The Accessibility Conformance Report filled in from it is the document a buyer reads, and the remarks column is the part they check.

The template and the report

The Voluntary Product Accessibility Template (VPAT) is a document published by the Information Technology Industry Council (ITI). It lists the criteria of one or more accessibility standards in tables, with a column for the conformance level and a column for remarks. The current version is VPAT 2.5Rev, published in April 2025. The template is free to use and does not require ITI membership, but VPAT is a registered service mark, so a report that uses the name has to carry the mark and follow ITI's essential requirements.

Filled in for one product, the document becomes an Accessibility Conformance Report (ACR). Section508.gov describes the VPAT as the most common way of completing an ACR, not the only one.

ITI sets the minimum content: a title in the form "[Company Name] Accessibility Conformance Report", the template version, product name and version, a report date (at least month and year), a description, a contact, notes, evaluation methods, the standards covered, definitions of the terms used, and the tables. Every criterion of each level reported needs an answer, and the report itself has to be accessible.

Who asks for one

US federal agencies. Section 508 of the Rehabilitation Act binds agencies when they develop, procure, maintain or use information and communication technology, and FAR subpart 39.2 requires the ICT they acquire to meet the standards at 36 CFR 1194.1 unless an exception or exemption applies. Those standards incorporate WCAG 2.0 Level A and AA for web content, software and electronic support documentation. Section508.gov tells agencies to require a written ACR for each commercial ICT item in a solicitation, and says an ACR must be complete for the offer to be considered for award. Their contractors are asked for the same document.

US states and public universities. Several states apply Section 508 or WCAG to their own purchasing. California's Government Code section 7405 requires state entities to comply with Section 508 when they procure technology. The Texas Department of Information Resources states that state agencies and institutions of higher education are responsible for procuring accessible technology, and that vendors submit accessibility documentation with their responses. Minnesota asks vendors for the INT edition, and Oklahoma's standard makes the conformance claim in the VPAT a material term of the contract.

European public buyers. Article 42 of Directive 2014/24/EU requires technical specifications for anything people will use to take accessibility into account, and to refer to Union accessibility requirements where a legal act sets them. EN 301 549 is the standard those references point to. Version 3.2.1 is the harmonised standard cited for public sector websites and apps under Directive 2016/2102, and the European Accessibility Act (Directive 2019/882), applied since 28 June 2025, gives a presumption of conformity to harmonised standards cited in the Official Journal. The VPAT EU edition reports against EN 301 549.

Companies. No law makes a private buyer ask, but any buyer can request the same document during vendor review.

Four editions, and which one to send

ITI publishes the template in four editions. They share the WCAG tables and differ in which other standards they add. Use the edition the buyer names. If the buyer names none, use the one that matches the law behind the purchase.

EN 301 549 has moved on. ETSI published V4.1.1 in September 2026, with clauses 9, 10 and 11 aligned to WCAG 2.2, prepared to support the European Accessibility Act. The current VPAT EU edition still reports against the 3.x versions, so a vendor answering a European buyer should say in the Notes which version the report covers.

  • WCAG edition: WCAG 2.0, 2.1 and 2.2 at Levels A, AA and AAA. Rows are marked "2.1 and 2.2" or "2.2 only", so a report on an earlier version may drop the later rows. The usual choice for private buyers and for anyone asked about WCAG 2.2.
  • Revised Section 508 edition: WCAG 2.0 plus the Revised 508 Standards, with chapters for functional performance criteria (3), hardware (4), software (5) and support documentation and services (6). Section508.gov tells federal sellers to use this edition or the INT edition.
  • EU edition: WCAG 2.0 and 2.1 plus EN 301 549 clauses 4 to 13, with clause 9 (web) answered through the WCAG tables. The 2.5Rev template covers EN 301 549 V3.1.1 and V3.2.1, whose criteria are identical.
  • INT edition: all of the above in one report, with shared criteria answered once and cross-referenced. Use it when one product is sold to US federal buyers, into the EU and elsewhere.

What the conformance levels mean

The Conformance Level column takes one of ITI's terms, and the report must define the terms it uses. A vendor who changes a definition has to say so in the Notes.

  • Supports: the product has at least one method that meets the criterion without known defects, or meets it with equivalent facilitation.
  • Partially Supports: some functionality does not meet the criterion. The term replaced the older "Supports with Exceptions" at the request of the US Access Board. Section508.gov tells buyers to read it as not conforming and to look in the remarks for what is affected.
  • Does Not Support: the majority of the product's functionality does not meet the criterion.
  • Not Applicable: the criterion is not relevant to the product, and the remarks should say why. ITI notes that Supports may be used instead, because WCAG treats a criterion with no content it applies to as satisfied.
  • Not Evaluated: the product has not been evaluated against the criterion. ITI allows it only for Level AAA criteria, and Section508.gov reminds buyers that it gives no assurance of accessibility.

How long a credible report takes, and keeping it current

There is no standard turnaround, and a date promised before anybody has looked at the product is a guess. The time goes into testing, not the template, and it grows with the number of distinct screens and user flows (WCAG conformance applies to full pages and complete processes, so a checkout counts from basket to confirmation); the roles, such as administrator and customer; the platforms, since a web app, a mobile app and the PDFs they produce are each tested; the edition, because the 508 and EU editions add software, documentation and support chapters; testing with screen readers, magnification and voice control, which no automated tool replaces; and any fixes made before the report is written, which mean a second pass.

Remarks come last. Each Partially Supports or Does Not Support row needs a note on which feature fails and how, checked by somebody who knows the product.

An ACR describes one version on one date. Section508.gov says an updated report may be needed every time the product changes. ITI's best practice is to change the report date and explain the revision in the Notes, or to issue a new report that names the one it supersedes. In practice, tie the report to releases that change the interface, re-test what changed and record it in the Notes. Section508.gov also offers the ACR Editor, which saves a report in the machine-readable OpenACR format.

What makes a reviewer distrust a report

Section508.gov tells federal buyers to run their own conformance testing where they can, and several states say a VPAT does not replace acceptance testing. A reviewer reads the report looking for the claim that will not survive that test. The usual reasons a report loses the reader:

  • Supports on every row and nothing in the remarks. No product of real size has zero known defects, so a reviewer reads it as unfinished rather than as good news.
  • Partially Supports or Does Not Support with no explanation. ITI and Section508.gov both require remarks naming the features affected and how they fall short.
  • No product version, an old date, or a version number that does not match what is being bought.
  • An old template or old standards. Section508.gov says reports built on the 2001 standards must be redone against the Revised 508 Standards. A WCAG 2.2 claim without the 2.2 rows is just as visible.
  • Evaluation methods that say only "automated testing" or "internal review". ITI asks for the testing performed, the tools, the assistive technologies used and any published test method.
  • Not Evaluated on Level A or AA rows with no word in the Notes, or Not Applicable on criteria the product plainly has content for, such as captions in a product with video.
  • 4.1.1 Parsing reported as a failure. For WCAG 2.0 and 2.1 the template pre-fills it as Supports under the September 2023 errata, and in WCAG 2.2 it is obsolete and removed.
  • The word "compliant" in the summary, or a report that is itself an inaccessible PDF.

What our free generator and the paid report do

The free generator on this page builds a WCAG edition report in English with the WCAG 2.1 Level A and AA rows, the ITI term definitions and your product details. Every row starts at Not Evaluated so that nothing is claimed before somebody checks it, and you set the level and write the remark for each criterion. It prints what you type and tests nothing, so the report is only as good as the testing behind it. Before it goes to a buyer, every A and AA row should carry a level and a remark.

The paid VPAT / ACR is built the other way round. We audit up to 25 pages of the website, the audit is included, and the report is filled criterion by criterion from that measurement. Two rules hold: a criterion is reported as Supports or Partially Supports only when a named person recorded that finding, and anything our measurement found failing is reported as Does Not Support whatever else was submitted. Criteria nobody assessed stay Not Evaluated and the report says so. That is a smaller claim than most reports make, and one a buyer can check.

/ Done for you

An ACR a procurement officer will read

A VPAT 2.5Rev report filled in criterion by criterion from a measured audit of up to 25 pages, with the remarks a reviewer reads. The audit is included, and nothing is marked Supports unless a person tested it.

$369 · one-off

Five example reports

Filled ACRs for made-up products, in English, the language VPATs are written in.

/ Questions

Questions people ask

What is the difference between a VPAT and an ACR?
The VPAT is ITI's blank template. The ACR is the completed report for one product and version. Buyers often ask for "a VPAT" and mean the filled-in ACR.
Which VPAT edition should I use?
The one the buyer names. If none is named: the Revised Section 508 or INT edition for US federal sales, as Section508.gov advises, the EU edition for buyers referencing EN 301 549, the WCAG edition for most private buyers, and INT when one product is sold into several of these markets.
Can we mark Supports for a criterion we have not tested?
No. Supports means the criterion is met without known defects, and an untested criterion gives no basis for that. Federal buyers are told to check claims with their own testing, and a claim that fails on inspection costs more than an honest Partially Supports with a remark saying what is affected and when it will be fixed.
Does a VPAT certify that a product is accessible or compliant?
No. An ACR is the vendor's own statement about one version on one date. ITI makes the vendor responsible for the accuracy of the data, and buyers are told to test the claims themselves.
Do you write ACRs for customers?
Yes. The paid VPAT / ACR includes a measured audit of up to 25 pages of your website and is filled criterion by criterion from it. A level above Not Evaluated appears only where a named person recorded the finding, and measured failures are reported as Does Not Support.
/ Sources

Where each statement comes from

Checked against the sources on .

This page explains the rules in general terms. It is not legal advice, and it does not tell you whether a rule applies to your organisation. For that, ask a lawyer who practises in the jurisdiction.