VPAT 2.5 Rev
A VPAT (Voluntary Product Accessibility Template) is the standard document that procurement teams request to verify product accessibility. This is the document that unblocks deals.
Deliverables
Engagements produce the accessibility compliance documents that procurement teams and regulators expect — in the standard VPAT format, reflecting findings as of the audit completion date.
Standard Deliverables
IncludedOpenACR Filing
Digital accessibility report format accepted by the GSA (General Services Administration) and other federal procurement systems. Required for many government contracts.
Accessibility Statement
Public disclosure following the W3C WAI model, formatted and ready for your site. Demonstrates good faith compliance and strengthens your legal position if accessibility is ever questioned.
Sample Audit Findings
Each finding includes plain-English impact and a recommended fix. These examples highlight issues that automated scanners typically miss.
Finding HAC-SAMPLE-0142Fix Included
Confirmation Dialog Close Button Has No Accessible Name
SC 4.1.2 — Name, Role, Value · Level A · WCAG 2.2 AA
Plain-English Impact
A keyboard-only user opens a confirmation dialog they cannot escape. The close button has no accessible name — screen reader users hear only “button” when focus lands on it. The practical consequence: users who rely on assistive technology cannot complete the workflow without mouse-based intervention.
Recommended Fix
- <button onClick={onClose}>
- <span className="icon icon-close" />
- </button>
+ <button type="button" onClick={onClose}
+ aria-label="Close dialog">
+ <span className="icon icon-close"
+ aria-hidden="true" />
+ </button>Finding HAC-SAMPLE-0217Fix Included
Data Visualization Has Generic Alt Text
SC 1.1.1 — Non-text Content · Level A · WCAG 2.2 AA
Plain-English Impact
A revenue chart in the dashboard uses generic alt text — technically present, so automated scanners report it as passing. A screen reader user hears only “chart” with no access to the data the visualization represents. The trends, values, and comparisons are locked in pixels. Automated tools check whether alt text exists; only a human can evaluate whether it communicates the same information.
Recommended Fix
- <img src="revenue-chart.png"
- alt="chart" />
+ <img src="revenue-chart.png"
+ alt="Monthly revenue: Jan $42K,
+ Feb $47K, Mar $51K — 21%
+ growth" />
+ <details>
+ <summary>View as data table</summary>
+ <!-- data table alternative -->
+ </details>Finding HAC-SAMPLE-0089Fix Included
Focus Not Managed After Form Submission
SC 2.4.3 — Focus Order · Level A · WCAG 2.2 AA
Plain-English Impact
When a user submits a search form, results appear below the form but keyboard focus stays on the submit button. A sighted user sees the results immediately. A screen reader user has no indication that content changed and must manually navigate the page to find what appeared. Automated tools detect the DOM update but cannot evaluate whether focus was moved appropriately.
Recommended Fix
const handleSearch = async () => {
const results = await fetchResults(query);
setResults(results);
- // focus stays on submit button
+ resultsRef.current?.focus();
};
- <div className="results">
+ <div className="results" ref={resultsRef}
+ tabIndex={-1} role="region"
+ aria-label="Search results">Available Add-Ons
OptionalRemediation Roadmap
Prioritized fix plan with effort estimates, broken down for your engineering team.
Fix Patches
Code patch files showing exactly what to change in your codebase to fix each finding — minimal, focused changes.
Jira/Tracker Backlog
CSV-ready issue backlog with pre-filled WCAG labels, components, and remediation checklists.
Engagements are priced per project, not per artifact. Reach out and we’ll scope the right combination together.
After Delivery
A VPAT is only useful if the right people can find it. These steps help you extract full value from your report.
- Share It With Procurement Teams
- Send it directly in response to RFPs, security questionnaires, or procurement checklists that include an accessibility line item.
- Publish It on Your Website
- Post the VPAT on your site’s accessibility page. Procurement teams routinely search for VPATs before reaching out.
- File It for Future RFPs
- Keep the report accessible to your sales and legal teams. RFP accessibility questions often arrive on short timelines.
- Pair It With an Accessibility Statement
- The VPAT provides the evidence behind a public accessibility commitment. Together, they give prospects both the promise and the proof.
- Understand the Shelf Life
- A VPAT reflects your product as of the evaluation date. Most organizations re-evaluate annually or after significant updates.
- Use It to Prioritize Remediation
- Treat the findings as a prioritized backlog — fix critical issues first, then work through moderate and minor items.
See a Sample of the Work
Browse a complete priority remediation plan from a real, anonymized audit — every finding, severity rating, and recommended fix. A sample of the full VPAT/ACR, our flagship deliverable, is available on request.