Accessibility compliance management platforms can generate Voluntary Product Accessibility Templates (VPATs) and Accessibility Conformance Reports (ACRs) by pulling directly from audit data stored within the platform. Instead of building these documents from scratch in a spreadsheet or word processor, the platform pre-populates conformance findings, support levels, and remarks into the correct template format.
| Key Point | What It Means |
|---|---|
| VPAT vs ACR | A VPAT is the blank template. An ACR is the completed document that reports conformance findings for a specific product. |
| Data Source | Platforms pull from stored audit results to populate each WCAG criterion with a support level and explanatory remarks. |
| Editions | VPAT editions include WCAG, Section 508, EN 301 549, and INT. The WCAG edition is the most common for SaaS companies. |
| Updating | ACRs do not formally expire, but updating them after significant product changes keeps them accurate for procurement reviews. |
What Happens During VPAT ACR Generation on a Platform
The generation process starts with audit data. After an audit is conducted and results are logged in the platform, each WCAG success criterion has a recorded conformance level: Supports, Partially Supports, Does Not Support, or Not Applicable.
The platform maps these conformance levels into the standard VPAT table structure. Remarks and explanations that auditors entered for each criterion carry over into the corresponding cells. This eliminates the copy-and-paste workflow that makes traditional ACR creation slow and error-prone.
How Edition Selection Works
Platforms that support ACR generation typically allow selection of the appropriate VPAT edition before generating the document. The WCAG edition covers Web Content Accessibility Guidelines (WCAG) conformance and is the default for most web applications. Section 508 and EN 301 549 editions apply when products are sold to U.S. federal agencies or European public sector organizations, respectively.
The INT edition combines all three. Selecting the correct edition determines which criteria appear in the final document and how the conformance table is structured.
Where AI Fits Into the Process
Some platforms use AI to assist with ACR generation. AI can translate technical audit findings into clear, readable remarks for each criterion. It can also suggest conformance levels based on the severity and scope of identified issues.
AI does not replace the auditor’s judgment. The conformance determination for each criterion still requires human review. AI accelerates the drafting stage, particularly for the remarks column, where writing clear explanations for dozens of criteria is time-intensive.
What the Output Looks Like
The generated ACR follows the standard VPAT format recognized by procurement teams. It includes a product description section, evaluation methods used, the conformance table organized by WCAG level, and any notes about the evaluation scope.
Most platforms export the finished ACR as a PDF, HTML document, or both. Some allow direct sharing through a public URL, which is useful when vendors need to provide ACRs to multiple procurement reviewers without sending individual files.
Keeping ACRs Current
ACRs reflect the product’s conformance status at a specific point in time. When a product undergoes significant updates, the ACR should be regenerated to reflect the current state. Platforms make this easier by retaining the previous audit data alongside new results, so only the changed criteria need fresh review.
Regeneration through a platform takes a fraction of the time required to build a new ACR from a blank template. This is one of the primary reasons organizations use platforms for this workflow.
Leave a Reply