AccessRecord

How to write a VPAT (and turn it into an ACR): a step-by-step guide for 2026

By Nabin Karna · Published

A buyer has asked for your VPAT and you have never written one. This guide walks through the actual writing: which file to download, what goes in each field, how to rate every criterion, and how to word the remarks so a procurement reviewer believes them. It follows ITI's own instructions in the VPAT 2.5Rev template (April 2025), with the Section508.gov guidance for federal sellers.

One clarification up front. You "write a VPAT" by filling in a template. The finished document is called an Accessibility Conformance Report (ACR). ITI puts it this way: "A version of the VPAT which has been completed for a specific product is an ACR" (ITI). Buyers say "VPAT" when they mean the finished report, so this guide uses both words. If you want the vocabulary spelled out, read ACR vs VPAT first.

The short version: download the right edition, test the product before you write anything, rate every Level A and AA criterion with one of four ITI terms, explain every "Partially Supports" and "Does Not Support" with specifics, then delete the instruction pages and publish. The template is free. The effort is in the testing and the remarks.

Before you start: three decisions

  1. Which edition? ITI publishes four editions of VPAT 2.5Rev: WCAG, Revised 508, EU (EN 301 549) and INT (all three). The WCAG edition covers WCAG 2.0, 2.1 and 2.2. If a solicitation names an edition or a standard, use that one. If you have a free choice and sell software or edtech to schools, companies or state and local government, use the WCAG edition. Federal sellers must use the Revised 508 or INT edition (Section508.gov). EU public buyers expect the EU edition.
  2. Which WCAG version? Report against WCAG 2.2 Level A and AA unless the buyer says otherwise. 2.2 builds on 2.1, so a 2.2 report also answers a 2.1 requirement. That matters because the US Department of Justice's ADA Title II rule for public schools, colleges and local governments names WCAG 2.1 AA, with compliance dates of 26 April 2027 (population of 50,000 or more) and 26 April 2028 (everyone else) (Federal Register, 20 April 2026). The Revised 508 edition still maps to WCAG 2.0 (ITI).
  3. Which product, which version, which parts? An ACR describes one version of one product. Decide whether the web app, the iOS and Android apps, the admin console, your help documentation and your support channels are in or out, and say so in the report.

Step 1. Download the template and keep the rules in mind

Get the edition you need from ITI's VPAT page. It is free and does not require ITI membership. Two rules from ITI's instructions are worth knowing now:

Step 2. Fill in the header

Every ITI edition requires the same header content at a minimum. For the WCAG edition:

Field What to write
Report title "[Company name] Accessibility Conformance Report"
Template version "Based on VPAT® Version 2.5Rev"
Name of product / version The exact product name and version identifier, for example "Acme Quiz web app, release 5.2"
Report date The publication date, at least month and year. Write "4 May 2026" or "May 4, 2026", not "5/4/26", which is ambiguous
Product description Two or three sentences: who uses it and what it does
Contact information An email address is enough. Use one that a person reads
Notes Scope, exclusions, what the report does not cover, related documents. May be blank, but should not be
Evaluation methods used See Step 3
Applicable standards / guidelines Which WCAG versions and levels the report covers, marked yes or no. List only the versions you actually evaluated against
Terms The definitions of the conformance levels (the template includes them. Keep them)

Source: ITI VPAT 2.5Rev WCAG edition, "Essential Requirements for Authors".

Step 3. Test the product, then write

You cannot write an honest ACR from memory or from a scan. The VPAT is a record of testing, so the order is: test, record, rate.

ITI's best-practice list for the Evaluation Methods Used field asks you to say: whether the testers know how the product is normally used; which assistive technologies you used; which manual and automated tools you used; and the name, publisher and link of any published test method (for example the DHS Trusted Tester process or a W3C method). Write it as facts a reader can check: "Manual testing by [name/role] on [dates] with NVDA [version] and Firefox [version], VoiceOver on iOS [version] and Safari, keyboard-only, 200% and 400% zoom; automated checks with axe DevTools [version]."

Step 4. Rate every criterion

For each success criterion in the tables, pick exactly one ITI term:

