VPAT Types Explained - How To Fill Your VPAT (and Why)
So you got asked for a VPAT - or you downloaded one using Wally’s free VPAT generator. Now what?
You’re looking at a template full of “Supports / Partially Supports / Does Not Support” and wondering what buyers actually expect you to write in there.
Here’s the simple truth: a VPAT isn’t impressive because it exists. It’s impressive when it’s specific. The best VPATs make it easy for someone to answer three questions fast:
Which standard are you reporting against?
What did you actually test?
Where does the product work well, and where does it still break?
This guide breaks down the different VPAT types, what needs to be in your VPAT, and why the “remarks” section is where trust is won or lost.
What is a VPAT?
A Voluntary Product Accessibility Template (VPAT) is the standard format used to document how your digital product meets accessibility requirements.
Once you fill it out with real evaluation results, the completed report is commonly referred to as an Accessibility Conformance Report (ACR).
Think of it like this:
Accessibility standards are the rules (WCAG, Section 508, EN 301 549)
VPAT accessibility is how you report your product’s conformance against those rules in a structured way
Why VPAT accessibility matters
A VPAT isn’t just “compliance paperwork.” It’s what helps a buyer answer:
Can our users with disabilities actually use this product?
Can we purchase this without getting dragged into accessibility risk later?
Are you being honest about limitations, or is this just marketing?
VPAT is a way to document your accessibility compliance that makes it easy for everyone to understand where your product stands.
And yes, this overlaps with ADA accessibility expectations in the real world, especially for web and software products.
The different types of VPAT (and which one you should use)
VPAT 2.5 is commonly used today, and it comes in four editions.
VPAT 2.5 Rev 508 (US Federal)
Use this if you’re selling into US federal agencies (or customers who mirror federal procurement). It aligns with Revised Section 508 reporting.
VPAT 2.5 WCAG
Use this when buyers specifically want WCAG-based reporting (common in private sector procurement and many global deals).
VPAT 2.5 EU (EN 301 549)
Use this if you sell into EU public sector or need EN 301 549 reporting.
VPAT 2.5 INT (International)
Use this if you sell across regions and want one report that covers the combined requirements (WCAG + 508 + EN 301 549).
Quick practical rule:
If your buyers are mixed across US + EU, INT is usually safest
If your buyers are only US federal, 508 is usually what they expect
What needs to be in a “good” VPAT (and why buyers care)
This is where most VPATs fall apart. Buyers don’t trust a VPAT that’s just a wall of “Supports.”
Here’s what procurement teams look for:
Clear product scope
Include product name, version, platforms covered (web app, iOS, Android), and what was actually tested. This prevents the classic loophole of a VPAT that only applies to one page or one environment.
Testing methodology
You should clearly state:
What was tested (flows and screens)
Which tools were used (automated + manual)
Which assistive tech was used (screen readers, keyboard, zoom, etc.)
Why it matters: without methodology, your VPAT reads like a claim, not evidence.
Conformance levels with real “Remarks and Explanations”
The remarks column is the whole game.
If you mark Partially Supports, say what doesn’t work and where.
If you mark Does Not Support, say it plainly and mention your plan (if you have one).
Even for Supports, add a short note for criteria that are commonly tricky (like focus order, name-role-value, error handling).
section508.gov explicitly guides vendors on creating an ACR using a VPAT and emphasizes clear reporting - not just checkbox answers.
A “last updated” date and update plan
A VPAT is a snapshot. If your product changes monthly but your VPAT is two years old, buyers will assume it’s unreliable.
A simple step-by-step workflow to build your VPAT
Start with accessibility testing (even a lightweight pass)
If you need a practical process your team can do without specialists,you can check out our How To Conduct Accessibility Reviews Before Launch (without Experts) for more info.
Pick the VPAT edition based on your buyers
WCAG, 508, EU, or INT. Don’t guess - align it to procurement expectations.
Generate the VPAT structure
This is where Wally’s free VPAT generator helps - it gets you a clean, professional template instantly, so you’re not wasting time formatting tables and headings.
Fill it with honest conformance notes
Use real findings. Avoid vague lines like “Meets requirements” with no detail. Buyers hate that.
Publish it and link it from your accessibility page
Pairing your VPAT with an accessibility statement is a strong trust move. If you don’t have one yet, find out How To Create an Accessibility Statement That Actually Means Something
Start free, then go all-in if you need a buyer-ready report
If you’re early in the process, start with Wally’s free VPAT generator to get a solid structure and publish something that’s clean and readable.
If you need a VPAT that stands up in serious procurement conversations, contact Wally to discuss a full 30-day audit by certified accessibility professionals.
We’ll test your product properly, document results clearly, and help you prioritize remediation so your VPAT is based on real evidence - not guesswork.
