A mini web accessibility audit takes one to two weeks, and a full web accessibility audit takes three to five weeks. Timelines are ranges and begin from the signed agreement date.
Remediation is the open-ended part, because it depends on how much we find and how quickly your team can act.
What slows things down
- Waiting on the page sample to be approved.
- Third-party components you don't control, which need vendor conversations.
- Design decisions that need input from more than one team.
The audit
- Reviewing and confirming the pages in scope takes a few days. We propose the sample, you confirm it.
- Auditing and reporting take most of the time above.
- The walk-through happens once you've had time to read the findings, so we can demonstrate anything that isn't clear on paper.
If usability testing with people with disabilities is part of the project, allow three to four weeks for that work. We confirm at scoping whether it can run alongside the audit. Current timelines sit beside each service on our web services page.
The remediation
We'd be guessing if we gave you a firm number before the audit. In our experience, one to two months is common for a team working through a full audit's findings, with a wide range between projects. Some run a focused sprint and remediate the highest-impact findings in a few weeks. Others work down the list alongside their normal release cycle over several months. Both are fine.
If your developers need extra support to remediate findings, we're happy to provide guidance as they work through them.
Every finding in the spreadsheet carries an impact level for this reason. You don't have to do it all at once, and you shouldn't try. Remediate the barriers that block people first, then work down the list.
Retesting
Once updates are made, we recommend retesting the findings to confirm which barriers were remediated correctly and flag anything still outstanding. That takes one to three weeks.