A typical website accessibility audit takes between one and three weeks from start to delivery. The exact timeline depends on the size of the site, the complexity of its pages, and the auditor’s current workload. Smaller informational websites with 10 to 15 pages can often be evaluated in under a week. Larger web apps or ecommerce sites with dynamic content, forms, and authenticated states take longer.
That range covers the evaluation itself plus report preparation. The calendar time from signing a contract to receiving your audit report may stretch further if there is a queue.
| Factor | Impact on Timeline |
|---|---|
| Site size (page count) | More pages require more evaluation time; 10 pages vs. 50 pages can double or triple the schedule |
| Page complexity | Interactive elements, forms, modals, and authenticated flows add hours per page |
| WCAG standard version | WCAG 2.2 AA includes additional criteria compared to WCAG 2.1 AA, adding modest time |
| Auditor availability | Queue times vary by provider; some have two to four week lead times before work begins |
| Report detail level | Comprehensive reports with screenshots and remediation guidance take longer to prepare |
What Determines the Length of an Accessibility Audit?
Page count is the most obvious variable. An auditor evaluating a 10-page marketing site against WCAG 2.1 AA will finish faster than one working through a 40-page ecommerce store with product filters, checkout flows, and account dashboards.
But page count alone does not tell the full story. A single page with three interactive components takes less time to evaluate than a single page with a multi-step form, a data table, a video player, and a modal dialog. Complexity per page matters as much as the number of pages.
The WCAG conformance standard also plays a role. Most audits target WCAG 2.1 AA or WCAG 2.2 AA. The 2.2 version includes additional success criteria, which adds evaluation time, though the difference is usually measured in hours rather than days.
How Does the Audit Process Break Down?
An accessibility audit is not a single activity. It is a sequence of steps, each with its own time cost.
First, the auditor defines scope. This means identifying which pages and states will be evaluated, which environments (desktop, mobile, or both), and which WCAG standard applies. Scoping typically takes a day or less.
Next comes the evaluation phase. The auditor works through each page and each WCAG success criterion, checking how content behaves with assistive technology, keyboard navigation, and visual inspection. This is the longest phase. For a mid-sized website, expect five to ten business days of active evaluation work.
After evaluation, the auditor compiles the report. A quality audit report documents every issue identified, maps each one to a specific WCAG criterion, includes screenshots or code references, and provides remediation guidance. Report preparation can add one to three days depending on the volume of issues and the level of detail.
Why Do Some Providers Quote Longer Timelines?
Two reasons: queue time and thoroughness.
Popular accessibility companies and independent consultants often have a backlog. You may sign a contract today and not have an auditor begin work for two to four weeks. This is lead time, not audit time, but it affects your project calendar.
Thoroughness is the other factor. Some providers deliver a spreadsheet with issue descriptions. Others deliver a detailed report with annotated screenshots, severity ratings, and prioritized remediation steps. The second version takes longer to produce. It is also far more useful when your development team begins fixing issues.
Can Automated Scans Speed Up the Process?
Automated scans and audits are completely separate activities. A scan can complete in minutes, but scans only flag approximately 25% of issues. They cannot evaluate whether alt text is meaningful, whether a form error message is clear, or whether a custom component is operable by keyboard alone.
Scans are useful for catching surface-level code issues before an audit begins, which can reduce some of the auditor’s workload. But they do not replace the evaluation itself. A manual accessibility audit is the only way to determine WCAG conformance.
What Can You Do to Shorten the Timeline?
Three things help.
First, define your scope clearly before contacting an auditor. Know how many pages or screens need evaluation, whether you need desktop and mobile coverage, and which WCAG version your procurement or compliance requirements specify. This eliminates back-and-forth during the scoping phase.
Second, provide the auditor with access to any authenticated areas, staging environments, or content management systems they will need. Delays in access are one of the most common reasons audits take longer than expected.
Third, choose a provider whose current queue matches your project timeline. Ask about lead time upfront. Some providers can begin within days. Others are booked weeks out.
Does Site Type Affect Audit Duration?
Yes. A static informational website with consistent page templates is faster to evaluate than a dynamic web app or SaaS product. Ecommerce sites with product pages, search filters, and checkout processes fall somewhere in between.
WordPress sites and Shopify stores often share common templates, which means the auditor can evaluate one instance of a template and apply findings across similar pages. This reduces total evaluation time compared to a site where every page has a unique layout.
Mobile app audits tend to take longer than website audits because the auditor must evaluate interactions across multiple screen readers (VoiceOver on iOS, TalkBack on Android) and account for gesture-based navigation.
| Site Type | Typical Page Count | Estimated Duration |
|---|---|---|
| Informational website | 5 to 15 pages | 3 to 7 business days |
| Ecommerce store | 15 to 30 pages | 7 to 14 business days |
| Web application | 20 to 50 screens | 10 to 20 business days |
| Mobile app | 15 to 40 screens | 10 to 20 business days |
These estimates cover active evaluation and report preparation. Add lead time based on your provider’s availability.
Does the audit cost change with duration?
Audit pricing is typically based on the number of pages or screens and their complexity, not the number of days the auditor spends. A 20-page audit priced at a set rate takes the same investment whether the auditor completes it in eight days or twelve. However, rush timelines may carry a premium with some providers.
Should you choose a faster provider or a more thorough one?
Thoroughness should take priority over speed. A quick audit with a thin report creates more work downstream because developers will lack the context needed to fix issues correctly. A detailed audit report saves time during remediation and reduces the chance of repeated evaluation cycles.
How often should a website be re-evaluated after the initial audit?
Re-evaluation is recommended after significant design changes, major content updates, or platform migrations. For sites with frequent content changes, an annual audit is a reasonable cadence. Organizations under ADA compliance requirements or Section 508 obligations may need more frequent evaluation to maintain conformance.
Audit timelines are predictable once you understand the variables. Define scope early, prepare access credentials, and choose an auditor whose thoroughness and availability match your project needs.
Contact an accessibility auditor through the AccessibilityBase directory to get a timeline estimate for your project.