VPAT Draft DeskStart your VPAT

Supports, Partially Supports, Does Not Support: choosing VPAT conformance levels

Every row in a VPAT needs one of four conformance levels. Picking the right one, and explaining it well, is most of the work. Here is how to decide.

Updated October 1, 2026 · 7 min read

The four levels

These are the definitions ITI uses in the VPAT template. Your report should repeat them in its Terms section.

LevelMeaning
SupportsThe functionality of the product has at least one method that meets the criterion without known defects, or meets it with equivalent facilitation.
Partially SupportsSome functionality of the product does not meet the criterion.
Does Not SupportThe majority of product functionality does not meet the criterion.
Not ApplicableThe criterion is not relevant to the product.

Some vendors also use Not Evaluated, which ITI reserves for Level AAA criteria. If you haven’t assessed a Level A or AA criterion yet, be explicit about that rather than guessing. VPAT Draft Desk prints such rows as “Not Yet Evaluated” so no one mistakes a gap in your knowledge for a claim.

How to choose

Work through these questions for each criterion, in order:

  1. Does the criterion apply at all? If your product has no video, the captioning criteria don’t apply. Mark them Not Applicable and say why.
  2. Do you know of any place where it fails? If not, and you have actually checked, it’s Supports.
  3. Does it fail somewhere, but most of the product meets it? That’s Partially Supports. This is the most common honest answer, and buyers expect to see plenty of them.
  4. Does most of the product fail it? That’s Does Not Support.
Not Applicable is not a way out.“Not Applicable” means the content the criterion covers doesn’t exist in your product. It doesn’t mean “we haven’t looked” or “it would be hard to fix.” Reviewers notice when a product with a sign-in form marks 3.3.1 Error Identification as Not Applicable.

Example rows

From our sample report for a fictional invoicing product:

2.4.7 Focus VisibleSupportsA visible focus outline appears on all interactive elements.Short and checkable. A Supports remark is optional, but it helps on criteria buyers often test themselves.
1.4.3 Contrast (Minimum)Partially SupportsBody text and controls meet 4.5:1. Placeholder text in search fields measures 3.2:1.Says what passes, what fails, where, and by how much.
1.2.5 Audio Description (Prerecorded)Does Not SupportHelp center tutorial videos do not include audio description. Full transcripts are provided (see 1.2.3).States the gap plainly and points to the alternative that does exist.
1.2.4 Captions (Live)Not ApplicableThe product does not contain live audio or video content.Explains why the criterion doesn’t apply, so the buyer doesn’t read it as a dodge.

You can see every row in context in the full sample report.

Common mistakes

  • All Supports, no remarks. Buyers don’t believe it, and it invites a closer look.
  • Partially Supports with no explanation. The buyer can’t tell if the gap is one icon or the whole checkout.
  • Remarks that argue. “Users rarely need this” or “no customer has complained” weakens the report. State the facts.
  • Promising fixes by a date. If the date slips, your report is wrong. Mention plans only when they’re committed.
  • Mixing platforms silently. If iOS supports a criterion and Android doesn’t, say so in the remark.

VPAT Draft Desk shows how each row will print as you answer it, and flags any partial or unsupported row that has no remark.

Start your VPAT

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.