VPATs and Accessibility Conformance Reports

The plain-language idea

A VPAT (Voluntary Product Accessibility Template) is a standardized document format a vendor fills out to describe how well their product conforms to specific accessibility standards — typically WCAG and Section 508 — criterion by criterion. It's not a general accessibility statement; it's a structured template with a row for each success criterion, where the vendor states whether the product supports it, partially supports it, or doesn't, often with a short remarks column.

VPATs are used heavily in B2B and especially government procurement. A purchasing organization — a government agency, a large enterprise with its own compliance requirements — needs to evaluate a vendor's accessibility before buying or adopting a product, and a VPAT is frequently a required part of that procurement process itself, not an optional nice-to-have a vendor volunteers.

Once a vendor fills out a VPAT for a specific product and version, the completed document is often called an ACR (Accessibility Conformance Report) — the same template, filled in with a real product's real conformance status, rather than the blank form.

See it in a real thing: a VPAT row for keyboard access

A VPAT typically lists WCAG success criteria one by one, each with a conformance level column. A row for keyboard accessibility (WCAG 2.1.1, part of the Operable principle covered in this track's foundational WCAG lesson) might read something like:

Criterion: 2.1.1 Keyboard (Level A)
Conformance Level: Partially Supports
Remarks: Core navigation and forms are fully keyboard-operable.
The custom date-range picker on the reporting dashboard is not
currently keyboard-operable; a fix is scheduled for the next release.

That's the real, practical implication for a frontend team: this row is written from the engineering team's actual, honest conformance status — not from what the sales team hopes is true. If the company sells into enterprise or government customers, a frontend engineer may genuinely be asked to help verify or produce content for a VPAT, which means real WCAG conformance work becomes a document customers read and make purchasing decisions from, not just an internal quality metric nobody outside the team ever sees.

What people usually miss

Watch out

• A VPAT is a template; an ACR is the filled-out version for a specific product. People often use the two terms interchangeably in casual conversation, but the distinction (blank form vs. completed report) is worth knowing precisely.
• "Voluntary" in the name doesn't mean optional in practice. Many government and large-enterprise procurement processes effectively require a VPAT/ACR as a condition of purchase, even though no single law mandates every vendor produce one.
• Honest partial conformance is the expected, normal outcome — not a failure. Almost no real product achieves perfect conformance across every criterion. A VPAT's standard vocabulary for partial support exists precisely because gaps are the norm, not the exception.
• A VPAT is read by real people making a purchasing decision, often including someone specifically evaluating accessibility risk. Treating it as boilerplate paperwork misses that it functions as a trust document between engineering's real work and a customer's real evaluation.

Why this matters in interviews

"Have you worked on a product that needed to document its accessibility conformance for customers?" tests whether a candidate has seen accessibility work connect to a real business process (procurement) beyond the product itself — naming VPATs/ACRs and the honesty expectation around them is a strong, concrete signal.