RatedWithAI
Accessibility scanner
Free VPAT Template
2026
A Voluntary Product Accessibility Template (VPAT) documents how your digital product conforms to accessibility standards. It's required for government procurement and increasingly demanded by enterprise buyers.
What Is a VPAT?
A Voluntary Product Accessibility Template (VPAT) is a standardized document created by the Information Technology Industry Council (ITI) that explains how a technology product or service meets accessibility standards.
When you complete a VPAT, the resulting document is called an Accessibility Conformance Report (ACR). While people often use "VPAT" to mean both the template and the completed report, technically the VPAT is the blank template and the ACR is the filled-in version.
The current version is VPAT 2.5 (released 2023), which covers three major accessibility standards:
- WCAG 2.x — Web Content Accessibility Guidelines (international)
- Revised Section 508 — U.S. federal accessibility requirements
- EN 301 549 — European accessibility standard for ICT procurement
Why Do You Need a VPAT?
Government Procurement
Federal agencies require VPATs under Section 508. Without one, your product is automatically disqualified from government contracts worth billions annually.
Enterprise Sales
Large companies (Fortune 500, universities, hospitals) increasingly require accessibility documentation. A VPAT shows you take accessibility seriously.
Legal Protection
With 5,000+ ADA lawsuits filed in 2025, having documented accessibility conformance provides evidence of good-faith compliance efforts.
EU Compliance
The European Accessibility Act (EAA) takes effect June 2025. EN 301 549 VPATs demonstrate conformance for EU market access.
ADA Title II Deadline
State and local governments must comply with WCAG 2.1 AA by April 24, 2026. Vendors serving government need updated VPATs NOW.
Revenue Unlock
Government IT spending exceeds $100B/year. Education budgets add billions more. A VPAT is your ticket to these markets.
VPAT 2.5 Editions Explained
The VPAT 2.5 comes in four editions. Choose based on which markets and regulations apply to your product:
| Edition | Standards Covered | Use When |
|---|---|---|
| WCAG | WCAG 2.x (Level A, AA, AAA) | International products, not targeting specific government regulations |
| Revised Section 508 | WCAG 2.x + Revised Section 508 | Selling to U.S. federal agencies |
| EN 301 549 | WCAG 2.x + EN 301 549 | Selling to European public sector |
| INT (International) | WCAG 2.x + Section 508 + EN 301 549 | Global products targeting both U.S. and EU markets |
Recommendation: If unsure, use the INT edition — it covers all standards and saves you from creating multiple VPATs later.
VPAT 2.5 Templates — Free Download
These are the official ITI VPAT 2.5 templates. Download the edition that matches your target market:
VPAT 2.5 — WCAG Edition
Best for: International products • Format: .doc
VPAT 2.5 — Revised Section 508 Edition
Best for: U.S. government sales • Format: .doc
VPAT 2.5 — EN 301 549 Edition
Best for: EU public sector • Format: .doc
VPAT 2.5 — INT (International) Edition
Best for: Global / both U.S. + EU • Format: .doc
Templates are provided by ITI (Information Technology Industry Council). Always verify you have the latest version at itic.org.
How to Complete a VPAT: Step-by-Step Guide
Run an Accessibility Audit
Before you can document conformance, you need to know your actual accessibility status. Use RatedWithAI's free scanner to get a baseline WCAG 2.1 AA compliance score, then supplement with manual testing for keyboard navigation, screen reader compatibility, and cognitive accessibility.
Run Free Scan →Choose the Right Edition
Select the VPAT edition matching your target market. For most SaaS companies, the INT (International) edition covers all bases. If you're only targeting U.S. federal agencies, the Revised Section 508 edition is sufficient.
Fill in Product Information
Document your product name, version, date of evaluation, contact information, and a description of the product's functionality. Be specific about what was tested — if you only evaluated the web application and not mobile apps, say so.
Evaluate Each WCAG Success Criterion
For each WCAG criterion (there are 78 in WCAG 2.1), rate your conformance level. Use the standard terms: 'Supports' (fully meets), 'Partially Supports' (some aspects don't meet), 'Does Not Support' (majority doesn't meet), or 'Not Applicable' (criterion doesn't apply).
Write Honest Remarks
For every criterion that isn't fully supported, explain specifically what doesn't conform and what your remediation plans are. Honest, detailed remarks build trust with procurement teams. Vague or misleading remarks can backfire badly.
Review and Publish
Have someone else review the VPAT for accuracy and completeness. Then publish it on your website (typically on a dedicated accessibility page or in your documentation). Government agencies and enterprise buyers will look for it there.
Understanding Conformance Levels
When evaluating each criterion in your VPAT, you'll use these standard conformance terms:
Supports
The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially Supports
Some functionality of the product does not meet the criterion.
Does Not Support
The majority of product functionality does not meet the criterion.
Not Applicable
The criterion is not relevant to the product. For example, WCAG 1.2.1 (Audio-only and Video-only) doesn't apply to a text-only product.
Not Evaluated
The product has not been evaluated against the criterion. This should be used sparingly — procurement teams may interpret it negatively.
7 Common VPAT Mistakes to Avoid
1. Claiming "Supports" When It Doesn't
Overstating conformance is the most damaging mistake. Procurement teams test claims — getting caught erodes trust and can disqualify you from future bids. Be honest about gaps and show a remediation plan instead.
2. Using "Not Applicable" Too Liberally
Marking criteria as "Not Applicable" when they actually apply raises red flags. If your product has images, WCAG 1.1.1 (Non-text Content) applies. If it has any interactive elements, keyboard criteria apply.
3. Empty or Vague Remarks
Remarks like "Working on it" or leaving the column blank tells procurement teams nothing. Specify what doesn't conform and when you plan to fix it: "Dashboard charts lack alt text. Remediation planned Q2 2026."
4. Testing Only with Automated Tools
Automated scanners catch ~30-40% of accessibility issues. Manual testing with screen readers (NVDA, JAWS, VoiceOver), keyboard navigation, and cognitive review is essential for an accurate VPAT.
5. Never Updating the VPAT
Your product changes — your VPAT should too. Best practice: update after every major release, or at minimum annually. Date your VPAT prominently so buyers know it's current.
6. Not Specifying What Was Tested
If you only tested the web application but not the mobile app, iOS app, or API documentation, say so. A VPAT covering the wrong product version or platform is useless to procurement.
7. Relying on Accessibility Overlays
Claiming conformance based on an accessibility overlay widget doesn't hold up. Procurement teams know overlays don't fix underlying code issues. 30% of ADA lawsuits in 2023 involved sites using overlays. Learn more about overlay alternatives.
Sample VPAT Entries (Good vs. Bad)
Here are examples of well-written vs. poorly-written VPAT entries for common WCAG criteria:
WCAG 1.1.1 — Non-text Content (Level A)
❌ Bad
Level: Partially Supports
Remarks: "Some images may not have alt text."
✅ Good
Level: Partially Supports
Remarks: "All UI icons and decorative images have appropriate alt attributes. User-uploaded images in the gallery section lack enforced alt text — implementing mandatory alt text field in upload flow, targeted for v3.2 (March 2026)."
WCAG 2.1.1 — Keyboard (Level A)
❌ Bad
Level: Supports
Remarks: "Keyboard accessible."
✅ Good
Level: Partially Supports
Remarks: "All navigation, forms, and primary actions are fully keyboard operable with visible focus indicators. Exception: the drag-and-drop task board requires mouse interaction — keyboard alternative (arrow key reordering) shipping in v3.1 (February 2026)."
Who Reviews Your VPAT?
Understanding who reads your VPAT helps you write it effectively:
- Government procurement officers — They compare VPATs across vendors. They know the standard terms and will flag inconsistencies. They're looking for honesty and a clear remediation roadmap, not perfection.
- IT accessibility coordinators — These specialists understand WCAG deeply. They'll cross-reference your VPAT with their own testing. Overstating conformance is worse than admitting gaps.
- Enterprise purchasing teams — They may not be accessibility experts but are checking a compliance checkbox. A well-organized, complete VPAT moves you forward; a missing or incomplete one stalls the deal.
- Legal/compliance teams — Especially post-lawsuit or in regulated industries (healthcare, financial services, education). They want evidence of systematic accessibility efforts.
⏰ April 24, 2026 Deadline
State & Local Governments Must Comply with WCAG 2.1 AA
The ADA Title II digital accessibility deadline is 61 days away. If you sell to government agencies, having an up-to-date VPAT is now critical. Run a free scan to assess your current status and start your VPAT with real data.
Frequently Asked Questions
Is a VPAT legally required?▼
Not directly — but practically, yes. U.S. federal agencies require VPATs under Section 508 for procurement. Without one, you can't sell to the government. Enterprise buyers increasingly require them too. While you won't be fined for not having a VPAT, you'll lose deals.
How much does it cost to create a VPAT?▼
Creating a VPAT yourself is free — you just fill in the template. However, getting a professional accessibility audit first (which informs the VPAT) typically costs $3,000-$15,000 depending on product complexity. You can start with a free automated scan from RatedWithAI and supplement with manual testing.
How often should I update my VPAT?▼
At minimum annually, or after any major product release that changes functionality. Government agencies may reject VPATs older than 12 months. Best practice: tie VPAT updates to your release cycle.
Can I create a VPAT with automated testing tools alone?▼
No. Automated tools catch 30-40% of WCAG issues. A credible VPAT requires manual testing with assistive technologies (screen readers like NVDA/JAWS/VoiceOver, keyboard navigation, magnification software). Start with automated testing to find the easy wins, then add manual testing.
What's the difference between a VPAT and an ACR?▼
A VPAT (Voluntary Product Accessibility Template) is the blank template. When you fill it in with your product's conformance data, the completed document is called an ACR (Accessibility Conformance Report). People often use 'VPAT' to mean both.
Where should I publish my completed VPAT/ACR?▼
On your website — typically on a dedicated accessibility page, in your product documentation, or in a 'Trust Center' section. Make it easy to find. Some vendors also upload to the Partnership on Employment & Accessible Technology (PEAT) database.
Can RatedWithAI help me fill out a VPAT?▼
Our free scanner evaluates WCAG 2.1 AA criteria and gives you a compliance score with specific findings. This data maps directly to VPAT criteria, giving you a solid starting point. For a complete VPAT, supplement our automated results with manual testing.