VPAT vs. ACR: The Nutrition Label for Accessibility
An ACR is a standardized report card for a product's accessibility, based on a template called a VPAT. It's a nutrition label stating conformance facts, not a pass/fail grade.
WHY IT EXISTS: To create a standardized way for technology vendors to report on the accessibility of their products. Before the VPAT, procurement departments, especially in government, had no consistent way to compare the accessibility of competing products, making it difficult to comply with laws like the US's Section 508.
THE MENTAL MODEL: An ACR is a nutrition label for product accessibility. It doesn't give a simple pass/fail grade. Instead, it provides a detailed, line-by-line statement of how a product conforms to specific accessibility standards. The VPAT (Voluntary Product Accessibility Template) is the blank form, and the ACR (Accessibility Conformance Report) is the completed report.
HOW IT WORKS: The Information Technology Industry Council (ITI) publishes the VPAT template. A vendor audits their own product against the criteria in the template, which map to standards like WCAG or Section 508. For each criterion, the vendor marks whether the product 'Supports', 'Partially Supports', 'Does Not Support', or is 'Not Applicable'. They add remarks to explain their ratings. This filled-out document is their ACR, which they publish for customers.
WHEN TO USE IT: As a vendor, you create an ACR to sell to government agencies and large enterprises that require accessibility documentation. As a buyer, you request ACRs from vendors to perform due diligence and compare products' accessibility features. It is a critical document for legal and procurement teams.
WHEN NOT TO USE IT: Do not treat an ACR as a third-party certification or a guarantee of perfect accessibility. It is a self-reported document, so its accuracy and detail can vary. It's a starting point for a conversation, not the final word. Always consider it alongside user testing and independent audits if accessibility is critical.
ONE CANONICAL EXAMPLE: A US federal agency needs a new collaboration tool. To comply with Section 508, their procurement office requests ACRs from three vendors. Vendor A's ACR shows full support for all criteria. Vendor B's shows partial support for keyboard navigation but includes a roadmap for a fix. Vendor C cannot provide an ACR. The agency can immediately see the relative risk and compliance of each vendor and use the reports to make an informed purchasing decision.
Read the original → itic.org
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.