Accessibility Conformance Report (ACR)
The filled-out accessibility report, often made from a VPAT, that tells buyers which standards a specific product version meets.
What it is
An Accessibility Conformance Report records how a specific product performs against accessibility requirements such as WCAG, Section 508, or EN 301 549. Teams commonly produce one by completing the Information Technology Industry Council's VPAT template. The VPAT is the blank template; the filled, dated document about your product is the ACR.
Reach for an ACR when government or enterprise procurement asks for evidence before buying. Each criterion gets a conformance level, an explanation, and enough test detail for a buyer to understand what was checked. Name the product version, platforms, assistive technologies, methods, standards, and evaluation date.
Gotcha: it is a disclosure, not a certification badge. An automated scan cannot test keyboard flows, focus order, screen-reader announcements, or whether instructions make sense. 'Supports' without evidence invites a buyer to find the contradiction, so report partial support and known failures honestly with remediation plans.
Ask AI for it
Produce an Accessibility Conformance Report for the product below using the ITI VPAT WCAG edition and WCAG 2.2 Level AA. Test representative flows with axe-core, keyboard-only navigation, NVDA with Firefox, and VoiceOver with Safari. For every success criterion, choose Supports, Partially Supports, Does Not Support, or Not Applicable and add concrete findings, affected screens, reproduction steps, and evidence. State the product version, platforms, test dates, methods, evaluator, and scope. List every known gap with severity, owner, Jira issue, target release, and workaround, and do not infer conformance from automated scan results alone.