Skip to the main content

8 min readPublished Last updated

How to Check a Website for AODA Compliance

Written by UXPro Design Studio. Kitchener, ON. Prepared with AI assistance and checked against the sources listed below.

How do I check whether my website meets AODA?

No automated checker can confirm that a website meets AODA: free scanners flag some WCAG 2.0 Level AA failures, and a person has to test the rest.

Key facts
Standard to test againstWCAG 2.0 Level AA, except live captions (1.2.4) and pre-recorded audio description (1.2.5)
Can a tool confirm compliance?No. W3C says evaluation tools can only assist; a person has to test the rest
Free screen readersNVDA on Windows; VoiceOver, built into macOS
UXPro AODA website pass$850 CAD per site, plus HST

Is there an AODA website checker that can confirm compliance?

No. Ontario's guidance does not name a checking tool, and the government says it does not endorse accessibility consultants. W3C's guide to selecting evaluation tools is direct: "Tools cannot check all accessibility aspects automatically. Human judgement is required." It also warns that tools "can produce false or misleading results".

Ontario's own guidance on making websites accessible points the same way. It suggests a final evaluation "using an automatic assessment to flag any issues that may not have been resolved", then a review with assistive technology such as a screen reader, and, where possible, testing by people with disabilities before launch.

What standard are you checking against?

WCAG 2.0 Level AA, minus live captions (1.2.4) and pre-recorded audio description (1.2.5). Ontario businesses with 50+ employees must meet it; see our AODA guide for who must comply, reporting and penalties.

WCAG 2.2 is newer and adds criteria (see WCAG 2.2 AA in our glossary). Meeting it helps your visitors, but the Ontario regulation names 2.0, so test against 2.0 AA for the AODA question. W3C's How to Meet WCAG quick reference has a version filter: set it to WCAG 2.0, levels A and AA.

Which pages should you test first?

Most sites are too large to test page by page, so test a sample chosen with care. W3C's evaluation method, WCAG-EM 2, builds the sample like this:

  • Common pages: home and main service pages, plus shared pages such as help, contact and legal information.
  • Every complete process, end to end: a booking, quote request or contact form, from the first field to the confirmation. WCAG 2.0 says that when a page is part of a process, every page in that process must conform.
  • One page of each type or template: a blog post, a location page, a team page.
  • A few pages picked at random. WCAG-EM adds a random sample equal to 10% of the structured sample.
  • Pages that explain accessibility features or offer help. We would add your accessibility notice, the page that tells visitors how to request an accessible format or give feedback.

How do you check a website for accessibility yourself, step by step?

Run each step on every page in your sample. The WCAG 2.0 success criterion number is in brackets so you can look each one up.

  1. Run a free automated scan. W3C keeps a list of evaluation tools. It includes the axe DevTools browser extension from Deque and Pope Tech, which is built on the WAVE engine. W3C does not endorse specific products, and neither do we. Fix what the scan reports, then treat a clean scan as the point where manual testing starts.
  2. Do a keyboard-only pass. Put the mouse aside and move through the page with Tab, Shift+Tab, Enter, Space and the arrow keys. Every link, button, menu and form control must be reachable and usable (2.1.1). You must never get stuck inside a widget such as a pop-up or an embedded map (2.1.2). The order should make sense against the layout (2.4.3), and you should always see where focus is (2.4.7).
  3. Spot-check with a screen reader. NVDA is free for Windows. VoiceOver is built into macOS and turns on with Command-F5, or, on a Mac with Touch ID, by holding Command and quickly pressing Touch ID three times. Listen for a page title that names the page (2.4.2), headings in order that match the visual structure (1.3.1), images described by their purpose (1.1.1), link text that makes sense in context rather than a row of "click here" (2.4.4), controls announced with a name and role (4.1.2), and the page read in the right language (3.1.1).
  4. Check colour contrast. Normal text needs a contrast ratio of at least 4.5:1 against its background, and large text at least 3:1 (1.4.3). Colour also cannot be the only way information is shown, such as a red border as the sole sign of an error (1.4.1). W3C's Easy Checks note that eyedropper contrast tools test one item at a time, so check text over images and buttons in their hover and focus states separately.
  5. Zoom to 200%. Use your browser's zoom. Text should resize to 200% without content or functions being lost (1.4.4). Reflow at narrow widths (1.4.10) is a WCAG 2.1 criterion, so it is outside the AODA mapping, but it is worth checking while you are there.
  6. Test your forms. Every field needs a label or instructions (3.3.2). Submit the form empty, then with a badly formed email address: the error should be identified and described in text, not only by colour (3.3.1). Repeat the form with the keyboard and the screen reader.
  7. Check your PDFs. A PDF linked from your site is web content. Open the ones visitors actually use, such as forms, menus and price lists, and check for tags, headings, a logical reading order, alt text on images, a set document language and a document title. W3C's PDF techniques for WCAG 2.0 cover each of these.
  8. Check video and audio. Pre-recorded video with sound needs captions (1.2.2); check that they exist and match what is said. Audio-only and video-only clips need a text alternative (1.2.1), and pre-recorded video needs either audio description or a full text alternative (1.2.3). Only live captions and the AA-level audio description are exempt.
  9. Write down what you found. For each issue, note the page, the criterion, what happened and the fix. Ontario's guidance suggests keeping a record of the accessibility issues you have resolved.

