Most accessibility audits take between one and three weeks from start to delivery. The exact timeline depends on the size of the site or application, the number of pages included in the audit scope, and the availability of the team conducting the evaluation.
| Factor | What It Means |
|---|---|
| Typical duration | One to three weeks for most audits |
| Small sites (under 25 pages) | Often completed within five to seven business days |
| Large or complex properties | May require three weeks or longer depending on scope |
| Biggest variable | Page count and the number of unique interactive components |
What Determines the Accessibility Audit Timeline
Page count is the primary driver. An audit of 10 pages moves faster than one covering 50 or 100 pages. Each page requires individual evaluation using screen readers, keyboard interaction, visual inspection, and code review.
Unique components also matter. A site with repetitive page templates takes less time than one with dozens of distinct interactive patterns, embedded media, forms, and custom widgets. The evaluator spends more time on pages that behave differently from one another.
How the Evaluation Process Affects Duration
An accessibility audit is a thorough, human-led process. Evaluators use assistive technologies like NVDA, JAWS, and VoiceOver across browsers such as Chrome and Safari. They also conduct keyboard testing, visual inspection at 200% and 400% zoom, and code-level review.
Automated scans are sometimes used as one component of the review, but scans only flag approximately 25% of accessibility issues. The remaining evaluation requires direct human analysis, which accounts for most of the time involved.
How Scope Selection Shapes the Schedule
Not every page on a site needs to be audited. Accessibility professionals typically recommend selecting a representative sample: key landing pages, forms, navigation flows, and any page type that appears frequently. A well-chosen sample of 15 to 30 pages covers the most common patterns without auditing every URL.
Choosing the right sample upfront keeps the audit timeline predictable. Expanding scope mid-project is the most common reason audits take longer than expected.
Does the Conformance Level Change the Timeline
Audits targeting WCAG 2.1 AA or WCAG 2.2 AA take roughly the same amount of time for most web properties. The conformance level defines what criteria the evaluator checks against, but the evaluation process itself stays consistent.
Targeting AAA conformance would extend the timeline, though very few organizations pursue AAA for an entire site.
What Happens After the Audit
The audit identifies issues and documents them in a report with specific locations, descriptions, and remediation guidance. Report preparation adds one to three business days after the evaluation phase finishes. Some providers include a walkthrough session to review the findings with the development team.
For most organizations, the full cycle from kickoff to final report delivery fits within two to three weeks, with smaller projects finishing sooner.