Section 508 and VPAT: a practical primer

Federal agencies and many contractors must demonstrate accessibility conformance as part of IT procurement and program oversight. Section 508 of the Rehabilitation Act, as refreshed by the Revised 508 Standards, incorporates WCAG 2.0 Level AA for web content; many programs today also align to WCAG 2.1 AA to match Title II and industry practice. This article is orientation, not legal guidance — your 508 office and contracting officer set the bar for your acquisition.

What buyers actually ask for

Solicitations often request a VPAT® (Voluntary Product Accessibility Template) or an ACR (Accessibility Conformance Report) summarizing how a product meets applicable criteria. Those documents are only as credible as the evidence behind them: scope of testing, known defects, and honesty about what automated scans can and cannot see.

WCAG, 508, and scanning tools

Automated engines such as axe-core are excellent at machine-detectable failures — missing names, contrast math, broken ARIA patterns, and similar. They do not, by themselves, prove full WCAG conformance. A defensible program pairs scheduled crawling with manual review on high-risk templates and user journeys, then ties remediation to retesting.

Reading a VPAT row honestly

• Supports should mean you tested that scenario and believe it holds for the configurations claimed.
• Partially supports is a valid and healthy answer when gaps exist but a documented workaround is available.
• Does not support with a dated remediation plan beats silent drift that surfaces in production later.

How Parity supports the evidence trail

Parity focuses on continuous WCAG scanning, durable fix surfaces so teams remediate at the right granularity, and exports (including VPAT-style matrices where configured) with org-defined disclaimers. It is an operational layer — not a replacement for your 508 office, manual test pass, or procurement legal review.