← Accessibility Insights & Resources

Is My Website AODA Compliant? How to Check

First find out whether the AODA website rule applies to you. Then spend an hour testing your own site, so you know roughly where you stand before anyone asks.

Run a free accessibility scan

Your website is AODA compliant if it conforms to WCAG 2.0 Level AA, apart from two criteria the regulation leaves out: live captions and pre-recorded audio description. That rule applies to Ontario's public sector and to businesses and non-profits with 50 or more employees in Ontario. There is no official AODA checker and no certificate. You find out by testing the site against WCAG.

You can get a useful first answer yourself in about an hour: run a free automated scan, then test one or two important pages with a keyboard, browser zoom and a screen reader. That won't prove your site is compliant, but it will show you quickly if it isn't.

This guide walks through both parts: whether the rule covers your organization, and how to run the self-check step by step. This is general information, not legal advice.

Step 1: Does the AODA website rule apply to you?

The website rule is section 14 of the Integrated Accessibility Standards Regulation (O. Reg. 191/11). Whether it applies depends on what kind of organization you are and how many employees you have in Ontario.

Who the AODA website rule applies to
OrganizationDoes the website rule apply?What it covers
Business or non-profit, 1 to 49 employees in OntarioNo No WCAG requirement. You still have to provide information in an accessible format when someone asks.
Business or non-profit, 50 or more employees in OntarioYesPublic websites and web content, at WCAG 2.0 Level AA with the two exceptions.
Designated public sector organization (municipalities, and the hospitals, school boards, colleges, universities and other bodies the regulation lists) Yes, at any sizePublic websites and web content, at WCAG 2.0 Level AA with the two exceptions.
Government of Ontario and the Legislative AssemblyYesPublic and internal websites, at WCAG 2.0 Level AA with no exceptions.

How to count employees

Ontario's accessibility rules for businesses and non-profits say to count full-time, part-time, seasonal and contract employees in Ontario. Don't count volunteers, independent contractors or employees outside Ontario. An organization with no employees in Ontario is exempt.

If you have fewer than 50 employees, the website rule doesn't apply to you, and you can stop here as far as section 14 goes. Your other duties are covered in our guide to AODA requirements for small business. The self-check below is still worth an hour: disability is a protected ground under the Ontario Human Rights Code whatever your size, and a site people can't use loses customers.

Which sites and content are covered

If the rule applies to you, section 14 sets its limits:

  • Public websites and web content, including web-based applications. Internal sites (intranets and extranets) are not covered for businesses, non-profits and the designated public sector.
  • Sites you control. That means directly, or through a contract that lets you modify the product. A site an agency built and hosts for you is still yours if your contract lets you have it changed.
  • Content published after January 1, 2012. Content published before that date is outside the rule.
  • Unless it is "not practicable". The regulation lets an organization consider things like whether commercial software or tools are available. This is a narrow exception, not a general excuse, and Ontario's guidance expects you to choose tools that support accessibility the next time you refresh the site.

The deadline for all of this was January 1, 2021. There is no upcoming date to wait for: if the rule applies, your public site is expected to conform now.

Step 2: Know what standard you're checking against

The AODA does not have its own website test. It points to the W3C's Web Content Accessibility Guidelines (WCAG) 2.0 at Level AA, which means meeting all the Level A and Level AA success criteria. The regulation removes two of them:

  • 1.2.4 Captions (Live), captions on live video and webcasts.
  • 1.2.5 Audio Description (Pre-recorded), a narration track describing what happens on screen in recorded video.

Everything else at Level A and AA applies. Ontario lists each criterion on its page about how to make websites accessible.

Many audits and tools, including our free scan, test against newer versions such as WCAG 2.1 or 2.2. That is fine. The newer versions contain every WCAG 2.0 criterion and add more, so a site that passes WCAG 2.2 AA also meets the AODA baseline. It does mean a report may list a few issues that go beyond what the AODA strictly requires.

Step 3: A self-check you can do in under an hour

Pick two or three pages that matter: your home page, a typical content page, and the most important thing a visitor does on your site, such as a contact form, booking or checkout. Don't try to cover the whole site. Problems in a template repeat on every page that uses it.

The steps below are in the order we'd do them. They overlap with the W3C's own Easy Checks, which are worth reading if you want more detail on any one of them.

