Step 1: Verify the VPAT Is Current
Check the product name, version number, and the date the VPAT was completed. A VPAT more than two years old — or one that doesn't specify the product version you are evaluating — should be treated as potentially outdated. Request a current VPAT that covers the specific version you are procuring.
Step 2: Confirm It Uses the VPAT 2.x Format
The VPAT 2.x format (introduced after the 2017 Section 508 refresh) covers WCAG 2.1 Level A and AA criteria. Older VPAT 1.x documents use the outdated 508 criteria. If a vendor provides a 1.x format, request an updated 2.x VPAT before evaluating.
Step 3: Identify the High-Impact Criteria
Not all WCAG criteria carry equal weight. The highest-impact criteria for most software products include:
- 1.1.1 Non-text Content (Level A) — Are images, charts, and non-text elements described for screen reader users?
- 1.4.3 Contrast (Minimum) (Level AA) — Is text readable for users with low vision?
- 2.1.1 Keyboard (Level A) — Is every function accessible without a mouse?
- 2.4.7 Focus Visible (Level AA) — Can keyboard users see where they are on the page?
- 4.1.2 Name, Role, Value (Level A) — Do interactive elements have accessible names and roles for screen readers?
Step 4: Read the Conformance Levels Critically
For each criterion, the vendor claims one of four conformance levels:
- Supports — The product fully meets the criterion.
- Partially Supports — The product meets the criterion in some cases but not all.
- Does Not Support — The product does not meet the criterion.
- Not Applicable — The criterion is not relevant to the product.
Any "Partially Supports" or "Does Not Support" on a high-impact criterion is a potential barrier for users with disabilities and warrants a follow-up question to the vendor.
Step 5: Hunt for Hedge Language
Pay close attention to the remarks column. Phrases like these signal that the vendor's conformance is incomplete:
- "with exceptions"
- "workaround available"
- "partially implemented"
- "planned for future release"
- "may not apply to all components"
These phrases often appear alongside a "Supports" conformance level — creating the appearance of full conformance while quietly acknowledging gaps. VPAT Score automatically flags hedge language across the entire document.
Step 6: Make the Call
Use the criterion-level breakdown to make your procurement decision. Gaps in low-impact criteria may be acceptable. Gaps in high-impact criteria — especially keyboard access, screen reader support, and focus visibility — may block access entirely for users with certain disabilities.
VPAT Score automates steps 3 through 6, producing an objective letter grade and risk rating in under a minute. You still own the decision — but you make it with better data.