Skip to contentAltstamp
Menu

VPAT template (ACR builder)

A VPAT® is ITI's free template; filled in for one product it becomes an Accessibility Conformance Report, or ACR. This builder lays out that report for a web product: the header fields ITI requires, the WCAG Level A and AA rows for your edition, a conformance level and a remark on each, ready to print or paste.

Build your ACR

Pre-filled with a worked example for a fictional invoicing app; edit any field or press Reset to start empty. The draft stays in this browser on this device and is never sent anywhere. It follows the structure of ITI's VPAT® 2.5Rev; for the official Word template, use ITI's VPAT page.

Goes in the title: “[Company] Accessibility Conformance Report”.

The release you tested.

At least the month and year, such as “May 2025”.

Two or three sentences: what it does and who uses it.

An email address is enough.

What the report covers and leaves out, and what changed since the last one. May be blank.

Evaluation methods used

Tick what you actually did. It prints as one line in the report.

Criteria answered

Level A criteria

    Level AA criteria

      Line drawing of a blank three-column table, one cell ringed in orange

      What WCAG asks

      • 2.1.1KeyboardA
      • 4.1.2Name, Role, ValueA
      • 1.4.3Contrast (Minimum)AA

      How to fill in the ACR builder

      1. Pick the edition and the WCAG version

        Use the ones the buyer's request names. A federal buyer means the 508 or INT edition; a request that names only WCAG means the WCAG edition.

      2. Fill in the header fields

        Company, product and the version you tested, a report date, a short description, a contact address, notes on what is in and out of scope, and how you tested.

      3. Test, then answer every row

        Answer from testing, not from memory. Our WCAG 2.2 AA checklist gives a plain test per criterion; the contrast check and the focus order checklist cover the rows people most often guess at.

      4. Write the remarks

        Every Partially Supports, Does Not Support and Not Applicable row needs one; the builder lists the rows still missing it. Remarks on Supports rows say how you checked.

      5. Preview, then print or copy

        Print to PDF, or copy the report as an HTML table or as Markdown into your own document. Then check that the finished file is itself accessible before you send it.

      New to the format? What a VPAT is explains the editions, the five conformance terms and what a buyer reads into each.

      What the builder checks for you

      It lays out the right rows for the version you report: 55 criteria at Level A and AA for WCAG 2.2, 50 for WCAG 2.1 and 38 for WCAG 2.0. In 2.1 and 2.0 one of those is 4.1.1 Parsing, which ITI's templates answer Supports by rule, so 49 and 37 rows are left for you to judge; in a 2.2 report the 4.1.1 row stays, marked removed. Rows that arrived in WCAG 2.1 or 2.2 say so, as the template's rows do.

      The level select offers exactly ITI's four terms for A and AA rows. Not Evaluated is left out because ITI allows it only on Level AAA rows. The report lists ITI's definitions under Terms, as every ACR must. On the 508, EU and INT editions, each answer is written “Web: Supports” and so on, because those templates answer each row per type of product.

      What it does not do

      It does not test your product, and it builds the WCAG tables only. The 508, EU and INT editions also have tables for the Revised 508 chapters or the EN 301 549 clauses; finish those in ITI's official template. The builder follows ITI's VPAT® 2.5Rev structure but is not ITI's document, and nothing it produces is a certification: ITI says there is none.

      What WCAG asks of a claim, and where an ACR differs

      What WCAG asks: 5.3.1 Required Components of a Conformance Claim

      Conformance claims are not required. Authors can conform to WCAG 2.2 without making a claim. However, if a conformance claim is made, then the conformance claim must include the following information

      The list that follows: the date of the claim; the guidelines' title, version and URI; the level met; a concise description of the pages covered; and the web content technologies relied upon. Read it in WCAG 2.2, section 5.3.

      An ACR is not a WCAG conformance claim. A claim says a set of pages meets a whole level; an ACR reports each criterion separately and can show gaps. The two still share their bones, so borrow WCAG's list: a dated report, the WCAG version named, the scope written down in the Notes, and the assistive technology you tested with in Evaluation Methods Used. W3C recommends listing those user agents in a claim as well.

      What a weak ACR usually looks like

      • Supports on every row and no remarks at all. To a buyer that reads as untested.
      • Not Applicable on criteria the product plainly touches, such as 1.4.3 Contrast (Minimum) on a product with text in it.
      • No product version, or a report date years older than the release being sold.
      • The retired term “Supports with Exceptions”, a sign the report was written on an old template.
      • Words like “certified” or “ADA compliant”. There is no VPAT certification, and an ACR reports against a standard such as WCAG 2.1 Level AA.
      • A scanned or untagged PDF, so the report about accessibility is itself inaccessible.

      If the report has to come from a third party, our comparison of VPAT writing services sets out what to ask each firm. Selling to a federal agency? Start with what Section 508 is.

      Related