How Long Does an Accessibility Audit Take?
The stages of a WCAG audit, what makes each one longer or shorter, why fixing usually takes more time than testing, and what to do when your deadline is close.
See the AODA website auditHow long an accessibility audit takes depends on how much distinct work there is to test, not on how many pages your website has. As a guide from our own published delivery times: a manual audit of one key user journey takes about a week, a full audit of up to 15 templates about two weeks, and the same audit with an Accessibility Conformance Report (ACR) about three.
That is the time to get the report. It is not the time to get an accessible website. After the report, your team has to fix what was found and the auditor has to re-test it, and that part is usually the longest. If you are working back from a deadline, plan for the whole thing, not just the testing.
This guide walks through each stage of the WCAG audit timeline, what speeds it up or slows it down, and how to prepare. We don't quote industry-average durations, because there is no reliable source for them and vendors mean different things by "audit". Where we give numbers, they are our own published delivery times.
The stages of an accessibility audit
Most manual audits follow the shape of the W3C's WCAG Evaluation Methodology (WCAG-EM): define the scope, explore the site, select a representative sample, evaluate it, and report the findings. Around that sit the parts that involve your team: the walkthrough, the fixes and the re-test. Our guide to what a website accessibility audit is covers what happens inside each step. Here we look at them by time.
| Stage | Who does it | What decides how long it takes |
|---|---|---|
| 1. Scoping | You and the auditor | How quickly you can name your templates and journeys, and approve the quote |
| 2. Testing | The auditor | Templates, journeys, custom components, platforms, and access to the site |
| 3. Reporting | The auditor | The number of findings, and whether an ACR is needed |
| 4. Walkthrough | You and the auditor | Getting the right people on one call |
| 5. Remediation | Your team | The findings, your developers' time, your release process and any third parties |
| 6. Re-test | The auditor | When your fixes are live, and how many findings need checking |
1. Scoping
Scoping fixes what will be tested: the templates, the user journeys, the standard and level, the browsers and assistive technologies, and any extras such as documents or a sign-in area. It is short when you arrive with a list, and slow when the list has to be worked out over several emails or needs sign-off from several people.
Don't rush it to save a day. A vague scope is the most common reason an audit runs over, because the auditor finds a booking flow or a customer portal nobody mentioned.
2. Testing
This is the core of the audit: an automated pass, then testing by hand with a keyboard, with screen readers, zoomed in, and with contrast tools. It is skilled manual work, so its length follows the amount of distinct interface there is to get through. This is the stage the factors in the next section affect most.
3. Reporting
Each barrier is written up with its location, the WCAG success criterion it fails, its severity, who it affects and how to fix it. A site with many findings takes longer to write up than a site with few. Good auditors report a shared-component problem once, against the component, which keeps both the report and the writing time shorter. See how to read an accessibility audit report for what the result looks like.
4. Walkthrough
A call where the auditor takes your team through the findings and answers questions. The call itself is short. What takes time is finding a slot that suits your developers, so book it when you book the audit.
5. Remediation
Your designers and developers fix the findings. The auditor isn't in control of this stage, and it is usually the longest. More on that below.
6. Re-test
Once the fixes are live, the auditor checks each finding again and updates the report. It is quicker than the first round because the auditor is checking known issues, not exploring. It can only start when your fixes are deployed somewhere the auditor can reach.
What makes an audit take longer or shorter
The W3C's methodology lists the things that change how big a sample an evaluation needs, including the size, complexity and consistency of the site, and notes that web applications typically require more time and effort to evaluate. In practice it comes down to the following.
Unique templates
A template is one distinct layout or screen: your home page, a product page, the checkout, a sign-up dialog. Pages built on the same template share the same code and the same barriers, so 2,000 product pages on one layout take about as long to test as one. A small site where every page has a custom layout can take longer than a large, consistent one.
User journeys
WCAG's conformance requirements say that when a page is part of a process, every page in the process has to conform. So booking, buying, applying and signing in are tested from start to finish, including error messages and alternate paths. A long form with conditional questions takes much more time than a contact form.
Custom components
Static content is quick to test. Date pickers, mega menus, carousels, drag-and-drop, live search, maps and dashboards are not. Each has several states, and each state needs keyboard and screen reader testing.
Documents
PDFs, Word files and forms are tested and fixed differently from web pages, and are usually scoped separately. A site with a large document library can need more document work than web testing. Archiving documents nobody uses is the fastest way to shrink this.
An ACR or VPAT
If a buyer has asked for an Accessibility Conformance Report, the auditor has to write a conformance level and a remark for every criterion on top of the findings report. That adds writing and review time, and more again for each extra edition (WCAG, Section 508, EN 301 549). Our article on what a VPAT and an ACR are explains the document.
Access to staging and logins
This is a common delay, and the easiest to avoid. Testing can't start, or stops partway, when the staging site is behind a firewall, the test account can't reach the admin area, a one-time passcode goes to someone's phone, or there are no test payment details for the checkout. Every one of these is a day lost waiting for a reply.
Site changes mid-audit
If a release goes out while the audit is under way, findings already recorded may no longer match the site, and pages already tested may have new problems. The auditor then has to re-check work that was finished. Agree a testing window and hold releases to the templates in scope until it closes.
Slow answers
Auditors ask questions: is this behaviour intended, which of these two flows do customers really use, who owns this embedded widget? One named contact who replies the same day keeps the audit moving.
How long our own audits take
These are the delivery times we publish for our three fixed packages. Larger sites and products get a delivery date with the quote.
| Package | What is tested | Delivery |
|---|---|---|
| AODA Check | One key user journey, such as booking or checkout, across up to 5 pages | 5 business days |
| Compliance Audit | Up to 15 templates and 3 key user journeys | 10 business days |
| Procurement Pack | Everything in the Compliance Audit, plus an ACR | 15 business days |
Every package includes a call to walk through the findings and one re-test of the reported findings, within 90 days of delivery. That window is the time your team has to make fixes and still have them checked as part of the same audit. What each package covers is set out with our fixed packages.
Need a result before your AODA report is due?
Our AODA Check tests your most important user journey by hand, with a remediation roadmap, a call to walk through it, and one re-test after your fixes.
See what the AODA Check includesRemediation: usually the long part
An auditor can tell you when the report will arrive. Nobody can tell you in advance how long the fixes will take, because that depends on what the audit finds and on your own team. It usually takes longer than the audit itself, for a few reasons.
- It competes with other work. The audit is the auditor's full-time job for those days. The fixes go into your developers' backlog next to features and bugs.
- Some fixes are design decisions. A brand colour that fails contrast, or a custom control that has to be rebuilt, needs agreement before anyone writes code.
- Some fixes aren't yours to make. Booking widgets, payment forms, chat tools and themes belong to a vendor. You have to ask, wait, or replace them.
- Content needs people, not code. Writing alt text, captioning videos and fixing documents is steady manual work, often spread across several content owners.
- Releases have their own schedule. A fix isn't done until it is tested and deployed, and many teams release on a fixed cycle.
The good news is that the order matters more than the total. Critical barriers in shared components, such as the header, the navigation and form fields, tend to account for a large share of the findings, and fixing a component once fixes it on every page that uses it. Start there. Our guide to building an accessibility remediation plan covers how to sequence the rest.
A clear report shortens this stage more than anything else. If each finding names the component, the failing criterion and a fix specific to your code, your developers can start the same day. If the report is a list of rule names from a scanner, they first have to work out what each one means.
How to prepare so the audit goes faster
Most delays are avoidable, and most of the preparation is on your side.
- List your templates and journeys before you ask for a quote. Walk the site and note each distinct layout, not each page, and the tasks a customer must be able to finish.
- Set up access before day one. A stable link, test accounts for each role, test payment details, and a way around any one-time passcode. Try the test account yourself first.
- Clear the automated issues first. Run a free automated accessibility scan and fix what it finds, so the audit doesn't spend time documenting things a tool could have told you.
- Freeze the templates in scope. Hold releases that touch them until testing is finished.
- Name one contact. Ideally a developer who knows the front-end code and can answer questions quickly.
- Decide on documents and the ACR up front. Adding either one after testing has started means going back over ground already covered.
- Book the developer time now. Reserve time for fixes straight after the report is due, and put the walkthrough call in the calendar when you book the audit.
What to do when a deadline is close
Deadlines come from two places: a buyer who wants an ACR or audit report with a bid, and a regulator. In Ontario, businesses and non-profits with 20 or more employees must file their next accessibility compliance report by December 31, 2026. If time is short, these steps help.
- Start with the fixes in mind, not the report. Work backwards: the date, minus time for a re-test, minus time for your team to fix, is when you need the findings.
- Narrow the scope instead of thinning the testing. A proper manual test of the one journey customers must be able to complete is worth more than a quick look at everything. It also finds the problems in shared components that affect the rest of the site.
- Ask about rush delivery early. Some auditors can deliver faster. Ask for the date to be confirmed before you commit.
- Ask for critical findings as they are found. Your developers can start on the worst barriers before the full report is written.
- Fix in priority order. Barriers that stop someone completing a task come first. Minor issues can follow in a documented plan.
- Don't reach for an overlay. A widget added in an afternoon doesn't change your code or produce evidence of conformance. We explain why in accessibility overlays and compliance.
- Be accurate about where you stand. If a report or a buyer asks whether you meet the standard, answer from what has been tested and fixed, and keep a dated plan for what is left. Our guide to filing an AODA compliance report covers the filing itself.
Be wary of anyone promising a full manual audit of a complex site in a day or two. That usually means the manual part is thin. And no auditor can promise you will be compliant by a date, because the fixes are in your hands. This is general information, not legal advice.
Frequently asked questions
How long does a WCAG audit take?
It depends on the number of unique templates and user journeys, how interactive the site is, and whether documents or an ACR are included. Our own packages are delivered in one to three weeks, depending on scope. Ask any auditor for a delivery date tied to a named scope.
Does a bigger website take longer to audit?
Not necessarily. Audits are scoped by distinct templates and journeys, not page counts. A large site built on a few consistent templates can be quicker to audit than a small site where every page is a one-off.
Can an accessibility audit be done in a day?
An automated scan can be done in minutes, and it is a useful first step. A manual audit with keyboard and screen reader testing through real journeys takes days, because a person has to do it. If a quote promises both speed and full manual coverage of a complex site, ask exactly what will be tested by hand.
How long does it take to fix the issues an audit finds?
It depends on how many findings there are, how many come from shared components, and how much time your team can give it. It usually takes longer than the audit. Fixing critical barriers in shared components first gets the biggest improvement soonest.
How long does the re-test take?
Less than the original testing, because the auditor is re-checking known findings. The wait is usually for the fixes to be deployed. Check how long after delivery the re-test stays included; ours is within 90 days.
Does an ACR or VPAT add time to the audit?
Yes. The ACR is written from the audit findings and needs a conformance level and a remark for every criterion. If a buyer will ask for one, say so at scoping so it is planned into the delivery date.