Website Accessibility Audit and AODA Compliance

An accessibility audit tells you whether people with disabilities can actually use your website, and what to change if they can't. You get a clear list of issues measured against WCAG 2.1 or 2.2 Level AA, the standard Canadian accessibility rules point to, along with the fixes, done properly, if you want them.

This is for Ontario organizations with obligations under the AODA, public sector and federally regulated organizations, businesses that have received a complaint or a demand letter, and anyone who wants their site to work for every customer.

What the audit covers

Automated scanning

Every page type is scanned with automated tools to catch the issues machines detect reliably: missing alternative text, low colour contrast, empty links, missing form labels and broken heading structure. A website accessibility checker is a useful starting point, and you can run the free website check yourself, but automated tools can only test part of WCAG.

Manual review

The rest needs a person. I work through each WCAG success criterion on your key templates: whether alternative text actually describes the image, whether link text makes sense out of context, whether error messages explain what went wrong, whether content still works when zoomed or reflowed on a small screen, and whether anything relies on colour alone.

Keyboard and screen reader testing

I go through your main tasks, such as navigating the menu, filling in a form, booking or checking out, using only a keyboard and then with screen readers such as NVDA on Windows and VoiceOver on Mac and iPhone. This is where the problems that block real users usually show up: focus that disappears, menus that trap you, buttons a screen reader can't name.

What you get back

• A written report listing every issue, the WCAG criterion it fails, where it occurs and how severe it is.
• Specific fix instructions your developer can follow, or that I can carry out.
• A priority order, so the problems blocking real users get fixed first.
• A summary for managers and boards explaining where the site stands.

Remediation

Most issues are fixed in the theme or templates, which means one change fixes a problem across hundreds of pages. Content issues, such as missing alternative text, unclear links and inaccessible PDFs, are fixed page by page or handed to your team with guidance. After remediation I retest everything and update the report so you have a record of what was done.

Accessibility statement

An accessibility statement tells visitors which standard you aim to meet, any known limitations, and how to request information in another format or report a problem. I'll write one that's accurate for your site and set up a feedback process that reaches a real person.

AODA compliance support

Under Ontario's accessibility law, public sector organizations and private and non-profit organizations with 50 or more employees in Ontario must make their public websites meet WCAG 2.0 Level AA, with a couple of exceptions. Auditing to WCAG 2.1 or 2.2 AA covers that requirement and prepares you for where standards are heading. For the full rules, deadlines and reporting obligations, read the AODA website requirements guide. I can help you document your website work for your compliance records.

Ontario isn't the only jurisdiction with rules. Federally regulated organizations such as banks, telecoms and transportation companies have obligations under the Accessible Canada Act, and several provinces, including Manitoba, Nova Scotia and British Columbia, have passed their own accessibility laws. An audit to WCAG AA is the common starting point for all of them.

Why overlays and widgets do not make you compliant

Accessibility overlays are scripts that add a toolbar or claim to fix your site automatically. They don't repair the underlying code, they can interfere with the assistive technology disabled visitors already use, and they don't make a site meet WCAG. Organizations using them still receive complaints and legal demands. Real compliance means fixing the site itself. If you have an overlay installed, I'll usually recommend removing it once the actual fixes are in.

How it works

1. Scoping call. We agree on which pages, templates and tasks to test, and which standard to measure against.
2. Audit. Automated scanning, manual review, keyboard and screen reader testing.
3. Report and walkthrough. You get the written findings and a call to go through them and agree priorities.
4. Remediation. I fix the issues, or support your developer while they do.
5. Retest and statement. Every fix is verified, the report updated and your accessibility statement published.
6. Ongoing monitoring. New pages and content are checked each month so the site stays accessible.

Accessibility drifts as content changes. The website maintenance plans include monthly accessibility checks on Business and Priority. If a full rebuild makes more sense than fixing an old site, a website redesign builds accessibility in from the start.