AccessRecord

VPAT template for software and edtech vendors: which one to use and how to fill it in

By Nabin Karna · Published

If you sell software to schools, colleges or any organization with a procurement office, you will be asked for a completed VPAT. This page tells you where to get the template, which of its four editions fits a software or edtech product, what is inside it, and which rows deserve the most attention when your product is a web app, a learning platform or a student-facing tool.

Short answer: download the WCAG edition of VPAT 2.5Rev from ITI (it is free), complete the Level A and Level AA tables for WCAG 2.2, and add the Revised 508 or EU edition only if a buyer asks for it. The template is a Word file. The finished document is called an Accessibility Conformance Report (ACR).

Where to get the official template

The VPAT is published by the Information Technology Industry Council (ITI). The current version is VPAT 2.5Rev, dated April 2025, free at itic.org/policy/accessibility/vpat. You do not need to be an ITI member. ITI asks that the VPAT name and report form not be altered without its permission, and that you use "VPAT®" with the registered mark.

You should always use the official template from ITI for a report you call a VPAT. AccessRecord also offers a free worksheet that lays out every WCAG 2.2 A and AA criterion in the same order and columns, to help you plan testing (AccessRecord VPAT worksheet). It is not the ITI template and does not replace it.

Which edition should a software or edtech vendor use?

ITI publishes four editions. They differ in which standards they include:

Edition Standards inside Use it for software and edtech when...
WCAG WCAG 2.0, 2.1 and 2.2 Default choice. Schools, colleges, universities, state and local agencies and companies asking for WCAG conformance
Revised 508 Revised Section 508 Standards (WCAG 2.0 for web) plus chapters for hardware, software and support documentation You sell to US federal agencies, or the solicitation names Section 508
EU EN 301 549 (v3.2.1, WCAG 2.1 for web) You sell to EU public bodies or respond to EU tenders
INT All of the above You sell across those markets and want one document

For a typical SaaS or edtech product sold to US schools, the WCAG edition is what buyers mean when they say "VPAT". It is also the right fit for the ADA Title II rule, which sets WCAG 2.1 AA as the standard for public schools, community colleges and public universities. The compliance dates are 26 April 2027 (public entities of 50,000 people or more) and 26 April 2028 (all others) (Federal Register, 20 April 2026). Because WCAG 2.2 builds on 2.1, reporting against 2.2 also answers a 2.1 requirement.

If a solicitation names an edition or a WCAG version, use that. Federal sellers must use the Revised 508 or INT edition (Section508.gov).

What is inside the WCAG edition

Pages 1 to 9 are instructions, and you delete them before publishing. The report itself has:

  1. Header block: report title, "Based on VPAT® Version 2.5Rev", product name and version, report date, product description, contact, notes and evaluation methods.
  2. Applicable standards: a small table marking which WCAG versions and levels the report covers (yes or no).
  3. Terms: the five ITI conformance terms: Supports, Partially Supports, Does Not Support, Not Applicable and Not Evaluated (the last only for Level AAA).
  4. Table 1, Level A: 32 rows, of which 31 apply to WCAG 2.2, because 4.1.1 Parsing is obsolete there.
  5. Table 2, Level AA: 24 rows.
  6. Table 3, Level AAA: optional. If you do not evaluate AAA, delete this table.

Each table has three columns: the criterion, the conformance level and the remarks. Rows are marked "2.1 and 2.2" or "2.2 only" so you can drop the newer rows if you report only on an older WCAG version. You cannot delete individual criteria, only whole sections. (Source: the ITI VPAT 2.5Rev WCAG edition template.) For the writing steps, see How to write a VPAT.

A copy-ready header for a SaaS or edtech product

Use this as a skeleton and replace everything in brackets. The wording follows ITI's required header fields.

[Company name] Accessibility Conformance Report
WCAG Edition (Based on VPAT® Version 2.5Rev)

Name of Product/Version: [Product name], web application, release [x.y]
Report Date: [Month D, YYYY]
Product Description: [Two or three sentences: who uses it (students, teachers, admins) and what it does]
Contact Information: [accessibility@yourcompany.com]
Notes: This report covers the [web application at app.example.com] as of release [x.y].
  It does not cover [native iOS/Android apps / customer-authored content / third-party embedded tools]. 
  [Link to a separate report for the mobile apps, if any.]
