How accessible is your website?Start free check

VPAT / Accessibility Conformance Report Explained

Also called: ACR, Accessibility Conformance Report, Voluntary Product Accessibility Template, VPAT report

Definition

A VPAT (Voluntary Product Accessibility Template) is a template from the Information Technology Industry Council (ITI). Filled in for a specific product, it becomes an Accessibility Conformance Report (ACR) that documents how the product meets accessibility standards such as the Revised Section 508 Standards and WCAG.

A VPAT / Accessibility Conformance Report is the document software and web vendors hand to buyers who ask "how accessible is your product?". The VPAT® (Voluntary Product Accessibility Template) is the blank form; once a vendor fills it in for one product and version, the result is called an ACR. US federal agencies ask for it before they buy, and many companies, universities and public bodies outside the US use it the same way.

What it means

The template was developed by the Information Technology Industry Council (ITI). It walks through the standards line by line, and the vendor states for each criterion how well the product meets it. The best-known use is Section 508: according to section508.gov, filling in a VPAT is voluntary, but a federal agency needs an ACR to consider a product at all. Only the government can waive it.

An ACR has two parts:

Part What it contains
Title page Company and product name, version, report date, product description, contact, notes and the evaluation methods used
Criteria tables One row per criterion – for web content the WCAG Level A and AA tables are required, Level AAA is optional

Each row gets one of four conformance terms:

Term Meaning
Supports The functionality meets the criterion without known defects
Partially Supports Some functionality does not meet it
Does Not Support Most functionality does not meet it
Not Applicable The criterion is not relevant to the product

"Not Evaluated" is only allowed in the Level AAA table, because that is the only table that is not required. For "Partially Supports" and "Does Not Support" a remark explaining the gap is required; for "Supports" it is encouraged.

For US federal sales, section508.gov points to the Revised Section 508 edition or the international (INT) edition, which includes all Revised Section 508 requirements. In Europe, procurement relies on EN 301 549, which ITI's international templates also address.

Examples

A useful ACR row is precise about what fails and where:

Example
<!-- Row in the WCAG 2.x Level A table of an ACR -->
<tr>
  <th>1.1.1 Non-text Content (Level A)</th>
  <td>Partially Supports</td>
  <td>Product photos in the shop have alt text. Icons in the
      account menu (settings, logout) have no text alternative.
      Fix planned for version 4.3.</td>
</tr>
Do

Test the exact product version before you write the report, name the tools and manual checks you used, write a concrete remark for every partial or failed criterion, and publish a new ACR when the product changes.

Don't

Mark every row "Supports" without testing, copy remarks between products, leave required rows empty, use "Not Evaluated" in the A and AA tables, or present the report as a certificate.

How to create a VPAT / Accessibility Conformance Report

    For websites, a free WCAG scanner helps you find automatically detectable issues before you start the manual part.

    Questions

    What is the difference between a VPAT and an ACR?

    The VPAT is the empty template. The ACR is the completed report for one product and version. In everyday language people often say "VPAT" for both.

    Is a VPAT required by law?

    Filling in the VPAT template is voluntary. But a US federal agency needs an ACR to consider buying an ICT product, and many private and public buyers ask for one in their tenders.

    Who should fill out a VPAT?

    The product owner or developer – a company, contractor or agency that sells the product. They must test the product against the standards first. Many vendors also hire an external auditor to make the report more credible.

    How often should an ACR be updated?

    Whenever the product changes in a way that could affect accessibility, for example a new version or major bug fixes. Reports based on the old 2001 Section 508 standards must be redone under the 2017 Revised Section 508 Standards.

    Does a VPAT cover the European Accessibility Act?

    The US Section 508 edition does not. For the European Accessibility Act and EU tenders, the relevant standard is EN 301 549, which builds on WCAG – choose a template edition that covers it.

    • Section 508: Accessibility for US Federal Agencies

      Section 508 is part of the US Rehabilitation Act of 1973 (29 U.S.C. 794d). It requires federal agencies to make the information and communication technology they develop, procure, maintain or use accessible to people with disabilities.

      Read definition: Section 508: Accessibility for US Federal Agencies
    • Accessibility Audit: How a WCAG Website Review Works

      An accessibility audit is a structured review of a website or app against an accessibility standard, usually WCAG 2.2 Level AA. It combines automated tests with manual checks by experts and ends in a report that lists each barrier, where it occurs and how to fix it.

      Read definition: Accessibility Audit: How a WCAG Website Review Works
    • WCAG Conformance Levels: A, AA and AAA Explained

      WCAG conformance levels are the three tiers – A, AA and AAA – at which a web page can meet WCAG. Each level includes every success criterion of the levels below it, and conformance always applies to full pages and complete processes.

      Read definition: WCAG Conformance Levels: A, AA and AAA Explained
    • EN 301 549: European Standard for Accessible ICT

      EN 301 549 is the European standard “Accessibility requirements for ICT products and services”. It covers websites, documents, software, hardware and support services; its web clause 9 contains the WCAG success criteria of levels A and AA.

      Read definition: EN 301 549: European Standard for Accessible ICT

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done