What Is the Difference Between WCAG 2.0, 2.1, and 2.2?

WCAG 2.0, 2.1, and 2.2 are successive versions of the Web Content Accessibility Guidelines published by the World Wide Web Consortium (W3C). Each version is backward-compatible, meaning WCAG 2.1 includes every success criterion from 2.0, and WCAG 2.2 includes everything from both 2.0 and 2.1. The primary differences are the new success criteria each version adds: WCAG 2.1 introduced requirements for mobile accessibility, low vision, and cognitive disabilities, while WCAG 2.2 added criteria for accessible authentication, consistent help, and dragging alternatives. For universities preparing for the ADA Title II accessibility deadline, WCAG 2.1 Level AA is the legal minimum, but targeting 2.2 is increasingly recommended.

Understanding these differences matters because your compliance obligations depend on which version the relevant law or policy references. Getting it wrong can mean investing effort in the wrong standard or missing criteria that regulators expect you to meet.

A Brief Timeline

WCAG 2.0 was published in December 2008. It established the foundational framework of four principles (Perceivable, Operable, Understandable, Robust) and three conformance levels (A, AA, AAA). Its 61 success criteria became the global baseline for web accessibility and were adopted by reference into laws worldwide.

WCAG 2.1 arrived in June 2018, a full decade later. It added 17 new success criteria (5 at Level A, 7 at Level AA, 5 at Level AAA) without modifying or removing any existing 2.0 criteria. This version was developed in response to the explosion of mobile devices and a growing understanding of cognitive and learning disabilities.

WCAG 2.2 was published in October 2023. It added 9 new success criteria (2 at Level A, 4 at Level AA, 3 at Level AAA) and notably removed one existing criterion (4.1.1 Parsing) that had become redundant due to modern browser behavior. WCAG 2.2 is now the current W3C Recommendation.

What WCAG 2.0 Established

WCAG 2.0 laid the groundwork that all later versions build on. Its success criteria cover the essentials: text alternatives for images, captions for video, keyboard accessibility, sufficient color contrast, readable text, predictable navigation, and input assistance. If you are familiar with accessibility basics — alt text, heading structure, form labels, focus indicators — you are working with WCAG 2.0 concepts.

For years, WCAG 2.0 Level AA was the standard referenced by most accessibility laws and policies. Many institutions built their compliance programs around it. However, 2.0 was written in an era of desktop-first web design, and its criteria do not adequately address touch interfaces, small screens, or the needs of users with cognitive and learning disabilities.

What WCAG 2.1 Added

WCAG 2.1 addressed three major gaps in 2.0: mobile accessibility, low vision support, and cognitive accessibility. The most consequential new criteria at Level AA include:

Mobile and touch accessibility. Criterion 1.3.4 (Orientation) requires that content not be locked to a single display orientation unless essential. Criterion 2.5.1 (Pointer Gestures) ensures that any functionality requiring multipoint or path-based gestures can also be operated with a single pointer. Criterion 2.5.4 (Motion Actuation) prevents content from relying solely on device motion (like shaking or tilting) for input.

Low vision support. Criterion 1.4.10 (Reflow) requires content to reflow without horizontal scrolling at 400% zoom — critical for users with low vision who magnify their screens. Criterion 1.4.11 (Non-text Contrast) extends contrast requirements to UI components and graphical objects, not just text. Criterion 1.4.12 (Text Spacing) ensures content remains functional when users override letter, word, and line spacing.

Cognitive accessibility. Criterion 1.3.5 (Identify Input Purpose) requires that the purpose of common input fields (name, email, phone) be programmatically determinable, enabling browsers and assistive technologies to auto-fill or present icons. Criterion 2.5.3 (Label in Name) ensures that visible labels match their accessible names, reducing confusion for voice control users.

These additions reflect the reality of how people actually use the web today. Students access course materials on phones and tablets. Faculty with low vision rely on screen magnification. Staff with cognitive disabilities benefit from predictable, auto-completable forms. WCAG 2.1 is where PDF accessibility requirements become more comprehensive as well, since many of these criteria apply to document content.

What WCAG 2.2 Added

WCAG 2.2 focused on reducing cognitive burden and improving usability for people with cognitive and learning disabilities, motor disabilities, and low vision. The key new criteria include:

Accessible authentication (Level AA). Criterion 3.3.8 (Accessible Authentication - Minimum) prohibits cognitive function tests — such as remembering a password, solving a puzzle, or transcribing a code — as the sole means of authentication. Users must have an alternative like a password manager, biometric login, or email link. Criterion 3.3.9 (Accessible Authentication - Enhanced, Level AAA) extends this further by prohibiting even object recognition and personal content recognition.

