How Often Should You Audit Your Website for Accessibility?
There is no fixed interval in the rules. What should decide the timing is how much your site has changed, and what you do in the months between audits.
Run a free scan of your websiteAudit your website for accessibility when it changes in a way that matters: after a redesign, when you add new templates or a new checkout or booking flow, when you switch platform or theme, or when someone reports a barrier. Ontario's AODA does not set an audit interval, and neither does the W3C. As a working default, many organizations do a manual audit about once a year and lighter checks in between.
That yearly figure is a habit, not a rule. A site that hasn't changed since its last audit doesn't become less accessible because twelve months have passed. A site that shipped a new checkout last week has untested code today, whatever the calendar says.
This guide covers what the rules actually require, the events that should trigger a new audit, what to do between audits, and how monitoring differs from an audit.
Does any rule say how often to audit?
Not in Ontario. The AODA website requirement tells you which standard to meet and who has to meet it. Ontario's guidance on how to make websites accessible says public websites and web content posted after January 1, 2012 must meet WCAG 2.0 Level AA, except live captions and pre-recorded audio description, if you are a designated public sector organization or a business or non-profit with 50 or more employees. It gives tips for testing, but no schedule for how often to test.
The requirement is ongoing. Your site has to meet the standard on the day a customer uses it, not only on the day it was audited. That is why change, not the calendar, is the better trigger.
The three-year report is a reporting cycle, not an audit interval
The number people often mix up with an audit schedule is the AODA compliance report. Ontario's page on completing your accessibility compliance report says businesses and non-profits with 20 or more employees must file one every three years, and designated public sector organizations every two years. The current deadline for businesses and non-profits is December 31, 2026.
The report is a declaration. A senior officer confirms that the organization has met its current accessibility requirements. It doesn't require you to commission an audit, and it doesn't say your website only has to be right every third year. In practice, though, it is hard to confirm that a website meets WCAG 2.0 Level AA without having tested it, so many organizations time an audit ahead of the filing. Our guide on how to file your AODA compliance report walks through the filing itself.
One wording trap: the same Ontario page says the ministry verifies compliance by "auditing and inspecting businesses and organizations". That is the government checking on you. It is not an instruction to audit your own site on a set schedule. This is general information, not legal advice.
What the W3C says
WCAG is a standard to measure against, not a testing calendar. The W3C's guidance on sustaining accessibility says that changing content can introduce accessibility issues, and asks for regular reviews as your content changes, with accessibility checks built into your publishing process. It doesn't name an interval. Its evaluation overview says to evaluate early and throughout development, not once at the end.
Events that should trigger a new audit
Templates share code, so a barrier in one template shows up on every page built from it. Any change that adds or rewrites templates, components or user journeys creates code nobody has tested yet. These are the changes to watch for.
A redesign or rebuild
A redesign replaces most of what the last audit tested: colours, type, navigation, components. The old report no longer describes your site. Audit the designs or a staging build before launch if you can. A contrast problem is a quick change in a design file and a slow one once it's live on every page.
New templates
A new landing page layout, a new product page, a new event listing. Each one is a distinct layout that wasn't in the last audit's scope. You don't need to repeat the whole audit. Test the new templates.
A platform or theme change
Moving to a new content management system or store platform, or swapping the theme on the one you have, changes the underlying markup across the site even if it looks much the same. Menus, forms, headings and focus styles all come from the theme. Treat it like a redesign.
A new checkout, booking or application flow
These are the journeys customers must be able to finish, and they are where barriers cost the most. A new or reworked flow needs keyboard and screen reader testing from start to finish, including the error messages.
A new third-party widget
Chat, booking calendars, cookie banners, maps, review carousels, embedded payment forms. You didn't write the code, but it sits on your page and your visitors have to get past it. Ontario's guidance puts the duty on the organization that controls the website, whether directly or through a contractual relationship. Test a widget before you add it, and again after the vendor ships a major update.
An ACR that is out of date
If you sell software and give buyers an Accessibility Conformance Report, it describes the product as it was when it was tested. The Information Technology Industry Council, which publishes the VPAT template, says in its VPAT guidance to review or update an ACR when the product changes in ways that could affect accessibility, or when the relevant standards or requirements change. An ACR can only be as current as the testing behind it, so an update usually means re-testing what changed. See what a VPAT and an ACR are for the background.
A complaint or a request for help
If a customer tells you they couldn't complete something, test that journey now. Fix the barrier they hit, then look for the same pattern elsewhere on the site. One report usually means others ran into it and left without saying anything.
Trigger and response at a glance
| Trigger | What to do |
|---|---|
| Redesign or rebuild | Full manual audit, ideally on designs or staging before launch |
| Platform or theme change | Full manual audit of the templates and key journeys |
| New templates | Manual test of the new templates only |
| New checkout, booking or application flow | Manual test of the whole journey with a keyboard and a screen reader |
| New third-party widget | Test the widget before it goes live, and after major vendor updates |
| ACR out of date | Re-test what changed in the product, then update the ACR |
| Complaint or request for help | Test that journey right away, fix it, and check for the same pattern elsewhere |
| AODA compliance report coming up | Check the site is tested and fixes are confirmed before the report is signed |
| New pages on existing templates | No audit. Content author checks and an automated scan |
| Nothing has changed | Automated scans, plus a periodic manual check of your key journeys |
Notice how few rows call for a full audit. Most changes need a focused test of what's new, which takes less time and costs less. If you're unsure what a full audit covers, read what a website accessibility audit is.
Changed your checkout or booking flow?
Our AODA Check tests one key user journey by hand, with a keyboard and screen readers, and includes a remediation roadmap and one re-test after your fixes.
See what the AODA Check includesWhat to do between audits
An audit is a snapshot. Most new barriers arrive afterwards, in small pieces: an image uploaded without alt text, a promotional banner with pale text, a form field added without a label. Four habits catch most of them.
Run automated scans
Automated tools are quick and repeatable, which makes them good at spotting regressions in things code can detect, such as missing alt attributes, unlabelled fields and low contrast. Run one after each release, or on a regular schedule your team will keep to. You can start with our free automated scan.
Know the limit. The W3C says plainly that no tool alone can determine whether a site meets accessibility standards, and that knowledgeable human evaluation is required. A clean scan means the tool found nothing, not that the page works. Our article on automated vs. manual accessibility testing explains what each one finds.
Test new features as they're built
Before a new component ships, have someone use it with only a keyboard: Tab through it, open it, close it, submit it, trigger an error. Then try it with a screen reader. Ten minutes at this stage finds problems that take far longer to fix after launch. Add it to your definition of done so it doesn't depend on someone remembering.
Give content authors a short checklist
Every page, image and document someone publishes is a chance to add a barrier, and publishing happens far more often than releases do. A short list covers the common ones:
- Every meaningful image has alt text that says what it shows.
- Headings are real headings, in order, not bold text.
- Link text makes sense on its own, not "click here".
- Videos have captions.
- PDFs and Word files are tagged and readable before they're uploaded.
- Text isn't baked into images.
Our WCAG 2.2 AA accessibility checklist is a fuller version you can adapt.
Re-test your fixes
A fix isn't done until someone has checked it with the same method that found the problem. It is common for a fix to solve the reported issue and break something next to it, such as a focus style that now shows but a focus order that changed. Keep a record of what was fixed and when. Ontario's guidance recommends exactly this, noting that the record helps if your organization is asked to show that your website meets WCAG 2.0 Level AA. Our guide to an accessibility remediation plan covers how to track the work.
Accessibility monitoring vs. an audit
The two are often sold as if they were interchangeable. They answer different questions.
| Aspect | Audit | Monitoring |
|---|---|---|
| Question it answers | Does this site meet the standard, and what has to be fixed? | Has anything got worse since last time? |
| Method | Mostly manual: keyboard, screen readers, zoom and contrast, checked against each success criterion | Mostly automated re-scans of the same pages, sometimes with a manual spot check |
| When | At a point in time, after significant change | Repeated at regular intervals |
| What you get | A findings report with the criterion failed, the location and the fix | A shorter report on what's new or changed |
| What it can't do | Tell you about changes made after the testing ended | Show that the site meets WCAG, because automated checks can't judge everything |
Monitoring is only useful with a baseline. If you monitor a site that was never audited, you are watching for new problems while the old ones, including everything a scanner can't see, stay where they are. Audit first, fix, re-test, then monitor.
And monitoring doesn't replace the next audit. When one of the triggers above happens, a re-scan of the old pages won't tell you whether the new checkout works with a screen reader.
How our monitoring works
Every CodexMotive audit package includes a few months of monitoring after delivery. We re-scan a set of your pages each month and send you a report, with any new critical issue at the top. It is a monthly report, not a live alerting system. A second plan adds a manual test of one key journey and a check-in call every quarter, and a yearly ACR update to match the fixes we've re-tested. Details are on our pricing page.
A simple schedule you can adopt
If you want something to put in a calendar, this is a reasonable starting point. It is our suggestion from audit work, not a legal requirement. Adjust it to how often your site changes.
- Every time content is published: the content author checklist above.
- Every release: an automated scan, and a keyboard test of anything new.
- Regularly, for example monthly: an automated re-scan of your main templates, so regressions are found while they are still small.
- About once a year, if the site changes steadily: a manual check of your key journeys with a keyboard and a screen reader.
- On any trigger in the table: the response listed beside it.
- Before your AODA compliance report: confirm the testing is current and the fixes have been re-tested.
A small brochure site that changes twice a year needs much less than an online store that ships weekly. Match the effort to the rate of change.
Frequently asked questions
How often should you do an accessibility audit?
After any redesign, platform or theme change, and whenever you add new templates or a new checkout or booking flow. If the site changes steadily, many organizations also do a manual audit about once a year. There is no interval set by the AODA or by the W3C.
Does the AODA require an annual website audit?
No. Ontario's guidance sets the standard your public website must meet, WCAG 2.0 Level AA with two exceptions, but no testing schedule. Organizations with 20 or more employees file a compliance report every three years, which is a reporting duty and not an audit interval.
Is the three-year AODA compliance report the same as an audit?
No. The report is a declaration, filed online, confirming that your organization has met its current accessibility requirements. An audit is the testing that tells you whether your website actually does. Many organizations audit before they file so they can sign with confidence.
What is the difference between accessibility monitoring and an audit?
An audit is a thorough, mostly manual test of your site against a standard at a point in time. Monitoring repeats lighter, mostly automated checks at regular intervals to spot new problems. Monitoring works best after an audit, and doesn't replace one.
Can automated scans replace regular audits?
No. Scans are good at catching regressions that can be detected in code, but the W3C notes that no tool alone can determine whether a site meets accessibility standards. Whether a checkout can be completed with a keyboard or a screen reader has to be tested by a person.
Do I need a full audit every time I add a page?
No. A new page built on an existing, already tested template needs content checks, such as alt text, headings and link text, and an automated scan. A new template or a new interactive feature needs a manual test of that part only.