VPAT Generator: Free Accessibility Conformance Report

Everything stays in your browser. Save a draft file to keep your work.

Product information

Company

Product name

Product version

Report date

Product description

Contact information

Notes

Evaluation methods used

Scope

WCAG version Include Level AA Include Level AAA Section 508 functional performance criteria

Legal disclaimer (optional)

1 of 50 rows rated2%

Show only unassessed rows

Table 1: Level A success criteria

1/30

Set every unassessed row to

1.1.1 Non-text ContentUnderstanding 1.1.1 (opens in a new tab)
1.2.1 Audio-only and Video-only (Prerecorded)Understanding 1.2.1 (opens in a new tab)
1.2.2 Captions (Prerecorded)Understanding 1.2.2 (opens in a new tab)
1.2.3 Audio Description or Media Alternative (Prerecorded)Understanding 1.2.3 (opens in a new tab)
1.3.1 Info and RelationshipsUnderstanding 1.3.1 (opens in a new tab)
1.3.2 Meaningful SequenceUnderstanding 1.3.2 (opens in a new tab)
1.3.3 Sensory CharacteristicsUnderstanding 1.3.3 (opens in a new tab)
1.4.1 Use of ColorUnderstanding 1.4.1 (opens in a new tab)
1.4.2 Audio ControlUnderstanding 1.4.2 (opens in a new tab)
2.1.1 KeyboardUnderstanding 2.1.1 (opens in a new tab)
2.1.2 No Keyboard TrapUnderstanding 2.1.2 (opens in a new tab)
2.1.4 Character Key Shortcuts (new in 2.1)Understanding 2.1.4 (opens in a new tab)
2.2.1 Timing AdjustableUnderstanding 2.2.1 (opens in a new tab)
2.2.2 Pause, Stop, HideUnderstanding 2.2.2 (opens in a new tab)
2.3.1 Three Flashes or Below ThresholdUnderstanding 2.3.1 (opens in a new tab)
2.4.1 Bypass BlocksUnderstanding 2.4.1 (opens in a new tab)
2.4.2 Page TitledUnderstanding 2.4.2 (opens in a new tab)
2.4.3 Focus OrderUnderstanding 2.4.3 (opens in a new tab)
2.4.4 Link Purpose (In Context)Understanding 2.4.4 (opens in a new tab)
2.5.1 Pointer Gestures (new in 2.1)Understanding 2.5.1 (opens in a new tab)
2.5.2 Pointer Cancellation (new in 2.1)Understanding 2.5.2 (opens in a new tab)
2.5.3 Label in Name (new in 2.1)Understanding 2.5.3 (opens in a new tab)
2.5.4 Motion Actuation (new in 2.1)Understanding 2.5.4 (opens in a new tab)
3.1.1 Language of PageUnderstanding 3.1.1 (opens in a new tab)
3.2.1 On FocusUnderstanding 3.2.1 (opens in a new tab)
3.2.2 On InputUnderstanding 3.2.2 (opens in a new tab)
3.3.1 Error IdentificationUnderstanding 3.3.1 (opens in a new tab)
3.3.2 Labels or InstructionsUnderstanding 3.3.2 (opens in a new tab)
4.1.1 ParsingUnderstanding 4.1.1 (opens in a new tab)
For WCAG 2.0 and 2.1, the W3C errata published in 2023 state that 4.1.1 Parsing is always satisfied for content written in HTML or XML.
4.1.2 Name, Role, ValueUnderstanding 4.1.2 (opens in a new tab)

Table 2: Level AA success criteria

0/20

Set every unassessed row to

1.2.4 Captions (Live)Understanding 1.2.4 (opens in a new tab)
1.2.5 Audio Description (Prerecorded)Understanding 1.2.5 (opens in a new tab)
1.3.4 Orientation (new in 2.1)Understanding 1.3.4 (opens in a new tab)
1.3.5 Identify Input Purpose (new in 2.1)Understanding 1.3.5 (opens in a new tab)
1.4.3 Contrast (Minimum)Understanding 1.4.3 (opens in a new tab)
1.4.4 Resize TextUnderstanding 1.4.4 (opens in a new tab)
1.4.5 Images of TextUnderstanding 1.4.5 (opens in a new tab)
1.4.10 Reflow (new in 2.1)Understanding 1.4.10 (opens in a new tab)
1.4.11 Non-text Contrast (new in 2.1)Understanding 1.4.11 (opens in a new tab)
1.4.12 Text Spacing (new in 2.1)Understanding 1.4.12 (opens in a new tab)
1.4.13 Content on Hover or Focus (new in 2.1)Understanding 1.4.13 (opens in a new tab)
2.4.5 Multiple WaysUnderstanding 2.4.5 (opens in a new tab)
2.4.6 Headings and LabelsUnderstanding 2.4.6 (opens in a new tab)
2.4.7 Focus VisibleUnderstanding 2.4.7 (opens in a new tab)
3.1.2 Language of PartsUnderstanding 3.1.2 (opens in a new tab)
3.2.3 Consistent NavigationUnderstanding 3.2.3 (opens in a new tab)
3.2.4 Consistent IdentificationUnderstanding 3.2.4 (opens in a new tab)
3.3.3 Error SuggestionUnderstanding 3.3.3 (opens in a new tab)
3.3.4 Error Prevention (Legal, Financial, Data)Understanding 3.3.4 (opens in a new tab)
4.1.3 Status Messages (new in 2.1)Understanding 4.1.3 (opens in a new tab)

