Government vendors · VPAT
A VPAT that held up when the buyer checked.
A software company that sells case management tools to state and county agencies needed a VPAT for a contract renewal. Its old one said “Supports” on nearly every line. We tested the product by hand and wrote a VPAT the buyer could rely on.
- Client
- A software vendor
- Type
- VPAT
- Scope
- 12 key tasks, WCAG 2.2 AA and Section 508
- Result
- A VPAT 2.5 the buyer accepted
Context and goals
Caseworkers use the product all day to open cases, write notes, upload files, and schedule visits. Some of them use screen readers, magnification, or voice control.
The buyer’s accessibility office had started checking VPATs against the product. The vendor wanted a report that matched what a tester would find.
What success looks like
- Every remark in the VPAT describes what really happens when a person uses the product.
- Every gap has a plain description and a planned fix.
- The buyer can see the methods, the standards, and the version that was tested.
What we measured
We tested 12 key tasks by hand with a keyboard, a screen reader, and zoom, against all 55 WCAG 2.2 Level A and AA criteria and the Section 508 chapters that apply to software.
How the 55 criteria were rated
- Supports38
- Partially Supports12
- Does Not Support2
- Not Applicable3
The old VPAT had claimed Supports for 52 of the 55.
| Criterion | Rating | Remark |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | Most icon buttons have names. The attach, print, and filter buttons do not. |
| 2.1.1 Keyboard | Partially Supports | Every task works by keyboard except choosing a time on the scheduling calendar. |
| 1.4.10 Reflow | Partially Supports | Text on the notes screen is cut off at 200% zoom. |
| 3.3.1 Error Identification | Supports | Errors are named in text and announced to screen readers. |
| 2.4.7 Focus Visible | Supports | A clear focus outline appears on every control. |
What we found
- The good news: the core case screens worked well with a keyboard.
- The old VPAT claimed full support for 52 of the 55 criteria. Our testing supported 38.
- The scheduling calendar could not be used with a screen reader.
- Several icon buttons had no names, so a screen reader announced only “button.”
- Text was cut off at 200% zoom on the notes screen.
The path to good
- We wrote the VPAT in the ITI VPAT 2.5 format, with Supports, Partially Supports, and Does Not Support used the way buyers expect.
- Every criterion has a plain remark, and every gap has a planned fix and timing.
- We gave the developers the issue list in the order that would raise the most ratings soonest.
Follow-up
The buyer accepted the VPAT with the contract renewal. When the vendor fixed the calendar and the button names, we retested and updated the report.
All case studies are samples. Each is based on our past work or on our audits of publicly available websites, documents, and social media. Names and details have been changed to protect privacy.
Before you buy
We start with a free light audit.
We prepare it for you and send you what we find.
- We check your homepageKeyboard, screen reader, contrast, and zoom.
- We review one public documentTags, headings, image descriptions, and language.
- We fix one public document freeYou get it back fixed, with a before and after.
- We send you what we findA short written summary you can share with your team.