If you sell software to schools or colleges, sooner or later someone will ask for your VPAT. If you buy it, you will be handed one. Both sides need to know what the document is and how it is supposed to be filled out.

The Voluntary Product Accessibility Template (VPAT®) is a free template from the Information Technology Industry Council (ITI), a tech trade group. Vendors test their product against accessibility standards and record the results in it. "Once completed, the VPAT® with documented testing results is referred to as an Accessibility Conformance Report (ACR)," ITI explains (ITI). In short: the VPAT is the blank form, and the ACR is the filled-in report about one product.

Download the sample VPAT report (Word, free with email signup)

Why schools and colleges ask for one

The VPAT was built for U.S. federal purchasing under Section 508, but many organizations outside the federal government now require one. "This includes K-12 schools and institutions of higher education," notes CAST, the education nonprofit (CAST).

The pressure is rising. The Justice Department's ADA Title II rule requires public schools, colleges and universities to make web content and apps meet WCAG 2.1 Level AA, with compliance dates of April 26, 2027 for larger entities and April 26, 2028 for smaller ones. Much of that content runs on vendors' platforms, which is why procurement teams ask for reports. Our guide to the federal accessibility rules has the details.

The four editions, and which one to use

ITI's current version is VPAT 2.5Rev, released April 24, 2025. It comes in four editions, each covering different standards (ITI):

Edition

Standards covered

WCAG version inside

508

Revised Section 508 (U.S. federal)

WCAG 2.0

EU

EN 301 549 (European public procurement)

WCAG 2.1

WCAG

Web Content Accessibility Guidelines

WCAG 2.0, 2.1 and 2.2

INT (International)

All three of the above

WCAG 2.2

Which to choose:

  • Selling to federal agencies: use the 508 or INT edition. Section508.gov says vendors selling to the federal government "must use the Revised Section 508 or the INT International Editions" (Section508.gov).
  • Selling to U.S. schools and colleges: because the Title II rule requires WCAG 2.1 AA, a report from the 508 edition alone, which covers WCAG 2.0, will not answer the question schools now have to ask. The WCAG edition, or the INT edition if you also sell to federal agencies or in Europe, covers WCAG 2.1 and 2.2.
  • Selling in Europe: use the EU or INT edition.

Download the template from ITI itself. It is free, and ITI membership is not required (ITI).

What's inside the template

The Word file has two parts: about nine pages of instructions, and the report itself. When you publish, you delete the instructions. The report has these parts:

1. The report header. ITI's minimum requirements are:

  • A title in the form "[Company Name] Accessibility Conformance Report"
  • The VPAT version the report is based on
  • The product name and version
  • The report date, at least month and year
  • A brief product description
  • Contact information; an email address is enough
  • Notes (may be blank)
  • Evaluation methods used: how the product was tested
  • The standards and guidelines the report covers, with only the WCAG versions actually evaluated

2. The terms. Every answer uses one of five terms, and the report must define them. ITI's definitions:

Term

ITI definition

Supports

"The functionality of the product has at least one method that meets the criterion without known defects or meets 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. This can only be used in WCAG Level AAA criteria."

Two details trip people up. First, "Not Evaluated" is allowed only at Level AAA, so every Level A and AA criterion must get a real answer. Second, where there is no content a criterion applies to, ITI notes that a vendor may answer "Supports" rather than "Not Applicable," in line with WCAG's own conformance rules. A product with no video can answer "Supports" for the caption criteria and explain why.

3. The criteria tables. In the WCAG edition, the success criteria sit in three tables, Level A, Level AA and Level AAA, each with three columns: Criteria, Conformance Level, and Remarks and Explanations. Rows marked "2.1 and 2.2" or "2.2 only" show which WCAG version added each criterion.

4. A legal disclaimer section, optional, for any text your organization requires.

How to build one, step by step

Step 1: Define what you are reporting on. One product and one version. If your product has distinct parts, such as a web app, mobile apps and an authoring tool, ITI allows separate reports, as long as each report's notes explain how to find the others.

Step 2: Pick the edition and download it from ITI. See the guidance above.

Step 3: Test the product. A VPAT is only as good as the testing behind it. ITI suggests describing testing by people who know how the product is used, testing with assistive technologies, manual and automated testing tools, and any published test method you followed (ITI). For web products, Section508.gov points to the ICT Accessibility Testing Baseline for Web and the federal Trusted Tester process (Section508.gov). In practice, that means keyboard-only testing, screen reader testing, zoom and reflow checks, contrast measurement, and an automated checker to catch the rest.

Step 4: Fill in the header. Be specific about the version and the date. CAST advises that the contact should be someone who knows the product's accessibility features, ideally on the accessibility team (CAST).

Step 5: Answer every criterion at the levels you report. "When reporting on a level (A, AA or AAA) all criteria for that level must be answered" for the WCAG version the report covers, ITI's instructions say. Most schools will expect Levels A and AA.

Step 6: Write remarks that a buyer can act on. For "Partially Supports" or "Does Not Support," ITI says remarks should identify the functions or features with issues and how they fall short. If a criterion does not apply, explain why. If there is an accessible alternative, describe it. ITI also suggests adding known workarounds and a way to get more information, such as a bug ID. Section508.gov says remarks are required for partial or non-support and encouraged for "Supports" (Section508.gov).

Here is the difference, using rows from our sample report:

Criterion

Answer

Weak remark

Remark a buyer can use

2.1.1 Keyboard

Partially Supports

"Some keyboard issues."

"All functions work with a keyboard except the 'ordering' question type, where students must drag items into place (issue EQB-388). Workaround: teachers can use the 'numbered list' question type, which is fully keyboard operable."

1.4.3 Contrast (Minimum)

Partially Supports

"Mostly meets contrast."

"Body text, labels and buttons meet a 4.5:1 contrast ratio. Placeholder text in the question editor measures 3.2:1 (issue EQB-417)."

2.1.4 Character Key Shortcuts

Supports

(blank)

"The product does not use single-character keyboard shortcuts."

Step 7: Trim only what the rules allow. You may delete whole sections, not individual criteria. You can delete the Level AAA table if you didn't evaluate it, and drop the "2.1 and 2.2" and "2.2 only" rows if you report only on WCAG 2.0. If you remove anything a customer has agreed doesn't apply, say so in the notes.

Step 8: Remove the instructions, check and publish. Delete the instruction pages, check that every required item is present and that every criterion has both a conformance level and a remark, and make sure the report itself is accessible. Then post it on your website or provide it on request. When you revise it, change the report date and explain the change in the notes.

Rules for using the VPAT name

The VPAT name and template are ITI registered service marks. A report that uses them must include the ® symbol, and authors agree to follow ITI's essential requirements; "[d]eviating from these guidelines precludes vendors from referencing the template by name." You may reproduce the template in another format such as HTML or PDF, as long as the final report is accessible. ITI does not review or approve VPATs (ITI).

Common mistakes

A completed VPAT is the vendor's own claim, not a certification. How buyers should read and test those claims is the subject of a separate guide.

Sources

  1. VPAT. Information Technology Industry Council (ITI) (2025)
  2. How to Create an Accessibility Conformance Report Using A Voluntary Product Accessibility Template (VPAT®). Section508.gov (2026)
  3. Understanding Vendor Claims in Accessibility Conformance Reports for Section 508 Conformance. Section508.gov (2026)
  4. How to Understand the VPAT®. CAST (2026)