Term ITI definition
Supports The functionality of the product has at least one method that meets the criterion without known defects, or meets it with equivalent facilitation
Partially Supports Some functionality of the product does not meet the criterion
Does Not Support The majority of product functionality does not meet the criterion
Not Applicable The criterion is not relevant to the product
Not Evaluated The product has not been evaluated against the criterion. Only allowed for Level AAA

Points that trip people up:

Step 5. Write remarks a reviewer will trust

The Remarks and Explanations column is where an ACR is believed or discounted. ITI and Section508.gov agree on the minimum: remarks are required for Partially Supports and Does Not Support, and they should identify the functions or features with issues and how they do not fully support the criterion. If a criterion does not apply, say why. If an accessible alternative exists, describe it.

A good remark answers four questions: where (which screen, component or flow), what (what exactly fails), what the user can do instead (workaround or alternative), and when it will be fixed (a release, or "no date set").

Weak Strong
Supports. We follow WCAG. Supports. All form fields in sign-in, course creation and quiz taking have programmatic labels. Verified with NVDA and VoiceOver (see Evaluation Methods).
Partially Supports. Some issues. Partially Supports. Charts on the Reports page are drawn on a canvas element with no text alternative. The same data is available in the table view and CSV export, both keyboard accessible. Text alternatives are planned for release 5.4.
Not Applicable. Supports. The product has no prerecorded audio or video, so there is no content to which 1.2.2 applies.
Does Not Support. Will fix. Does Not Support. Drag-and-drop ordering questions in the quiz builder cannot be operated with a keyboard or a single pointer. Instructors can use the "Reorder with buttons" setting as an alternative. No release date set.

(Examples are illustrative.) Two habits make the report stronger: cite the evidence behind each rating (date, tool, assistive technology), and do not rate "Supports" on a criterion that a scanner cannot check unless a person checked it. Reviewers who read many ACRs are suspicious of a column of identical "Supports" ratings. An honest "Partially Supports" with a specific remark reads better than a perfect score nobody can verify.

Step 6. Complete the extra chapters for 508 or EU editions

If you use the Revised 508 edition, you fill the WCAG A and AA tables for web content, electronic documents, software and authoring tools, then the 508 chapter tables that apply. Chapter 3 (Functional Performance Criteria) is used if criteria from other chapters do not cover the product. Chapter 4 covers hardware, Chapter 5 software, and Chapter 6 support documentation and services (Section508.gov).

If you use the EU edition, you report against EN 301 549 clauses: functional performance statements (4), generic requirements (5), two-way voice (6), video (7), hardware (8), web (9), non-web documents (10), software (11), documentation and support (12) and relay and emergency services (13). Keep each clause and mark the irrelevant ones Not Applicable with a one-line reason instead of deleting them. The EU edition today maps to EN 301 549 v3.2.1, based on WCAG 2.1 AA. A new version, v4.1.1, was published in September 2026. It adopts WCAG 2.2, but v3.2.1 remains the current reference version until the Commission cites the new one (AccessibleEU). Say which version your report uses.

Step 7. Finish the document

ITI's own checklist for posting a finished report:

  1. Delete the first nine pages of the template (table of contents, introduction and instructions).
  2. Check every required item is present: title, "Based on VPAT® Version 2.5Rev", product and version, report date, description, contact, notes, evaluation methods, applicable standards, terms and the tables.
  3. Check there is a conformance level and a remark for every criterion.
  4. Make sure the final document is accessible (tagged PDF or HTML with real headings, table headers and text alternatives).
  5. Publish it on your website or give it to customers on request.

There is no submission step, no review and no certificate. ITI does not review or approve VPATs, and "there is no VPAT certification" (ITI FAQ). The ACR is your own declaration, which is exactly why a buyer reads it critically.

Seven mistakes buyers notice

Keep it current

An ACR describes one version. When you ship a release that changes the interface, the report may stop being true. ITI's guidance is to change the report date and explain revisions in the Notes, or issue a new report that says it supersedes the earlier one. Put a recurring reminder next to your release process, and keep the older reports visible so a buyer evaluating last year's version can find the right one.

Want it written for you, or kept current?

I am Nabin Karna, the founder of AccessRecord.

Sources

This guide is general information, not legal advice. Confirm the requirement in the solicitation or contract that prompted your request.

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