Skip to main content :::
:::

What Are VPAT, ACR, and Accessibility Conformance Reports?

A VPAT is a template for producing an Accessibility Conformance Report, or ACR. ACRs are often used in procurement and vendor review; they are not the same as user accessibility reports, automatic certification, or whole-product guarantees.

Key Takeaways

  • VPAT is the template; ACR is the report created from that template.
  • An Accessibility Conformance Report is procurement documentation, not the same thing as a user-submitted accessibility report.
  • It is often used in B2B, government procurement, and vendor assessment.
  • It organizes evidence and limitations, but it does not replace testing, user feedback, or ongoing maintenance.

Separate VPAT from ACR

VPAT stands for Voluntary Product Accessibility Template. ACR stands for Accessibility Conformance Report, usually produced using the VPAT format.

In simple terms, VPAT is the template; ACR is the completed document for a specific product.

Where it is used

VPAT/ACR often appears in procurement, vendor review, enterprise customer requests, or government purchasing. Buyers want to understand conformance against WCAG, Section 508, EN 301 549, or other standards.

For product teams, it can organize test results, known limitations, and improvement plans into a document that others can review.

ACR is not the same as a user accessibility report

An Accessibility Conformance Report is conformance documentation used in procurement and vendor review. It usually describes support status, test scope, and limitations against specific standards.

A user accessibility report or accessibility issue report is a real-use clue about a barrier someone encountered, such as a form that cannot be completed with a keyboard, an unclear error message, or a PDF that is difficult to read. Both can support maintenance evidence, but they serve different purposes.

Do not treat it as automatic certification

VPAT/ACR is documentation, not automatic certification. Its quality depends on honest reporting, sufficient testing, clear scope, and specific limitations.

Without real testing, human judgment, and follow-up maintenance, producing a document alone will not make the product easier for end users to use.

How it relates to Accesserty

Accesserty does not treat VPAT/ACR as the current product center because it would pull the product toward procurement documentation and enterprise compliance workflows.

Conceptually, DevCheck, Pulse, Signal reports, and ALLY maintenance records can provide clues for understanding issues, organizing evidence, and improving over time. They do not automatically create a trustworthy ACR and should not be packaged as compliance guarantees. Accesserty does not currently provide a VPAT or ACR generator.

Frequently Asked Questions

Is VPAT/ACR a certification?

No. It is a documentation format and report describing product conformance status. It may support procurement decisions, but it is not automatic or official certification.

Does Accesserty generate VPAT/ACR?

Not currently. Accesserty focuses on making barriers visible, reportable, inspectable, and maintainable, not on producing formal procurement documents.

Related Pages

References