ACR Turnaround Time

Most ACRs take two to six weeks from kickoff to delivery, depending on product size, VPAT edition, and team responsiveness during evaluation.

Most Accessibility Conformance Reports (ACRs) take two to six weeks from project kickoff to final delivery. The actual ACR turnaround time depends on the size of the product being evaluated, the edition of the Voluntary Product Accessibility Template (VPAT) being completed, and how quickly your team can provide access and answer questions during the process.

ACR Turnaround Time Overview
Key Point What It Means
Typical Timeline Two to six weeks from kickoff to final ACR delivery
Biggest Variable Product size and the number of pages or screens in scope
VPAT Edition WCAG edition is fastest; INT edition takes the longest due to broader criteria
Client Responsiveness Delays in providing access or answering questions extend the timeline

What Determines ACR Turnaround Time?

An ACR is the completed document produced from a VPAT template. Before the ACR can be written, an accessibility audit must be conducted against the product. The audit is the time-intensive portion of the process.

A small web application with 10 to 15 screens can often be audited within one to two weeks. A large enterprise platform with dozens of workflows and user roles may require three to four weeks of evaluation. The ACR document itself is typically produced within a few days after the audit wraps up.

How VPAT Editions Affect the Timeline

The VPAT comes in four editions: WCAG, Section 508, EN 301 549, and INT (International). Each edition maps to a different set of criteria.

The WCAG edition covers Web Content Accessibility Guidelines (WCAG) conformance only, making it the most focused and typically the fastest to complete. The Section 508 and EN 301 549 editions layer additional requirements from their respective regulatory frameworks. The INT edition combines all three, which means the evaluation covers the broadest set of criteria and takes the most time.

Common Causes of Delays

The most frequent cause of extended timelines is access. If the product requires login credentials, staging environments, or specific user accounts to evaluate, any lag in providing those adds directly to the calendar.

Products with complex authentication flows or role-based interfaces require coordination between the accessibility provider and your development team. When that coordination stalls, the audit pauses.

Rush Timelines and Their Cost

Some providers offer expedited ACR delivery for an additional fee. Rush timelines typically compress the schedule to one to two weeks for small to mid-sized products. Expect a premium of 25% to 50% on top of the standard cost.

For reference, ACR issuance generally costs between 300 dollars and 1,000 dollars, depending on the VPAT edition. That cost sits on top of the audit itself, which typically starts at 1,000 dollars and ranges to 3,000 dollars depending on scope.

What You Can Do to Speed Things Up

Prepare access credentials and staging environments before the project starts. Identify the specific screens, workflows, and user roles that should be in scope. Assign a point of contact who can respond to provider questions within 24 hours.

Organizations that have this preparation done before kickoff consistently see shorter turnaround times than those who figure it out after the audit begins.