The problem this solves
Procurement teams often need conformance information, not marketing claims. A useful ACR states scope, standards, criteria, support level, remarks and known limitations clearly.
Who needs this
Vendors responding to procurement requests
Scope, evidence and recommendations are adapted to this context.
SaaS teams selling to government, education or enterprise buyers
Scope, evidence and recommendations are adapted to this context.
Product teams preparing a first ACR
Scope, evidence and recommendations are adapted to this context.
Teams updating an older report after product changes
Scope, evidence and recommendations are adapted to this context.
What we evaluate
Scope and product version
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Applicable standards and editions
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Criteria-by-criteria evaluation
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Remarks and explanations
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Review of conformance statements and limitations
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Technical examples
Distinguish support, partial support and non-support
Findings include evidence, impact, fix guidance and verification steps.
Tie remarks to test evidence, not assumptions
Findings include evidence, impact, fix guidance and verification steps.
Document exceptions and dependencies
Findings include evidence, impact, fix guidance and verification steps.
Avoid unsupported claims such as certification
Findings include evidence, impact, fix guidance and verification steps.
Methodology
Test
Define scope and evaluate representative workflows.
Find
Record barriers with reproducible evidence.
Explain
Connect issues to user impact and technical criteria.
Fix
Recommend source-level remediation.
Verify
Retest fixes and update status.
Deliverables
Testing plan aligned to the target standard
Prepared for product, design, engineering and QA conversations.
Evidence and issue notes for criteria
Prepared for product, design, engineering and QA conversations.
Draft or review support for ACR remarks
Prepared for product, design, engineering and QA conversations.
Disclaimer that the report is not a government certification
Prepared for product, design, engineering and QA conversations.
Related resources
Accessibility in procurement
How audits, VPAT templates and ACRs support technology procurement.
Section 508 vs. ADA Title II
Where procurement documentation and public-sector requirements differ.
FAQ
Is a VPAT a certification?
No. VPAT® is a registered template from ITI. The completed document is an ACR and it is not a certification.
Can you write the whole ACR?
We can support the technical evaluation and report preparation, but final publication decisions remain with the organization.
Which edition should we use?
That depends on procurement requirements and product market. We confirm the expected standard during scoping.
Audit, fix, verify.
Tell us about your website or application, the scope and your accessibility goals. We'll recommend an approach — audit only, or audit plus remediation — and send a written proposal.