The self-check at a glance
CheckWhat you needWhat it tells you
Automated scanA free scannerCode-level errors: missing alt text, low contrast, unlabelled fields
Keyboard passYour keyboardWhether someone who can't use a mouse can reach and operate everything
Zoom to 200%Your browserWhether enlarged text stays readable and usable
Content reviewYour eyes and the scan resultsWhether headings, alt text, contrast, forms and video hold up
Screen readerThe one built into your computer or phoneWhat a blind visitor actually hears
PDFsA PDF readerWhether your documents are readable text or just pictures of pages

1. Run a free automated scan

Start here because it's the fastest. Enter your address in our free accessibility scan and you get a report in about a minute, listing the issues a machine can detect and where they are. Typical findings are images with no alt text, text with too little contrast, form fields with no label, and buttons or links with no name.

Treat the result as a list of confirmed problems, not as a score. A long list tells you the site is not compliant. A short or empty list only tells you the machine-detectable errors are gone.

2. Put the mouse away and use the keyboard

This is the most revealing ten minutes of the whole check. Load a page, click in the address bar, then press Tab repeatedly and try to complete your main task without touching the mouse. Use Shift+Tab to go back, Enter to follow links and press buttons, Space for checkboxes, arrow keys inside menus and radio groups, and Escape to close pop-ups.

  • Can you always see which item has focus? If the highlight vanishes, that's a failure.
  • Can you reach every link, button, menu item and form field?
  • Does focus move in an order that makes sense, roughly top to bottom?
  • Can you open and close the menu, any pop-up and the cookie banner?
  • Do you ever get stuck somewhere you can't Tab out of?
  • Can you finish the form or checkout, including fixing an error?

Anything you can't do here, a keyboard user can't do at all. Our keyboard accessibility guide explains the common causes and fixes.

3. Zoom to 200%

WCAG 2.0 requires that text can be resized up to 200 percent without losing content or functionality. Press Ctrl and the plus key (Cmd and plus on a Mac) until your browser shows 200%, then read the page and use the menu and a form. Look for text that is cut off, overlaps other text, or disappears, and for buttons you can no longer reach.

4. Look at headings, alt text, contrast, forms and video

These are the areas where the scan gives you a head start but can't finish the job, because each one needs a judgment call.

  • Headings. Skim the page reading only the headings. Do they outline the content, with one main heading and sub-headings under it? Text that only looks like a heading because it's big and bold doesn't count.
  • Alt text. The scan tells you which images have none. For the ones that do, read it: does it say what the image is for? "IMG_4032" and "banner" pass a scanner and fail a person.
  • Contrast. WCAG 2.0 AA asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. The scan measures this for you. Pay attention to grey text, text over photos, and placeholder text in form fields.
  • Forms. Does every field have a visible label that stays put when you type? Submit the form empty. Are the errors described in words, next to the fields they belong to, and not only by turning a border red?
  • Video and audio. Recorded video with speech needs captions. Play one and check that captions exist and are accurate, not unedited automatic ones full of mistakes. Recorded video also needs either audio description or a full text alternative such as a descriptive transcript: the AODA drops the Level AA audio description criterion, but the Level A one that offers this choice still applies. Live captions are not required.

For what "good" looks like in each of these areas, use our AODA website compliance checklist. This article is about finding out where you stand; the checklist is the list of things to get right.

Start with the quick part

The free scan runs automatically and lists what it finds, so you can spend your hour on the checks only a person can do.

Run a free accessibility scan

5. Try a screen reader

You don't need to buy anything. VoiceOver is built into Macs and iPhones, Narrator is built into Windows, TalkBack comes with Android, and NVDA is a free screen reader for Windows. Turn one on, go to your home page, and listen.

  • Is the page title announced, and does it describe the page?
  • Do images, buttons and links have names that make sense when read aloud?
  • Do you hear "button" or "link" with nothing else? That control has no name.
  • When you move into a form field, do you hear what the field is for?
  • When an error appears or a menu opens, are you told?

You will be slow and it will feel awkward. That's normal for a first attempt, and you'll still notice the big problems. Our screen reader testing guide covers the basic commands.

6. Open your PDFs

Ontario's guidance defines web content as any information found on a web page or web application, so treat the PDFs you publish as part of the check. Open two or three that people really use: a form, a menu, a brochure, a report.

  • Try to select a sentence with your cursor. If you can't, the PDF is a scanned image, and a screen reader has nothing to read.
  • Does it have real headings and a title, or just large text?
  • If it's a form, can you fill it in on screen using only the keyboard?
  • Turn your screen reader on and see whether the content is read in a sensible order.

The simplest fix for many PDFs is not to have them: put the information on a normal web page instead.

What a self-check cannot tell you

