Find my businessStart

VPAT accessibility template: free download and a filled-in row

A VPAT is a free form from the Information Technology Industry Council (ITI) that tells a buyer how well your product meets accessibility rules, row by row. The finished form is called an Accessibility Conformance Report, or ACR. This page shows where to get the VPAT accessibility template, which edition to pick, a filled-in example row, and whether a small business needs one at all. We are not lawyers; this is not legal advice.

If a client has asked for a VPAT, the work behind it is a test of your pages. Site Record tests up to 25 pages, writes each fix and rechecks monthly for 12 months: $499 once.

What is a VPAT?

VPAT stands for Voluntary Product Accessibility Template. A company that sells software, a web app or a website service fills it in to say, criterion by criterion, how its product does against a standard such as WCAG. A buyer, often a school, a university, a city or a federal agency, uses the finished report to compare products. ITI, the trade group that publishes the template, describes it as a way for sellers to document conformance. The words "voluntary" and "template" matter: nobody certifies it. It is the seller's own statement.

Because it is a statement you sign, it can be wrong, and a wrong one is a problem. Keep each answer tied to a test you can show.

Does a small business need a VPAT?

Most do not. A dentist, a restaurant or a plumber with a brochure website is not selling a product to buyers who ask for conformance reports. The ADA does not ask for a VPAT, and no regulation for private business websites does either. A VPAT matters when:

If none of those fits you, skip the VPAT and spend the time fixing the errors a scan finds. Our guide to ADA website compliance requirements covers what a private business site faces.

Where to get the VPAT accessibility template

ITI publishes the template free on its website, as a Word document, under the name VPAT. The current version at the time of writing is 2.5, with four editions. Pick the one the buyer names.

EditionMeasures againstPick it when
WCAGThe W3C's WCAG 2.x criteria onlyA private buyer or a school asks for "WCAG 2.1 AA"
Revised Section 508The US federal rules, which point to WCAG 2.0 A and AA plus some software and documentation rulesYou sell to a US federal agency
EU (EN 301 549)The European standard for ICT productsYou sell to European public bodies
INTAll of the above in one reportYou sell in several markets and want one document

Ask the buyer which edition and WCAG version they want before you start. Filling the wrong one wastes the whole job.

How a VPAT is laid out

The form has a header (product name, version, date, contact, the evaluation methods used) and then tables. For the WCAG edition there is one table per level (A, AA and, if you want, AAA). Each row is one success criterion, with three columns:

  1. Criterion, such as 1.4.3 Contrast (Minimum).
  2. Conformance level, one of Supports, Partially Supports, Does Not Support, Not Applicable. "Not Evaluated" is allowed only for AAA criteria.
  3. Remarks and explanations, where you say what you tested and what fails.

The remarks column is where reports are won or lost. "Supports" with no remark reads as a guess. "Partially Supports. The date picker on the booking page cannot be used by keyboard; other form fields are labelled. Fix planned for the December release" reads as a company that tested.

A filled-in VPAT row, with what to write

Here are three rows for an invented booking app, written the way a buyer wants to read them.

CriterionConformance levelRemarks and explanations
1.1.1 Non-text Content (A)SupportsAll images in the app and marketing pages have text alternatives. Decorative icons have empty alt text. Tested with axe DevTools and NVDA on 2026-11-10.
1.4.3 Contrast (Minimum) (AA)Partially SupportsBody text and buttons measure 4.5 to 1 or better. The grey hint text in the search box measures 3.1 to 1. Fix scheduled for version 2.4.
2.1.1 Keyboard (A)Does Not SupportThe date picker on the booking screen opens only on mouse click. A text date field is available as a workaround for users who cannot use the picker. Fix scheduled for version 2.4.

Notice the pattern: what was tested, with what, when; what fails and where; the workaround, if there is one; and when the fix is due. Do not promise a date you cannot keep.

How to fill in a VPAT, step by step

  1. Fix the scope. List the product, version and the pages or screens covered. Say what is out of scope, such as third-party payment pages.
  2. Run automated tests. Use a free scanner on every screen. Our Chrome extension guide compares the tools. Save the results.
  3. Test by hand. Use the keyboard only, a screen reader (NVDA is free on Windows; VoiceOver is built into Mac and iPhone) and 200% zoom. The WCAG 2.1 AA checklist lists what each criterion asks.
  4. Record each finding in an audit sheet. The shape is in our accessibility audit report example.
  5. Map findings to rows. No errors on a criterion across the tested screens: Supports. Some: Partially Supports. The criterion fails everywhere: Does Not Support. Not relevant (no video, so no captions): Not Applicable.
  6. Write remarks for every row that is not a clean Supports, and a short line on the method for the rest.
  7. Have someone else read it, ideally the person who did the hands-on tests. Date it and set a time to redo it, often every release or every year.

How long does a VPAT take?

For a small product with a handful of screens, plan on a few days of testing and writing if you have done accessibility work before, and longer if you have not. The slow part is not the form; it is the hand testing, because the form asks about criteria that scanners cannot judge, such as meaningful sequence, consistent navigation and error suggestion. Doing the audit first, and fixing the blockers, makes the form shorter and the answers better. Buyers will often accept a VPAT that shows honest "Partially Supports" rows with dated fix plans over a flawless-looking one they cannot trust.

Common VPAT mistakes

VPAT or accessibility statement: which one?

They answer different readers. A VPAT is for a buyer comparing products; it is detailed, formal and organised by criterion. An accessibility statement is for visitors; it is short, says what you have done, what is still wrong and how to contact you. A product company may need both. A local business needs only the statement: start with our accessibility statement template.

Can I pay someone to write the VPAT?

Yes. Audit firms write them as part of an audit, and the price depends on the number of screens and the depth of testing; see website accessibility audit cost for published ranges. If you write it yourself, the cost is your time plus whatever audit you buy for evidence. Either way, you sign it, so read every row.

Frequently asked questions

Is a VPAT required by law?

No law requires a company to publish one. Buyers, especially US federal agencies and many schools, ask for one when they buy. It is a request in the sales process.

Is the VPAT accessibility template free?

Yes. ITI publishes the blank template free. You pay only for the testing and the time to fill it.

What is the difference between a VPAT and an ACR?

The VPAT is the blank template. The ACR, the Accessibility Conformance Report, is the filled-in version you give to buyers.

Which WCAG version should I use?

The one the buyer asks for. If they do not say, WCAG 2.1 AA is the common yardstick, and 2.2 AA is the newer one.

Does a VPAT make my site ADA compliant?

No. It documents what you tested. It does not fix errors and no court or agency certifies it.

How often should I update it?

At every major release and at least once a year.

Need the test behind the form? Site Record, $499 once: up to 25 pages, each fix written, monthly rechecks for 12 months. More: all accessibility guides.

Sources

Related: WCAG 2.1 AA checklist PDF.