Consistent help (Level A). Criterion 3.2.6 (Consistent Help) requires that if a site provides help mechanisms — such as contact information, a chatbot, or a FAQ link — they appear in the same relative location on every page. This benefits users with cognitive disabilities who rely on consistent page structure.

Focus and target improvements. Criterion 2.4.11 (Focus Not Obscured - Minimum, Level AA) ensures that when a UI component receives keyboard focus, it is not entirely hidden behind other content like sticky headers or footers. Criterion 2.5.8 (Target Size - Minimum, Level AA) requires interactive targets to be at least 24 by 24 CSS pixels, with some exceptions, reducing motor difficulty on both touch and pointer devices.

Dragging alternatives. Criterion 2.5.7 (Dragging Movements, Level AA) requires that any functionality achievable through dragging also be operable with a single pointer without dragging. This helps users who cannot perform drag gestures due to motor disabilities.

Which Version Should Universities Target?

The DOJ ADA Title II rule (compliance now April 2027 after the April 2026 IFR) specifically references WCAG 2.1 Level AA as the technical standard for web content and digital services of state and local government entities, which includes public universities. This is your legal floor — you must meet it.

However, there are strong reasons to target WCAG 2.2 Level AA instead:

• Forward-looking compliance. Regulations tend to adopt newer versions over time. The EU's EN 301 549 (which governs accessibility in European higher education) has already aligned with WCAG 2.1 and is expected to incorporate 2.2. Building to 2.2 now avoids costly retrofitting later.
• Better user experience. The 2.2 criteria address real usability barriers. Accessible authentication alone eliminates a major pain point for students with cognitive disabilities trying to log into your LMS.
• Backward compatibility. Since 2.2 includes all of 2.1, meeting 2.2 automatically satisfies 2.1 requirements. You do not have to choose — you just aim higher.

For a practical breakdown of what to audit, see the WCAG compliance checklist.

How WCAG Versions Map to Laws and Standards

Different regulations reference different WCAG versions:

• ADA Title II (United States): WCAG 2.1 Level AA, per the April 2024 DOJ final rule, with compliance required by April 2027 (extended from 2026 via the IFR) for large entities.
• Section 508 (United States): Currently references WCAG 2.0 Level AA via the 2017 Section 508 Refresh. An update to 2.1 or 2.2 is anticipated but not yet finalized.
• EN 301 549 (European Union): Currently aligned with WCAG 2.1 Level AA. Used as the benchmark for the European Accessibility Act and public sector accessibility directives.
• Disability Discrimination Act / DDA (Australia): Does not reference a specific WCAG version by name but enforcement actions have relied on WCAG 2.0 and 2.1 as the de facto technical standard.

The practical takeaway: if you are a public university in the United States, WCAG 2.1 AA is your legal requirement. If you operate internationally or want to future-proof your compliance, WCAG 2.2 AA is the target.

Backward Compatibility Explained

One of the most important design decisions in the WCAG versioning model is strict backward compatibility. Every success criterion in WCAG 2.0 exists unchanged in 2.1, and every criterion in 2.1 exists unchanged in 2.2 (with the single exception of 4.1.1 Parsing, which was removed in 2.2 because modern browsers and assistive technologies no longer need it).

This means:

• A document or page conforming to WCAG 2.2 Level AA also conforms to WCAG 2.1 Level AA and WCAG 2.0 Level AA.
• You never have to "downgrade" work. Accessibility improvements made to meet 2.2 count toward 2.1 and 2.0 compliance simultaneously.
• Testing tools and checklists for 2.2 cover the full scope of earlier versions.

Moving Forward

The gap between WCAG 2.0 and 2.2 represents fifteen years of evolving understanding about how people with disabilities use digital content. Universities that still benchmark against 2.0 alone are missing criteria that address how students, faculty, and staff actually interact with your platforms — on mobile devices, with cognitive accommodations, and through assistive authentication methods.

Start by auditing your digital presence against WCAG 2.1 Level AA to meet the ADA Title II deadline, then layer in 2.2 criteria where feasible. Pay particular attention to authentication flows, help placement, and target sizes — these are the areas most likely to affect your campus community today.

Aelira's accessibility scanning and remediation tools evaluate documents and web content against the full WCAG 2.2 Level AA criteria set, helping your institution identify gaps and fix them before the compliance deadline arrives.