Export the report

Rows you have not rated show as "[Not yet assessed]" in Level A and AA tables and as "Not Evaluated" in the Level AAA table. This tool formats your own findings; it does not certify conformance.

Follow @mytoolstudio

How to use

Describe the product and scope

Fill in company, product name and version, report date, description, contact, notes and evaluation methods. Pick the WCAG version, tick Level AA or AAA, and add the Section 508 table if a US federal buyer needs it.

Rate each criterion

For every row choose a conformance level and write remarks that say what works and what does not. Use Set every unassessed row to for quick passes, or Import checker result to pre-fill failed checks.

Export and save

Click Word (.docx), HTML, CSV or Markdown, or copy the Markdown or HTML. Click Save draft to keep a JSON file you can load again when the product changes.

Why VPAT Generator

Every WCAG 2.0, 2.1 or 2.2 criterion in the VPAT 2.5 table layout.
Optional Section 508 Chapter 3 functional performance criteria table.
Pre-fill failures from our accessibility checker's JSON result.
Word, HTML, CSV and Markdown exports; draft files instead of an account.

What goes into each part of the report

A conformance report is read by procurement teams who compare several products, so each part has a fixed place. The generator keeps that order and fills in the standard wording for the terms section.

Part	What to write
Product information	Name and version, report date, a short description and a contact for accessibility questions
Evaluation methods	How you tested: automated tools, keyboard testing, which screen readers and browsers
Applicable standards	Which WCAG version and levels the report covers, and whether Section 508 Chapter 3 is included
Criteria tables	A conformance level and remarks for every success criterion at each included level
Legal disclaimer	Your own wording; a short default says the report is for information and not a warranty

Using automated results without overclaiming

Automated checks find a useful share of problems, such as missing alt text, low contrast and unlabeled fields. They cannot confirm that a criterion is fully met, and several criteria, like keyboard traps or caption accuracy, need a person to test them.

When you import a checker result, criteria with failed checks become Partially Supports and the failures are listed in the remarks. Review each one: if most of the product fails, change it to Does Not Support. Rate the rest only after manual testing.

Common questions

What is a VPAT and how is it different from an ACR?

A VPAT (Voluntary Product Accessibility Template) is the blank template published by the Information Technology Industry Council. Once you fill it in for a product, the result is called an Accessibility Conformance Report, or ACR. Buyers often say VPAT when they mean the completed report.

Which VPAT edition does this generator follow?

It follows the layout of the VPAT 2.5 WCAG edition: product details, evaluation methods, applicable standards, terms, and one table per WCAG level. You can add the Section 508 Chapter 3 functional performance criteria. The full 508, EU and international editions include more chapters, such as hardware and support documentation, that this tool does not cover.

What do Supports, Partially Supports and Does Not Support mean in a VPAT?

Supports means the product meets the criterion without known defects. Partially Supports means some functionality does not meet it. Does Not Support means most functionality does not meet it. Not Applicable means the criterion is not relevant, and Not Evaluated may only be used for Level AAA criteria.

Can this VPAT generator test my product for me?

No. It formats your findings into a report. You can import a JSON result from our accessibility checker to mark criteria with failed automated checks as Partially Supports, but it never marks anything as Supports for you, because automated checks cannot prove a criterion is met.

How should I write remarks in a VPAT?

Say what works and what does not, in plain terms, for each criterion you do not fully support. Name the feature, describe the barrier and mention any workaround or planned fix. Buyers read the remarks more closely than the conformance labels.

Why does 4.1.1 Parsing start as Supports in the VPAT?

For WCAG 2.0 and 2.1, the W3C errata published in 2023 say 4.1.1 Parsing is always satisfied for content written in HTML or XML. The generator fills that row in with an explanation, and you can change it. In WCAG 2.2 the criterion no longer exists, so it does not appear.

Which WCAG version should my VPAT report against?

Use the version your buyers ask for. US federal buyers under Section 508 need WCAG 2.0 A and AA at minimum. Many private and EU buyers now ask for WCAG 2.1 AA, and some ask for 2.2. Reporting against a newer version covers the older one, since newer versions include the older criteria.

Is my VPAT data uploaded anywhere?

No. The report is built in your browser, and downloads are created on your device. Nothing is saved on our server, so click Save draft to keep a JSON copy of your answers.

Can I edit the VPAT Word file after downloading?

Yes. The .docx file uses normal headings and tables in landscape pages, so you can add a logo, change fonts or add sections in Word, Google Docs or LibreOffice before you send it.

How often should a VPAT be updated?

Update it for each major release, after a new accessibility audit, and whenever a fix changes a conformance level. Many buyers expect a report dated within the last year. Loading your saved draft makes the update a short job.