What do automated tools catch, and what needs a person?

WCAG-EM 2 states that "most accessibility checks are not fully automatable", even though tools "can significantly assist evaluators". The table shows roughly where the line falls. Treat it as a guide, not a measurement: tools differ, and none is complete.

Table · scrolls sideways

CheckWCAG 2.0 criterionCan a free tool flag it?What a person has to judge
Image alt text1.1.1 (A)Yes, when alt is missingWhether the alt text describes the image's purpose
Colour contrast1.4.3 (AA)Mostly, for plain text on solid backgroundsText on images or gradients; hover and focus states
Form labels3.3.2 (A)Yes, when a label is missingWhether labels and instructions make sense; error messages (3.3.1)
Page title and language2.4.2, 3.1.1 (A)A missing title or language attributeWhether the title describes the page
Keyboard access, no trap2.1.1, 2.1.2 (A)Not reliablyTabbing through every menu, pop-up and form
Focus order and visible focus2.4.3 (A), 2.4.7 (AA)PartlyWhether the order is logical and the focus ring is visible
Headings and structure1.3.1 (A)Skipped levels, empty headingsWhether headings match the visual structure
Link purpose2.4.4 (A)Empty linksWhether link text makes sense in context
Captions1.2.2 (A)NoWhether captions exist and are accurate
Text resize to 200%1.4.4 (AA)NoZooming in and looking
PDFsSeveral (PDF techniques)Partly; PDF checkers report missing tagsReading order and the quality of alt text

W3C's Easy Checks put the risk plainly: a page "could seem to pass these checks, yet still have significant accessibility barriers". An accessibility check is also narrower than a UX audit, which asks why visitors leave without getting in touch. The two answer different questions.

What should an accessibility audit quote include?

Audit quotes vary with the number of templates, forms, PDFs and videos tested. Check that each quote tests by hand against WCAG 2.0 AA, names the pages sampled, and includes a retest.

UXPro's AODA website pass is $850 CAD per site, plus HST, and covers up to 10 pages. Larger sites are quoted before any work starts.

How can UXPro help?

What the AODA website pass covers, and what you receive, is listed on the AODA website pass page.

If you want a lighter first look, request a free Redline: we redline one page of your site at phone width, up to ten notes, sent as a PDF.

What people ask next

The questions this guide gets asked after it has been read. Each answer is on the page, so the FAQ markup and the visible text are the same words.

No. Section 14 of O. Reg. 191/11 requires the website and its content to conform to WCAG 2.0 AA, and an overlay does not change the page underneath. Fix the code and the content.

The regulation does not set a retest interval for websites. Recheck before a launch or redesign, after adding a new form, template, batch of PDFs or video, and whenever someone reports a barrier. If you are a business or non-profit with 20 or more employees in Ontario, the compliance report you file every three years, next due 31 December 2026, is a sensible point to rerun the full sample.

Treat it as web content if visitors open it from your site. Check it for tags, headings, a logical reading order, alt text on images, a document language and a title, using W3C's PDF techniques for WCAG 2.0. A menu published as an accessible web page avoids the problem.

You can run the self-check in this guide yourself, and fixing what it finds is worth doing either way. A paid audit adds documented testing across every template and process, and a written issue list a developer can work from. UXPro's AODA website pass is $850 CAD per site, plus HST.

Next step

What to do with this.

Run the scan and the keyboard pass on your home page and your main form this week; neither needs anything you do not already have. For a second pair of eyes, request a free Redline. For a full test against WCAG 2.0 AA, see the AODA website pass. For the rules themselves, read our AODA website compliance guide.

Checked against the cited primary sources on 14 November 2026. General information, not legal advice.

What you get

We read your site by hand and reply with written findings.

No turnaround time is published yet. We would rather say nothing than publish a window we have not tested.

Written by

UXPro Design Studio

UXPro Design Studio · Kitchener, ON

Prepared with AI assistance and checked against the sources listed below.

Sources

For AI agents

Read as Markdown — the same guide as plain text, served as text/markdown. The feed for every published guide is at /blog/rss.xml.