A self-check can show that your site is not compliant. It cannot show that it is. Be clear about that difference before you rely on the result.

  • Automated tools only test what a machine can judge. The W3C says so directly in its guidance on selecting evaluation tools: "Tools cannot check all accessibility aspects automatically. Human judgement is required." A clean scan is not a pass.
  • Quick manual checks are not definitive either. The W3C describes its Easy Checks as "designed to be quick and easy, rather than definitive" and warns that a page "could seem to pass these checks, yet still have significant accessibility barriers."
  • You tested a few pages. WCAG conformance is claimed for full pages and for complete processes. A sample tells you about the templates you looked at, not the ones you didn't.
  • You are not a daily screen reader user. People who rely on assistive technology use it very differently from someone trying it for the first time, and they hit barriers a beginner won't notice.
  • Some criteria need experience to judge. Whether custom menus, date pickers and pop-ups expose the right information to assistive technology, or whether error handling is sufficient, is hard to decide without knowing the standard well.

That is the gap a manual audit fills. The difference between the two is explained in automated vs. manual accessibility testing.

What to do with your results

  1. Write down what you found. Page, problem, date. Ontario's guidance recommends keeping a record of the accessibility issues you resolve, because it helps if your organization is asked to show that its website meets WCAG 2.0 Level AA.
  2. Fix the blockers first. Anything that stops a person finishing a task comes before cosmetic issues: a form that can't be submitted by keyboard, a menu that can't be opened, a button with no name.
  3. Fix at the template. A missing label in the site-wide header or footer is one fix, not five hundred.
  4. Send the list to whoever builds your site. Ask them which items come from the theme or platform and which come from your own content. Content problems, such as alt text and heading structure, you can often fix yourself.
  5. Re-test. Run the scan and the keyboard pass again after the fixes.
  6. Decide whether you need a manual audit. If the rule applies to you and you'll be confirming compliance in a report, or the self-check turned up serious problems, get the key pages and journeys tested by a specialist. Our AODA website audit does that by hand, with a remediation roadmap and a re-test after your fixes; see our fixed packages for what each one covers.

Be wary of shortcuts at this stage. An accessibility widget or overlay added to the page does not change the code underneath, and the AODA has no certification scheme, so a badge or certificate from a vendor is not proof of compliance.

How this connects to your AODA compliance report

Businesses and non-profits with 20 or more employees file an accessibility compliance report every three years, and the current deadline is December 31, 2026. Designated public sector organizations file every two years.

The report asks you to confirm that you have met the accessibility requirements that apply to you. For an organization with 50 or more employees, that includes the website rule. With 20 to 49 employees you still file, but your report covers the customer service standards only.

The report is certified by a senior officer who has the legal authority to say it is complete and accurate. That person should not be guessing about the website. A self-check gives them a first reading; a documented audit and a record of fixes gives them something to stand on. If the honest answer is "not yet", our guide on how to file your AODA compliance report explains how to answer and what to say.

Frequently asked questions

Is there an official AODA compliance checker?

No. The Ontario government does not publish a website testing tool or issue compliance certificates. The legal test is conformance with WCAG 2.0 Level AA, with the two exceptions, and you establish that by testing: automated scans for a first look, then manual testing with a keyboard and assistive technology.

My free scan found no errors. Is my website AODA compliant?

Not necessarily. A scan checks only what software can detect in the code. It can't tell whether your alt text makes sense, whether a keyboard user can finish your checkout, or whether a screen reader announces your error messages. Do the keyboard and screen reader checks before you draw any conclusion.

We have fewer than 50 employees. Do we need to check our website?

The AODA website rule doesn't apply to businesses and non-profits with fewer than 50 employees in Ontario, so you are not required to meet WCAG. You do have to provide information in an accessible format when someone asks, and the Ontario Human Rights Code applies at any size. Checking your site is good practice, not a legal requirement under section 14.

Does my website have to meet WCAG 2.1 or 2.2 for the AODA?

No. The regulation names WCAG 2.0 Level AA. Testing against WCAG 2.1 or 2.2 is common and covers the 2.0 criteria as well, so it does no harm, but the extra criteria in the newer versions are not AODA requirements.

Our website was built by an agency. Are we still responsible?

Yes, if you control the site. Section 14 applies to websites an organization controls directly or through a contractual relationship that allows the product to be modified. Send your developer the results of your check and ask how and when each item will be fixed.

How often should we repeat the check?

The regulation doesn't set a schedule. A sensible habit is to repeat the scan and the keyboard pass after any redesign, new template or new feature, and before you file a compliance report, because websites change and new content brings new barriers.