WCAG 2.0 vs 2.1 vs 2.2: What Changed and Which One the AODA Requires
How the three versions differ, which one each law points to, and which one to build and test against today.
Open the WCAG 2.2 AA checklistWCAG 2.0, 2.1 and 2.2 are the same standard at three points in time. Each version keeps the earlier success criteria and adds new ones: WCAG 2.1 added 17 and WCAG 2.2 added 9. Ontario's AODA requires WCAG 2.0 Level AA. Because the versions are backward compatible, a site that meets WCAG 2.2 Level AA also meets 2.1 and 2.0, so 2.2 AA is the sensible target for most organizations.
The rest of this article gives the dates and numbers, lists what each version added at Level A and AA, and sets out which version the main laws and standards refer to. For what the individual WCAG 2.2 criteria ask of your site, see our guide to WCAG 2.2 success criteria.
The three versions at a glance
WCAG is published by the World Wide Web Consortium (W3C). Every success criterion has a level: A, AA or AAA. To conform at Level AA you have to meet every Level A and every Level AA criterion, which is why the last column below is the number that matters to most organizations. Our article on WCAG levels A, AA and AAA explains the levels themselves.
| Version | Published | Level A | Level AA | Level AAA | Total | Needed for AA conformance (A + AA) |
|---|---|---|---|---|---|---|
| WCAG 2.0 | December 11, 2008 | 25 | 13 | 23 | 61 | 38 |
| WCAG 2.1 | June 5, 2018 | 30 | 20 | 28 | 78 | 50 |
| WCAG 2.2 | October 5, 2023 | 31 | 24 | 31 | 86 | 55 |
The dates come from the W3C's WCAG 2 overview. The counts come from the criteria listed in each published version: WCAG 2.0, WCAG 2.1 and WCAG 2.2.
The Level A count only rises by one between 2.1 and 2.2, even though 2.2 added two Level A criteria. That's because WCAG 2.2 also removed one: 4.1.1 Parsing.
Are the versions backward compatible?
Yes. The W3C states that content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and WCAG 2.0. Later versions add criteria. They don't reword or drop the existing ones, with a single exception.
That exception is 4.1.1 Parsing, which asked for markup without certain coding errors, such as duplicate IDs. The W3C says it is no longer needed for accessibility, and marked the criterion obsolete and removed it from WCAG 2.2. It still appears in WCAG 2.0 and 2.1, but the W3C has added a note to both saying it should be considered always satisfied for content written in HTML or XML.
In practice this means you don't have to choose between the AODA's version and the current one. Meet the newer version and you have met the older ones.
What WCAG 2.1 added
WCAG 2.0 was written in 2008, before most people browsed on a phone. The W3C says the 17 criteria added in WCAG 2.1 address three areas: mobile accessibility, people with low vision, and people with cognitive and learning disabilities.
Of the 17, five are Level A, seven are Level AA and five are Level AAA. The 12 at Level A and AA are the ones a typical audit covers:
| Success criterion | Level | What it asks for, in short |
|---|---|---|
| 1.3.4 Orientation | AA | Content works in both portrait and landscape |
| 1.3.5 Identify Input Purpose | AA | Fields that collect personal details say what they are in code, so browsers can autofill them |
| 1.4.10 Reflow | AA | Content fits a narrow screen or a zoomed-in view without scrolling in two directions |
| 1.4.11 Non-text Contrast | AA | Buttons, form field borders, icons and meaningful graphics have enough contrast |
| 1.4.12 Text Spacing | AA | Nothing is cut off or overlaps when a user increases line, word and letter spacing |
| 1.4.13 Content on Hover or Focus | AA | Tooltips and pop-ups can be dismissed, hovered over and don't vanish too soon |
| 2.1.4 Character Key Shortcuts | A | Single-key shortcuts can be turned off or changed |
| 2.5.1 Pointer Gestures | A | Swipes, pinches and other complex gestures have a simple one-finger alternative |
| 2.5.2 Pointer Cancellation | A | An accidental tap or click can be cancelled before it takes effect |
| 2.5.3 Label in Name | A | The name assistive technology uses for a control includes its visible label |
| 2.5.4 Motion Actuation | A | Anything triggered by shaking or tilting a device also works with an ordinary control |
| 4.1.3 Status Messages | AA | Messages such as "added to cart" are announced by screen readers without moving focus |
The five Level AAA additions were 1.3.6 Identify Purpose, 2.2.6 Timeouts, 2.3.3 Animation from Interactions, 2.5.5 Target Size and 2.5.6 Concurrent Input Mechanisms.
What WCAG 2.2 added
WCAG 2.2 added nine criteria: two at Level A, four at Level AA and three at Level AAA. They deal with keyboard focus, small or drag-only controls, and the effort of filling in forms and logging in.
| Success criterion | Level | What it asks for, in short |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | The item with keyboard focus isn't completely hidden by a sticky header, banner or widget |
| 2.5.7 Dragging Movements | AA | Anything done by dragging can also be done without dragging |
| 2.5.8 Target Size (Minimum) | AA | Clickable targets are at least 24 by 24 CSS pixels, or have enough space around them |
| 3.2.6 Consistent Help | A | Help options that repeat across pages appear in the same place each time |
| 3.3.7 Redundant Entry | A | People aren't asked to re-type information they already gave in the same process |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logging in doesn't depend on a memory or puzzle test with no alternative |
The three Level AAA additions were 2.4.12 Focus Not Obscured (Enhanced), 2.4.13 Focus Appearance and 3.3.9 Accessible Authentication (Enhanced). Focus Appearance is sometimes described as a Level AA requirement. In the published standard it is Level AAA.
Each of these has exceptions and detail we haven't repeated here. Our WCAG 2.2 success criteria guide walks through the main ones with examples.
Check your site against all 55 criteria
Our free checklist lists every WCAG 2.2 Level A and AA success criterion with a plain-language check, and marks which rows make up the AODA's WCAG 2.0 AA baseline.
Open the WCAG 2.2 AA checklistWhich WCAG version each law requires
Laws name a specific version, and they are updated far less often than WCAG is. That's why different rules point to different versions. This is general information, not legal advice.
| Law or standard | Where it applies | WCAG version and level |
|---|---|---|
| AODA (O. Reg. 191/11, s. 14) | Ontario: public sector, and businesses and non-profits with 50 or more employees | WCAG 2.0 Level AA, except live captions and pre-recorded audio description |
| Accessible Canada Regulations (digital accessibility amendments) | Federal public sector and federally regulated businesses with 100 or more employees | CAN/ASC - EN 301 549, whose web requirements are WCAG 2.1 Level AA |
| Section 508 (Revised 508 Standards) | US federal agencies | WCAG 2.0 Level A and AA |
| ADA Title II web rule | US state and local governments | WCAG 2.1 Level AA |
| EN 301 549 v3.2.1 | European Union (the standard EU accessibility law currently refers to) | WCAG 2.1 Level AA |
AODA: WCAG 2.0 Level AA
Section 14 of Ontario's Integrated Accessibility Standards Regulation requires public websites and web content to conform to WCAG 2.0 Level AA. It applies to public sector organizations and to businesses and non-profits with 50 or more employees in Ontario. Two criteria are excepted: 1.2.4 Captions (Live) and 1.2.5 Audio Description (Prerecorded).
The regulation has not been updated to WCAG 2.1 or 2.2. If you're subject to the AODA, the 38 WCAG 2.0 Level A and AA criteria, less those two exceptions, are your legal baseline. Our AODA requirements guide covers who has to do what, and Is my website AODA compliant? explains how to check.
Accessible Canada Act: WCAG 2.1 Level AA, through EN 301 549
The federal Accessible Canada Act works through regulations and standards. Amendments to the Accessible Canada Regulations published in December 2025 add digital accessibility requirements that point to the national standard CAN/ASC - EN 301 549. The current edition is an identical adoption of the 2021 European standard, and its web clause is built on WCAG 2.1 Level AA.
According to the Government of Canada's summary of the changes, the web page rules start on December 5, 2027 for federal public sector organizations and on December 5, 2028 for federally regulated businesses with 100 or more employees. The regulations refer to the most recent version of the standard, so the WCAG version could change if the standard is updated. Most Ontario businesses are provincially regulated and fall under the AODA instead; see Accessible Canada Act vs. AODA.
Section 508: WCAG 2.0 Level A and AA
Section 508 covers technology that US federal agencies buy, build and use. The Revised 508 Standards incorporate the WCAG 2.0 Level A and AA success criteria by reference. If you sell software or services to US federal buyers, this is the version your VPAT or ACR will be read against.
ADA Title II rule: WCAG 2.1 Level AA
In 2024 the US Department of Justice adopted a rule under Title II of the ADA that requires the web content and mobile apps of state and local governments to meet WCAG 2.1 Level AA. According to the department's fact sheet, an interim final rule published in April 2026 extended the compliance dates to April 26, 2027 for governments serving 50,000 or more people, and April 26, 2028 for smaller governments and special districts.
This rule covers governments, not private businesses. For how US and Ontario law compare, see AODA vs. ADA.
EN 301 549: WCAG 2.1 Level AA, with 2.2 on the way
EN 301 549 is the European standard for accessible technology. Version 3.2.1, published in 2021, is the one EU accessibility law currently refers to, and its web requirements are WCAG 2.1 Level AA. The European Commission's AccessibleEU centre reports that version 4.1.1, which adopts WCAG 2.2, was published in September 2026. It does not become the legal reference until the Commission cites it in the Official Journal of the European Union.
Which version should you target?
For most organizations, WCAG 2.2 Level AA. The reasons are practical:
- It covers every older requirement. One round of testing against 2.2 AA answers the AODA (2.0 AA), Section 508 (2.0 AA), and the rules that point to 2.1 AA.
- It is what the W3C recommends. The W3C encourages using the latest version of WCAG, and says the best way to prepare for future guidelines is to meet WCAG 2.2 now.
- The standards are moving that way. WCAG 2.2 is now also an ISO standard (ISO/IEC 40500:2025), and the newest edition of EN 301 549 adopts it.
- The newer criteria fix real problems. WCAG 2.0 says nothing about reflow on a phone, the contrast of form field borders, or controls too small to tap. Customers run into those barriers whether or not a law names them.
There are two cases where the exact version still matters. The first is your legal statement: if you file an AODA compliance report, the question you're answering is about WCAG 2.0 Level AA, so your audit report should show which findings fall inside that baseline and which go beyond it. The second is a contract: if a buyer's RFP names WCAG 2.1 AA or Section 508, report against the version they named.
If your site has a long list of failures and a deadline, fix the WCAG 2.0 AA failures first, because those are the legal requirement in Ontario, then work through the 2.1 and 2.2 additions. Our AODA website compliance checklist is a good starting point.
CodexMotive audits against WCAG 2.2 Level AA by default, which covers the AODA baseline in the same pass. You can run a free automated scan for a first look, or see our fixed packages for a manual audit.
What about WCAG 3?
WCAG 3 is a separate, future standard, and it is not something to plan around yet. The W3C's WCAG 3 introduction describes it as an incomplete working draft that will change, and says it is not expected to be a completed standard for a few more years.
The W3C also says WCAG 3 will not supersede WCAG 2, and that WCAG 2 will not be deprecated for several years after WCAG 3 is finalized. No law we cover in this article refers to it. Work done to meet WCAG 2.2 today is not wasted.
Frequently asked questions
Which WCAG version does the AODA require?
WCAG 2.0 Level AA, with two exceptions: live captions and pre-recorded audio description. It applies to the public websites of Ontario's public sector and of businesses and non-profits with 50 or more employees. The regulation has not been updated to WCAG 2.1 or 2.2.
If my site meets WCAG 2.2 AA, does it meet the AODA's WCAG 2.0 AA rule?
Yes. The W3C states that content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and 2.0. The only criterion 2.2 dropped is 4.1.1 Parsing, which the W3C says should be considered always satisfied for HTML content in the older versions.
What is the difference between WCAG 2.0 and 2.1?
WCAG 2.1 added 17 success criteria to WCAG 2.0, 12 of them at Level A or AA. They cover mobile accessibility, low vision and cognitive and learning disabilities, with requirements such as reflow, non-text contrast, text spacing and status messages.
What is the difference between WCAG 2.1 and 2.2?
WCAG 2.2 added nine success criteria, six of them at Level A or AA, and removed 4.1.1 Parsing. The additions cover keyboard focus being hidden, dragging, target size, consistent help, redundant entry and accessible authentication.
Is WCAG 2.0 outdated?
It is still a valid standard, and it is still the version the AODA and Section 508 name. But it was published in 2008 and misses barriers that 2.1 and 2.2 address, especially on phones. Treat it as the legal floor, not the goal.
Should I wait for WCAG 3?
No. The W3C describes WCAG 3 as an incomplete draft that is a few years from being a finished standard, and says the best way to prepare for it is to meet WCAG 2.2 now.