Home / Guides / How to fill out a VPAT 2.5, section by section
Guide · Updated November 21, 2026
How to fill out a VPAT 2.5, section by section
Each VPAT 2.5 section in order: pick the WCAG, 508, EU or INT edition, write product details and evaluation methods, then fill in the WCAG, 508 and EN 301 549 tables.
A VPAT is a blank template published by ITI. Once you fill it out, it becomes an ACR (Accessibility Conformance Report). This guide follows the template in order and explains what goes in each section, how SaaS products usually handle it, and where people most often go wrong.
Step 1: Choose the right edition
VPAT 2.5 comes in four editions. Pick the one that matches the standard your buyer asks for:
- WCAG edition: reports against WCAG only. Use it for customers who ask only for WCAG.
- 508 edition: reports against the revised Section 508. For web content, that means the 38 WCAG 2.0 Level A and AA criteria. Use it for US federal procurement.
- EU edition: reports against the European standard EN 301 549. Use it for EU public sector procurement and customers affected by the EAA.
- INT edition: covers WCAG, 508 and EN 301 549 in one report. If your customers are spread across several regions, one INT report is usually the least work.
When you download a template, check which WCAG version it lists. If a customer asks for WCAG 2.2, make sure your template includes the criteria added in 2.2, or attach a separate WCAG 2.2 report.
Step 2: The basic information at the top
Product name, version and report date
State the exact version you evaluated (or, for SaaS, the release date) and the date of the report. SaaS products change constantly, and buyers use these dates to decide whether a report is out of date. A common practice is to update it once a year or after every major redesign.
Product description
Say in one or two sentences what the product is and which parts the report covers. For example, state whether it includes the mobile apps, the admin console, the help center and exported PDFs. A clear scope prevents disputes later.
Contact information
Give an email address for accessibility questions that will keep working over time. Do not use a personal inbox.
Notes
Use this field for report-wide notes, such as "This report is based on testing of version X in the following browsers."
Step 3: Evaluation Methods Used
This section decides how much buyers trust the whole report. At a minimum, cover:
- Manual testing: completing the main workflows with a keyboard only, and checking focus order and visible focus.
- Screen readers: which combinations you used, such as NVDA + Firefox, JAWS + Chrome, or VoiceOver + Safari.
- Automated tools: which tools you ran. Automated tools find only some issues and cannot support a conclusion on their own.
- Testers: whether testing was done by your own team or by a third party.
Step 4: Applicable Standards/Guidelines and Terms
In the "Applicable Standards/Guidelines" table, mark the standards and levels this report covers (for example, WCAG 2.2 Level A and AA). The "Terms" section defines the conformance levels; leave the template wording as it is. For how to choose a level, see how to choose VPAT conformance levels.
Step 5: The WCAG tables
These usually come as three tables: Table 1 for Level A, Table 2 for Level AA and Table 3 for Level AAA. Most procurement asks only for A and AA, and every row needs a conformance level and a remark. You can mark Level AAA as Not Evaluated as a whole; this is the only place the template allows Not Evaluated. For how to write remarks, see how to write ACR remarks.
Step 6: The Section 508 report (508 and INT editions)
Besides the WCAG tables, Section 508 has chapters of its own:
- Chapter 3, Functional Performance Criteria (302): for example, whether the product can be used without vision, with limited vision, without hearing or with limited manipulation. You can answer these by summarizing your WCAG test results.
- Chapter 4, Hardware: a pure SaaS product usually marks this Not Applicable.
- Chapter 5, Software (501–504): web content is reported through the WCAG tables. 502 covers interoperability with assistive technology. 504 covers authoring tools; fill it in if your product lets users create web content, for example with an editor or a site builder.
- Chapter 6, Support Documentation and Services (601–603): whether the help center, user guides and support channels are available in accessible formats.
Step 7: The EN 301 549 report (EU and INT editions)
EN 301 549 is organized by clause. A SaaS product usually fills in Clause 4 (functional performance statements), Clause 5 (generic requirements, partly applicable), Clause 9 (web, which maps to WCAG), Clause 10 (non-web documents, if the product produces files such as exported PDFs), Clause 11 (software, for desktop or mobile apps) and Clause 12 (documentation and support services). Clause 6 (two-way voice communication) and Clause 7 (video capabilities) apply only if the product has calling or video features. For details on each clause, see what EN 301 549 is.
Step 8: Legal disclaimer
Reports usually end with a legal disclaimer from the company, stating that the report reflects an evaluation at a point in time. Ask your legal team whether you need one and how to word it.
The five most common mistakes
- Choosing the wrong edition, such as sending a 508 report to a customer who asked for EN 301 549.
- Leaving out the report date or product version, so the buyer cannot tell whether the report is current.
- Listing only automated tools under evaluation methods.
- Copying levels and remarks from another product's ACR.
- Contradicting your public accessibility statement.
Next step
The generator supports the INT, 508 and EU editions. You set a conformance level for each of the nine areas, then download an ACR draft (.docx) and an accessibility statement. After that, use this guide to fill in the evaluation methods and remarks section by section.
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