Compare
VPAT generator for agencies
Procurement asked for a VPAT and you're staring at a blank Word template with 50-odd WCAG success criteria and no idea where to start. Here's the short version and how Gangway shortens it further.
What a VPAT actually is
A Voluntary Product Accessibility Template — a standardized document (the current baseline is VPAT 2.5, aligned to WCAG 2.2 and Section 508) that states, criterion by criterion, whether a product Supports, Partially Supports, Does Not Support, or hasn't been evaluated for that requirement. Procurement teams — especially government and enterprise buyers — ask for one as a baseline filter before they'll even take a sales call.
Filling one out by hand means manually mapping every finding you know about to the right criterion, guessing at ones you haven't checked, and hoping the spreadsheet doesn't drift from reality the next time the site changes.
How Gangway's VPAT draft works
Every finding Gangway tracks already carries its WCAG success criteria (mapped from the axe-core rule that caught it) and its current status. The VPAT draft is generated directly from that data:
- A criterion with an open or in-progress finding → Does Not Support.
- A criterion resolved as won't-fix (with your stated reason) → Partially Supports, reason attached.
- A criterion with everything verified fixed by a rescan → Supports.
- A criterion nothing in the scan touched → Not Evaluated, stated plainly rather than assumed passing.
That last point matters: a VPAT that quietly assumes "not found = passing" is exactly the kind of overclaim that turns into a liability later. Gangway's draft says what it actually knows and nothing more — which is also why it's labeled a draft, meant to save you the mechanical assembly work, not to replace a human accessibility reviewer's sign-off before it goes out under your agency's name.
Available on the Agency and Scale plans, generated per site, versioned alongside your remediation reports and accessibility statement.