ACR / VPAT report draft

The draft makes the conformance claim reviewable

An ACR or VPAT should explain the accessibility status of a real product, not make unsupported marketing claims. The report draft connects product scope, standards, test evidence, support levels, remarks, and known limitations in one reviewable document.

The goal is clarity. Procurement, legal, sales, product, and accessibility stakeholders should be able to understand what was evaluated, what supports the claim, and where follow-up work remains.

What the report draft includes

• Product scope: product name, version, platforms, included experiences, excluded areas, and any third-party dependencies.
• Evaluation methods: manual review, assistive technology checks, supplied evidence, remediation validation, and any automated support used as context.
• Standards coverage: WCAG 2.2 AA, Section 508, EN 301 549, or other standards relevant to the buyer or procurement path.
• Support levels: Supports, partially supports, does not support, not applicable, or equivalent template language used consistently across criteria.
• Evidence-backed remarks: concise notes that explain the support level, known exceptions, and any remediated or deferred items.

Evidence keeps the language defensible

Reliable documentation is based on evidence. The draft should draw from audit findings, retest notes, product scope, release context, assistive technology observations, and known exceptions.

When evidence is incomplete, the report should say so. Unsupported certainty creates risk for sales, procurement, and legal review because future buyers may ask how the claim was validated.

What you receive

• A structured ACR / VPAT report draft prepared for stakeholder review.
• Product scope and evaluation method notes written in procurement-friendly language.
• Support-level remarks connected to the available evidence.
• Known exceptions and open items separated from validated support claims.
• A foundation for the standards matrix and buyer review packet.