Most accessibility audits take 2 to 4 weeks from kickoff to final report. Smaller informational websites can wrap in about 10 business days. Larger web apps, software platforms, or projects with many templates can run 4 to 6 weeks or longer. The biggest factors are scope (how many pages or screens), complexity (static content vs. interactive components), the standard being evaluated (WCAG 2.1 AA or WCAG 2.2 AA), and the auditor’s current capacity. A WCAG audit is a fully manual review, so timing reflects careful evaluation by a trained auditor, not automated scanning.
| Project Type | Typical Turnaround |
|---|---|
| Small informational website | 1 to 2 weeks |
| Mid-size website (10 to 25 templates) | 2 to 4 weeks |
| Web app or SaaS product | 3 to 6 weeks |
| Mobile app (iOS or Android) | 2 to 4 weeks per platform |
| Large enterprise or multi-product scope | 6 weeks or more |
What determines how long an accessibility audit takes?
Scope is the single biggest factor. An auditor evaluates a defined set of pages, screens, templates, or user flows, and each one requires its own careful review against WCAG criteria.
Complexity matters nearly as much. A static marketing page moves quickly. A multi-step checkout, a data-heavy dashboard, or a custom form with conditional logic takes substantially longer because each interactive state has to be evaluated.
The standard also plays a role. WCAG 2.1 AA and WCAG 2.2 AA are close in practice, but the auditor still maps each requirement to real content and components. Section 508 and EN 301 549 reference WCAG but add documentation steps that can extend timing.
Typical timeline for a website audit
For a standard business website with a dozen or so unique templates, expect about 2 to 3 weeks from the date the auditor begins evaluation to the delivery of the final report.
That window usually breaks down into a few phases. Scoping and kickoff can take 2 to 5 business days. The evaluation itself runs 1 to 3 weeks depending on page count. Report writing and quality review typically adds 3 to 5 business days.
Auditor capacity affects the start date more than the audit duration. Reputable providers often have a queue, so the clock starts when your project reaches the front of the line.
How long does a web app or SaaS audit take?
Web apps run longer than informational sites because the auditor has to evaluate authenticated flows, component states, error handling, and dynamic content updates. A typical SaaS audit lands in the 3 to 6 week range.
If the product has multiple user roles (admin, member, guest) each role’s view may need its own evaluation. That expands scope and time accordingly. VPAT and ACR projects follow the audit and add their own timeline for documentation.
Mobile app audits
Mobile app audits cover a single platform at a time. An iOS app audit and an Android app audit are separate efforts, each running 2 to 4 weeks depending on screen count and feature depth.
Native components, gestures, and screen reader behavior (VoiceOver on iOS, TalkBack on Android) each need direct evaluation on real devices. Auditors do not rely on emulators for accurate results.
Can the audit be faster?
Rush timelines exist but they come with tradeoffs. Some providers can compress a small website audit into a week if their schedule allows and the scope is tight. Quality stays the same only when the auditor has the bandwidth, not when corners get cut.
The fastest way to shorten a real timeline is to narrow scope. Audit the highest-traffic templates first, then expand in a second phase. This approach gets actionable results into developers’ hands sooner while the remaining scope moves through a follow-up evaluation.
What happens after the audit is delivered?
The audit identifies issues and provides clear remediation guidance. Fixing those issues is a separate phase handled by your development team or a remediation service, and that timeline depends entirely on issue volume and developer capacity.
Validation (a re-check of fixes) typically happens after remediation is complete. That adds another 1 to 2 weeks for most projects, depending on how many items need to be re-evaluated.
FAQs
How quickly can I book an accessibility audit?
Booking depends on the provider’s queue. Some auditors can start within a few days; others have a 2 to 4 week lead time. The audit itself begins on the scheduled kickoff date, not the date you sign the agreement.
Does a WCAG 2.2 AA audit take longer than WCAG 2.1 AA?
Not meaningfully. The two versions are closely related and the evaluation workflow is essentially the same. A skilled auditor covers either standard without materially changing the timeline.
Can an automated scan replace the audit to save time?
No. Scans flag approximately 25% of issues and cannot determine WCAG conformance. A (manual) audit by a trained auditor is the only way to evaluate a digital asset against WCAG criteria. Scans are a monitoring tool, not an audit substitute.
How often should an audit be repeated?
Most teams re-audit annually or after significant product changes. Between audits, ongoing monitoring and internal review help catch new issues introduced during development.
Accessibility audit timing is predictable when scope is defined clearly upfront. The more precisely you define what needs to be evaluated, the more accurately a provider can quote both price and turnaround.
Find a qualified auditor for your project in the Accessibility Base directory.