VPATFast.com

Home / Guides / How to choose VPAT conformance levels

Guide · Updated November 21, 2026

How to choose VPAT conformance levels

What the five conformance levels in a VPAT 2.5 ACR mean, how to choose one for each criterion, and the most common mistakes: when to use Partially Supports, when Not Applicable is allowed, and where Not Evaluated fits.

Every criterion in an ACR (a completed VPAT) gets a conformance level, with a remark next to it that explains the choice. Buyers often scan this column first, so a wrong level draws more questions than a missing sentence in the remarks. This guide follows the definitions in the VPAT 2.5 template.

What the five levels mean

The template defines them in its Terms section. Below is a plain summary; when you fill out the report, use the wording of the official template you downloaded and do not edit that section.

LevelMeaning
SupportsThe functionality of the product 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 the product's functionality does not meet the criterion.
Not ApplicableThe criterion is not relevant to the product, for example because the product has no content of that kind.
Not EvaluatedThe product has not been evaluated against the criterion. The template allows this only for WCAG Level AAA criteria.

Choose with three questions

  1. Does the product have this kind of content? Only if it does not is the answer Not Applicable. For example, if the product has no prerecorded video at all, 1.2.2 Captions (Prerecorded) can be Not Applicable, with the remark "The product does not contain prerecorded video."
  2. Did testing find anything that fails? If nothing fails, choose Supports. If there is any known issue, it cannot be Supports.
  3. Is the problem local or widespread? If it affects some pages or some components, choose Partially Supports. If the core workflows generally fail, choose Does Not Support.

The four most common misuses

  • Supports despite known issues. The buyer's testers find them as soon as they open the product, and the whole report loses credibility.
  • Not Applicable for something nobody tested. If the help center has tutorial videos, the 1.2.x criteria are not Not Applicable. If you have not tested, test first and fill in the report afterwards.
  • Not Evaluated on a Level A or AA criterion. The template does not allow it, and buyers usually expect a conclusion for every A and AA criterion.
  • Partially Supports without a remark. A level with no explanation leaves the buyer unable to judge the impact, and they tend to assume the worst. See how to write ACR remarks.

An all-Supports report looks suspicious

Almost no product meets all 55 WCAG 2.2 A and AA criteria without a single defect. Experienced buyers who see an "all green" ACR ask about the test methods and dates. A few honest Partially Supports entries with clear remarks and workarounds usually pass review more easily than a report that says Supports everywhere.

Keep levels consistent with your statement

If you also publish an accessibility statement, every issue in its known limitations section should appear in the ACR as Partially Supports or Does Not Support. Documents that contradict each other are a common finding in procurement reviews.

Next step

The generator sets levels by area: all criteria in one of the nine areas share a level. In the exported .docx you can then adjust levels and remarks row by row as described above. The result is a self-assessed draft; confirm it against your actual test results before you publish it.

Ready to draft your ACR?

The preview is free. US$49 one-time per product to download the ACR and the statement.

Open the generator