Auto-drafted VPAT from your accessibility audit
A VPAT (Voluntary Product Accessibility Template) is the standard document procurement teams — especially US federal agencies under Section 508 — ask vendors to produce before they’ll buy. The format is well-defined. Filling it out is tedious. Consultants charge $5,000 to $50,000 and weeks of turnaround.
We’re considering a generator that takes your ScanAble audit and produces a pre-filled VPAT draft — conformance statuses derived from real findings, remarks pre-populated with the WCAG criteria each finding maps to, blank where human judgment is genuinely needed. You finish the draft, export to Word, hand to procurement.
What you’d get
Pre-filled conformance
Each WCAG criterion auto-marked Supports / Partially Supports / Does Not Support / Not Applicable based on what the scan can determine.
Honest blanks
Criteria that genuinely need human review (keyboard nav flow, screen reader UX, alt-text quality) are left blank with a one-line note explaining what to evaluate.
Standards covered
WCAG 2.0 / 2.1 / 2.2 Level A and AA, Section 508 (Revised), and EN 301 549 — the three tables most procurement teams ask for.
Editable export
Word document (and PDF) with your branding. Edit before sending to procurement; the auto-fill is a starting point, not a final answer.
Tentative pricing & honest caveats
Likely $199 standalone, or bundled with the $149 Site Audit for $299 combined (instead of the $348 you’d pay for the two SKUs separately). Prices subject to change before launch.
An auto-drafted VPAT is a starting point, not a certified accessibility opinion.
Automated tools catch ~30–40% of WCAG issues per Deque’s research. The remaining 60–70% — keyboard navigation, screen reader UX, focus management, alt-text quality — require manual review by a person who knows what they’re doing. Anyone selling you a fully-automated VPAT is misrepresenting the technology. Our draft would be honest about that. If you’re selling into a high-stakes procurement (federal contracts, healthcare, finance), pair this with a human review.
Would you use this?
We build it if there’s real demand. If ~20 of you sign up, it ships. If not, we won’t. Either way you’ll hear an answer.
What is a VPAT, exactly?
The Voluntary Product Accessibility Template is a standardized document published by the Information Technology Industry Council (ITI). It describes how a software product conforms to specific accessibility standards. Current revision: VPAT 2.5.
It exists because procurement — especially US federal government procurement — needs a uniform way to compare vendor accessibility claims. Section 508 of the Rehabilitation Act requires federal agencies to consider accessibility when buying software. The VPAT is the standardized answer to “tell us what your product supports.”
For each WCAG criterion (and Section 508 / EN 301 549 criterion), a vendor declares one of:
- Supports — fully meets the criterion
- Partially Supports — some functionality meets it, but with caveats
- Does Not Support — doesn’t meet it
- Not Applicable — criterion doesn’t apply to this product
- Not Evaluated — couldn’t be evaluated
Plus a Remarks/Explanations column where the vendor describes the basis for the status. That column is where auto-generation can save the most time — a scan already knows which rules failed, on which elements, and against which WCAG criteria.