WCAG Without the Headache

Every accessibility law worth naming, including AODAAccessibility for Ontarians with Disabilities Act in Ontario, the ADAAmericans with Disabilities Act, which has no company size exemption in the US, and the European standards, eventually points at the same rulebook. It's called WCAGWeb Content Accessibility Guidelines, the technical standard the AODA points at, the Web Content Accessibility Guidelines, published by the W3C. If you understand WCAG, you understand what the law is really asking for. So let's cut through it.

The four principles: POUR

WCAGWeb Content Accessibility Guidelines, the technical standard the AODA points at is organized under four ideas. Content should be:

• Perceivable, meaning people can perceive the information, with text alternatives for images, captions for video, and enough contrast.
• Operable, meaning people can operate the interface, with keyboard access, enough time, and no seizure inducing flashing.
• Understandable, meaning content and controls behave in predictable, readable ways.
• Robust, meaning it works with assistive technology like screen readers, and keeps working as tech changes.

Under those four principles sit specific, testable success criteria. Each one is a concrete pass or fail check, and that's what an audit actually measures against. In WCAGWeb Content Accessibility Guidelines, the technical standard the AODA points at 2.0, the version Ontario's regulation names, there are 38 of them across Levels A and AA. That is the whole list, and it's a smaller number than most people brace for.

The three levels: A, AA, AAA

Every success criterion is graded by level.

• Level A is the floor. Fail these and the site is broken for whole groups of people. Think images with no text alternative, or content you can't reach by keyboard.
• Level AA is the real world target. This is what laws point to. It covers the issues that matter to a broad range of users, such as colour contrast minimums, resizable text, clear labels, and consistent navigation.
• Level AAA is the gold standard. It's excellent to aim for in places, but not expected across a whole site, and sometimes impossible to fully meet. No serious law demands blanket AAA.

Each level includes the ones below it. Meeting AA means you've also met A.

So which do you need?

For AODAAccessibility for Ontarians with Disabilities Act, and honestly for almost any compliance conversation, the answer is Level AA. That's the bar written into Ontario's regulation against WCAGWeb Content Accessibility Guidelines, the technical standard the AODA points at 2.0, and it's the bar the rest of the world has largely settled on. When someone says we need to be accessible, what they operationally mean is we need to pass WCAG at Level AA.

It's worth being precise about who that regulation catches, because this is where the sales emails get loose. Ontario's web standard applies to public sector organizations and to businesses and non profits with 50 or more employees in the province. If you have fewer than 50 employees, the web standard is not pointed at you, whatever anyone tells you.

What is pointed at you, at any size, is the Ontario Human Rights CodeOntario's human rights law, which applies at any size and has no employee threshold. It has no employee threshold, and it gives a person who couldn't use your site a real route to the Human Rights Tribunal that the AODAAccessibility for Ontarians with Disabilities Act doesn't. So the target stays the same, Level AA, but the reason it matters is different depending on how big you are. Under 50 people, the honest reason isn't a provincial filing regime. It's a customer who was shut out and has somewhere to take that.

A note on version numbers

WCAGWeb Content Accessibility Guidelines, the technical standard the AODA points at has editions: 2.0, 2.1, and 2.2. Ontario's regulation was written against 2.0 Level AA, so that's the strict legal reference. But the newer versions are additive. Versions 2.1 and 2.2 mostly add criteria for mobile and cognitive accessibility on top of 2.0. Building to the current version, 2.2 AA, means you comfortably clear the 2.0 bar the law names, and you're ready for wherever the standard goes next. There's rarely a good reason to aim at the older number on purpose.

In counts, Levels A and AA together come to 38 criteria in 2.0, 50 in 2.1, and 55 in 2.2. If you see 56 quoted for 2.2, it's out of date. Success criterion 4.1.1 Parsing was removed when 2.2 was published, and a lot of the checklists floating around online never caught up.

When we audit a site, every issue we flag is tied to a specific success criterion and level. So you're never told this feels wrong. You're told exactly which check failed and what it takes to pass it. We're not lawyers and this isn't legal advice about your own obligations. It's what the standard says and what the regulation names. For the rest, a lawyer is the right call.