VPAT generator (2.4 INT)
A Voluntary Product Accessibility Template (VPAT) is the document procurement teams ask you for when they evaluate your product for accessibility. It is a self-disclosure: you state, criterion by criterion, whether you Support, Partially Support, Do Not Support, or Not Applicable. This generator builds a VPAT 2.4 INT-style HTML report covering WCAG 2.1 Level A and AA — the version most US federal and EU buyers expect.
Everything is local in your browser. The export is HTML — Microsoft Word will open it directly.
Per-criterion conformance (WCAG 2.1 A & AA)
| # | Criterion | Level | Conformance | Remarks |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | ||
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | ||
| 1.2.2 | Captions (Prerecorded) | A | ||
| 1.2.3 | Audio Description or Media Alternative | A | ||
| 1.2.4 | Captions (Live) | AA | ||
| 1.2.5 | Audio Description (Prerecorded) | AA | ||
| 1.3.1 | Info and Relationships | A | ||
| 1.3.2 | Meaningful Sequence | A | ||
| 1.3.3 | Sensory Characteristics | A | ||
| 1.3.4 | Orientation | AA | ||
| 1.3.5 | Identify Input Purpose | AA | ||
| 1.4.1 | Use of Color | A | ||
| 1.4.2 | Audio Control | A | ||
| 1.4.3 | Contrast (Minimum) | AA | ||
| 1.4.4 | Resize Text | AA | ||
| 1.4.5 | Images of Text | AA | ||
| 1.4.10 | Reflow | AA | ||
| 1.4.11 | Non-text Contrast | AA | ||
| 1.4.12 | Text Spacing | AA | ||
| 1.4.13 | Content on Hover or Focus | AA | ||
| 2.1.1 | Keyboard | A | ||
| 2.1.2 | No Keyboard Trap | A | ||
| 2.1.4 | Character Key Shortcuts | A | ||
| 2.2.1 | Timing Adjustable | A | ||
| 2.2.2 | Pause, Stop, Hide | A | ||
| 2.3.1 | Three Flashes or Below Threshold | A | ||
| 2.4.1 | Bypass Blocks | A | ||
| 2.4.2 | Page Titled | A | ||
| 2.4.3 | Focus Order | A | ||
| 2.4.4 | Link Purpose (In Context) | A | ||
| 2.4.5 | Multiple Ways | AA | ||
| 2.4.6 | Headings and Labels | AA | ||
| 2.4.7 | Focus Visible | AA | ||
| 2.5.1 | Pointer Gestures | A | ||
| 2.5.2 | Pointer Cancellation | A | ||
| 2.5.3 | Label in Name | A | ||
| 2.5.4 | Motion Actuation | A | ||
| 3.1.1 | Language of Page | A | ||
| 3.1.2 | Language of Parts | AA | ||
| 3.2.1 | On Focus | A | ||
| 3.2.2 | On Input | A | ||
| 3.2.3 | Consistent Navigation | AA | ||
| 3.2.4 | Consistent Identification | AA | ||
| 3.3.1 | Error Identification | A | ||
| 3.3.2 | Labels or Instructions | A | ||
| 3.3.3 | Error Suggestion | AA | ||
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | ||
| 4.1.1 | Parsing | A | ||
| 4.1.2 | Name, Role, Value | A | ||
| 4.1.3 | Status Messages | AA |
When you actually need a VPAT
If you sell to US federal agencies, public universities, or large enterprise buyers, you will be asked for a VPAT during procurement. EU public-sector buyers ask for an equivalent EN 301 549 conformance report, which a VPAT 2.4 INT also covers (the INT variant maps to both Section 508 and EN 301 549). For consumer SaaS, a VPAT is rarely required — but having one accelerates enterprise deals and removes a back-and-forth round during security reviews.
Honest disclosure beats inflated claims
A VPAT that claims full support for criteria you actually fail is worse than no VPAT at all — procurement and legal teams notice, and a misrepresentation can void the contract. Mark partial support honestly, list known exceptions, and commit to a remediation timeline. Buyers reward transparency; they reject lies.
VPAT vs ACR: the terms buyers mix up
A VPAT is the blank template published by the Information Technology Industry Council (ITI). An ACR — Accessibility Conformance Report — is what you have once that template is filled in with findings about your product. Vendors say “send us your VPAT” and mean the completed ACR; the distinction only matters when a procurement officer insists on the formal wording. This generator produces the completed report, so what you download is technically an ACR based on the VPAT 2.4 INT template.
Which VPAT edition and version to use
- VPAT 2.4 / 2.5 INT — covers WCAG, Section 508 and EN 301 549 together. Use this unless a buyer names something else; 2.5 differs mainly in editorial clarifications, and a buyer asking for 2.5 will accept a well-completed 2.4 INT in practice.
- VPAT WCAG edition — WCAG criteria only. Enough for a private-sector buyer who just wants the conformance picture.
- VPAT 508 edition — US federal procurement only.
- VPAT EU edition — EN 301 549 only, for European public-sector tenders.
On the standard itself: report against WCAG 2.1 AA as the baseline, because that is what Section 508, EN 301 549 and the European Accessibility Act all reference. Adding WCAG 2.2 criteria on top is a differentiator, not yet a requirement — no major procurement regime mandates 2.2 as of 2026.
VPAT vs HECVAT and other procurement documents
Higher-education buyers frequently request a HECVAT alongside a VPAT, and the two are not substitutes. HECVAT is a security and privacy questionnaire; the VPAT/ACR is the accessibility conformance report. A full HECVAT does contain accessibility questions, but they ask whether a VPAT exists rather than replacing it. Similarly, a VPAT is not a VAPT — vulnerability assessment and penetration testing is a security exercise with an unfortunately similar acronym.
How to fill each conformance level
Every criterion takes one of four values, and using them precisely is what makes a report credible:
- Supports — the product meets the criterion with no known exceptions.
- Partially supports — some functionality does not meet it. Name what, specifically.
- Does not support — the majority of functionality fails it.
- Not applicable — the criterion has no bearing on the product (no video, so no captions).
The remarks column carries the weight. “Partially supports” with an empty remark reads as evasion; the same value with “date picker in the booking flow is not keyboard operable, fix scheduled Q4” reads as a vendor who tested their product. Run a scan first so the remarks describe measured findings rather than guesses, and pair the report with a public accessibility statement.