Procurement documentation
A buyer asked for an ACR. Know what it will take to deliver one.
Define the product scope, evaluate the experience and prepare evidence-backed Accessibility Conformance Report documentation. Bring the buyer’s request; we’ll clarify the evaluation, deliverables and schedule with you.
Important boundary: A VPAT is the reporting template; the completed accessibility conformance report describes the evaluation. This service is technical documentation, not legal advice, certification or a promise of buyer acceptance.
What we clarify before testing
The product is more than its homepage.
- Product and versionIdentify the experience, components and states that procurement is asking about.
- Criteria and editionConfirm the requested template, standard and any “not sure” questions.
- Evidence and handoffSeparate observed findings, limitations, open work and review responsibilities.
Start with a scope conversation
Bring the request. We’ll define the work.
A short scoping conversation with Virtually(Creative). Technical attendance is arranged when the agreed scope requires it. Share only the context needed to route the request; arrange secure product access after scope is agreed.
Define the report
Make the report defensible.
The report scope names the product version, criteria, coverage, evidence, limitations, review handoff and any optional remediation or retest. Quote and schedule follow those factors.
View the review format- 01
Agree what is evaluated
Product version, representative features, user journeys, environments and applicable criteria.
- 02
Document observed evidence
Findings include scope, reproduction context, user impact, limitations and the questions that remain open.
- 03
Hand off to the right reviewers
Virtually(Creative) coordinates the engagement. Virtually(Creative) performs manual review. Your organization owns final claims, approval and buyer response.
Before you send
Questions, answered plainly.
Does an ACR certify compliance?
No. An ACR documents the scope and results of an evaluation. It is not legal advice, a universal certification or a guarantee of procurement acceptance.
Can you review a product behind login?
Yes, when the access method and scope are agreed. Do not put credentials in this form; we arrange secure test access after scoping.
Do you also fix the findings?
Implementation support is separately scoped. We can discuss developer pairing, pull-request review or retesting when those capabilities fit the agreed work.
What will it cost?
Pricing reflects product coverage, report requirements, access and deliverables. We’ll explain those quote factors during scoping.