VPAT Draft DeskStart your VPAT

How to fill out a VPAT template, row by row

The VPAT WCAG edition is a long Word file with bracketed instructions and empty cells. This guide walks through each part and shows what a buyer expects to read in it.

Updated October 1, 2026 · 8 min read

Before you start

Download the current template from ITI and pick the edition your buyer asked for. For most software teams that is the WCAG edition. Decide which WCAG version you’re reporting against (2.1 or 2.2) and which platforms are in scope. If you aren’t sure, read what a VPAT is first.

Delete the template’s instruction text as you go. A finished report with “[Insert notes here]” still in it tells the buyer nobody read it closely.

Product information

The top of the report identifies exactly what you are describing.

  • Name of product and version. Use the version the buyer will actually receive. “Tallyroom Invoicing 4.2” is better than “Tallyroom.”
  • Report date. The date you finished the evaluation. Buyers use it to judge how current the report is.
  • Product description. Two or three sentences a stranger could understand: what it is, who uses it, and what this report covers. Mention exclusions, such as a marketing site or a third-party payment page.
  • Contact information. A named role and an email address that someone actually reads.
  • Notes. Anything that changes how to read the report, such as “Mobile apps are covered in a separate report.”

Evaluation methods used

Describe what your team actually did, in plain language. Name the assistive technology and browsers, with versions if you know them. For example:

ExampleKeyboard-only testing of all core workflows in Chrome and Safari. Screen reader testing with NVDA on Windows and VoiceOver on macOS and iOS. Automated checks with a browser extension, followed by manual review of contrast and reflow at 400% zoom.

Don’t overstate this section. If you didn’t test with a screen reader, don’t list one. A modest, accurate description is more credible than a long list of tools.

Applicable standards and guidelines

The template has a small table where you say which standards and levels the report includes. For a WCAG AA report, you include Level A and Level AA, and say Level AAA was not evaluated. Most buyers don’t expect AAA.

The template also has a “Terms” section defining the four conformance levels. Keep ITI’s definitions as they are.

The conformance tables

The WCAG edition has three tables: Level A, Level AA and Level AAA. Each row is one success criterion with three columns:

  1. Criteria: already filled in, such as “1.4.3 Contrast (Minimum) (Level AA).”
  2. Conformance Level: Supports, Partially Supports, Does Not Support, or Not Applicable.
  3. Remarks and Explanations: your words.

If your report covers several platforms (web, iOS, Android, documentation), you can split each cell by platform, or note platform-specific differences in the remarks. Keep whichever approach you choose consistent across every row.

Choosing the level is the hard part. We cover it in detail in Supports, Partially Supports, Does Not Support, with examples.

Watch the version-specific rows.WCAG 2.2 added six Level A and AA criteria and removed 4.1.1 Parsing. If you start from an older template or copy last year’s report, you can easily miss rows. See what changed in 2.2.

Writing remarks buyers trust

Good remarks are short, specific and factual. They say what works, what doesn’t, and where.

VagueMost images have alt text.
SpecificIcons and form images have text alternatives. The revenue trend chart on the Dashboard has a text summary but no data-table alternative.
  • Name the screen or feature. “The column chooser in Reports” beats “some components.”
  • For Not Applicable, say why: “The product does not contain live audio or video.”
  • For Supports, a short remark is optional but helps where a buyer is likely to ask.
  • Mention fixes only when they are committed, and avoid dates you can’t guarantee.
  • Never write remarks that claim testing you didn’t do.

VPAT Draft Desk gives you a plain-language question and a remark hint for every criterion, so each row reads like this.

Start your VPAT

Finishing touches

  • Add a one-page summary of known gaps near the front. The template doesn’t require it, but reviewers appreciate not having to hunt through 50 rows.
  • Make sure every “Partially Supports” and “Does Not Support” row has a remark.
  • Remove all template instructions and placeholder brackets.
  • Export to PDF for sending, and keep the editable file for the next release.
  • Add your own legal disclaimer if your company requires one. The template leaves space for it.

These guides explain common practice for software vendors. They are not legal advice, and VPAT Draft Desk is not affiliated with ITI or the W3C.