VPAT (Voluntary Product Accessibility Template)
A Voluntary Product Accessibility Template (VPAT) is a standardized document that describes how an information and communication technology (ICT) product conforms with Section 508 and WCAG 2.x accessibility standards. VPAT 2.5 INT (International, 2025 update) is the current standard. Required by federal procurement for any ICT acquisition; increasingly expected by enterprise B2B buyers.
Also called: VPAT, Accessibility Conformance Report, ACR · Last updated: May 27, 2026 · By Joseph W. Anady
Why it matters.
VPAT is the standardized way to demonstrate accessibility conformance. Without a VPAT, federal agencies cannot procure your ICT product or service. The document is structured around three sections: WCAG 2.x conformance, Revised Section 508 conformance, and EN 301 549 conformance (European equivalent). Each section maps your product/service against specific success criteria with conformance ratings.
How it works.
VPAT documents are voluntary but functionally required for federal ICT procurement. The vendor (or their accessibility consultant) evaluates the product against each WCAG 2.x AA success criterion and Section 508 standard, documenting conformance level (Supports / Partially Supports / Does Not Support / Not Applicable). The completed VPAT becomes the Accessibility Conformance Report (ACR) shared with federal agencies during procurement.
2026 reality check.
VPAT 2.5 INT was released in 2024 and includes updated WCAG 2.2 mapping (added 9 success criteria covering focus appearance, dragging movements, target size, redundant entry). Federal procurement increasingly requires VPAT submission as part of the proposal package, not just at award. Enterprise B2B buyers (especially banking, healthcare, education) request VPATs even when not legally required.
Data points
- VPAT 2.5 INT released 2024 (current standard)
- Maps to WCAG 2.2 AA + Revised Section 508 + EN 301 549
- Required for federal ICT procurement (FAR Part 39 + Section 508)
- Available free from ITI (Information Technology Industry Council) at itic.org
- Federal CO's reject inaccurate VPATs — accuracy matters more than perfect conformance
First-hand insight from ThatDeveloperGuy.
ThatDeveloperGuy delivers VPAT 2.5 INT with every site we build for federal-grade engagements. Our standard VPAT covers WCAG 2.2 AA conformance (more rigorous than the WCAG 2.0 AA baseline required by Section 508) and Revised Section 508 conformance. The VPAT documents our use of axe-core automated testing, NVDA + JAWS + VoiceOver manual testing, keyboard-only navigation verification, and color-contrast validation across the entire deliverable.
How TDG approaches it
TDG's VPAT methodology: axe-core + Pa11y automated CI testing on every build, manual NVDA + JAWS + VoiceOver screen reader walkthrough, keyboard-only navigation verification, color contrast validated at design-system level (not page-by-page), VPAT 2.5 INT document maintained per project with quarterly review cycles. VPAT delivered as PDF at project launch and during federal proposal responses.
Common mistakes.
- Self-evaluating without genuine WCAG audit (federal CO's reject inaccurate VPATs)
- Using outdated VPAT version (must be 2.5 INT as of 2025)
- Conflating 'Supports' rating with 'Partially Supports' (be honest about partial conformance)
- Skipping accessibility overlays disclosure (overlays don't produce true conformance)
- Failing to update VPAT when product changes (becomes stale)
FAQ.
Is a VPAT legally required?
Required for federal procurement of ICT products and services. Voluntary for commercial sales, but increasingly expected by enterprise B2B buyers and government-adjacent organizations.
What version of VPAT should I use?
VPAT 2.5 INT (released 2024) is the current standard as of 2025. Maps to WCAG 2.2 AA + Revised Section 508 + EN 301 549.
Can I write my own VPAT or do I need a consultant?
Self-prepared VPATs are valid but must reflect genuine accessibility evaluation. Federal CO's reject inaccurate VPATs. Most organizations work with accessibility consultants for the formal VPAT preparation.
How long does VPAT preparation take?
For a small site/product: 1-2 weeks with proper accessibility audit. For enterprise products: 4-8 weeks. The audit work is the bulk of the time; documenting the VPAT is mostly recording the findings.
What's the relationship between VPAT and ACR?
VPAT is the document template. ACR (Accessibility Conformance Report) is what you call the completed/published VPAT shared with buyers. Used interchangeably in practice.
Maintained by Joseph W. Anady at ThatDeveloperGuy. Back to glossary · Suggest a term