Evaluation Methods Used: Manual testing by [name/role] on [dates] using keyboard only, NVDA [version] with
  Firefox [version], VoiceOver with Safari [version], and 200% and 400% zoom. Automated checks with
  axe DevTools [version]. Testers [do / do not] have working knowledge of the product's normal use.
Applicable Standards/Guidelines: WCAG 2.2 Level A (Yes), Level AA (Yes), Level AAA (No)

Rows that need extra attention for software and edtech

Every row must be answered, but some deserve more testing and longer remarks in learning and SaaS products. These are the ones reviewers look at first, with the questions to ask yourself:

Criterion Why it matters here Ask yourself
2.1.1 Keyboard, 2.1.2 No Keyboard Trap A student must finish a lesson or quiz without a mouse Can I complete sign-in, the core task and submission with only the keyboard? Can I leave every modal and embedded player?
2.5.7 Dragging Movements (2.2 only) Drag-and-drop matching, sorting and ordering are common in learning tools Is there a non-drag way to do the same thing, such as buttons or a menu?
2.2.1 Timing Adjustable Timed quizzes and session timeouts Can a user extend or turn off the time limit, or is there an accommodation setting?
1.2.2 Captions, 1.2.5 Audio Description, 1.2.4 Live Captions Lesson videos and live sessions Do all videos you control have captions? What about audio description and live sessions?
1.3.1 Info and Relationships, 4.1.2 Name, Role, Value Custom components: grids, tabs, rich-text editors, equation inputs Does a screen reader announce the control's name, role and state correctly?
4.1.3 Status Messages "Answer saved", score feedback, error and timer updates Are updates announced without moving focus?
3.3.1 Error Identification, 3.3.2 Labels, 3.3.3 Error Suggestion, 3.3.4 Error Prevention Forms, assessments, gradebooks, data submission Are errors described in text and linked to the field? Can submissions be reviewed or reversed?
3.3.7 Redundant Entry, 3.3.8 Accessible Authentication (2.2 only) Rostering, login, SSO and password flows Do I ask users to re-enter the same data, or to solve a puzzle to log in?
1.4.10 Reflow, 1.4.4 Resize Text, 1.4.12 Text Spacing Students on small screens, zoom or custom text settings Does content reflow at 320 CSS pixels wide without two-direction scrolling?
1.4.3 Contrast, 1.4.11 Non-text Contrast Charts, icons, input borders Do graphs and form borders meet 3:1? Does text meet 4.5:1?
2.4.11 Focus Not Obscured (2.2 only), 2.4.7 Focus Visible Sticky headers, cookie banners and chat widgets Does focus ever disappear behind a fixed element?
1.3.4 Orientation, 2.5.1 Pointer Gestures, 2.5.4 Motion Actuation Tablets and phones in classrooms Does it work in both orientations, without complex gestures or shake-to-undo?
1.1.1 Non-text Content Images, diagrams and charts in content Do your own images have meaningful alternatives? Does your editor prompt authors for alt text?

Three scoping questions that decide how long your report is

  1. Content created by teachers or admins. If your product lets users author lessons or pages, say whether the authoring tool is in scope, and what your tool does to help authors produce accessible output (prompts for alt text, caption fields, heading structure). In the 508 and INT editions there are separate "Authoring Tool" rows.
  2. Third-party and embedded tools. Video players, LTI tools, maps and payment pages are often part of what the user experiences. State which are covered and link to the third party's report if one exists.
  3. Native apps. If you ship iOS or Android apps, report on them as well, naming platform and OS versions. ITI allows multiple reports for a complex product as long as each report's Notes explains how to reach the others.

What buyers do with the finished document

Procurement and accessibility staff typically check the date and version first, then the evaluation methods, then read the remarks on the criteria that matter to their users. Reports that are undated, name no product version, show "Supports" on every row without evidence, or cite an outdated WCAG version are the ones that draw follow-up questions. Many universities pair the ACR request with a security questionnaire such as HECVAT.

Remember that ITI does not review or approve any VPAT and "there is no VPAT certification". You complete and publish it as the product owner. If a solicitation or contract requires third-party testing, follow that requirement.

Template checklist

Don't want to fill it in yourself?

I am Nabin Karna, the founder of AccessRecord.

Sources

This guide is general information, not legal advice.

Data behind several of these guides: The State of Edtech VPATs 2026.