WCAG 2.1 vs WCAG 2.2: What Changed and Does It Affect Universities?

WCAG 2.2 was published in October 2023, adding 9 new success criteria to the accessibility standard. If your university is targeting WCAG 2.1 AA compliance, you might be wondering: Do we need to update our target?

Here's the practical breakdown for higher education.

The Quick Answer

For most universities in 2026:

• Legal requirement: WCAG 2.1 AA (US ADA Title II, Australian DDA)
• Recommended target: WCAG 2.1 AA
• Future-proofing: Plan migration to WCAG 2.2 AA by 2027-2028

Why not WCAG 2.2 now?

• Tools and testing frameworks are still catching up
• Regulatory guidance still references 2.1
• Focus resources on achieving 2.1 first

What's New in WCAG 2.2

The 9 New Success Criteria

WCAG 2.2 added criteria across three levels:

Level A (Minimum):

• None added

Level AA (Standard):

1. 2.4.11 Focus Not Obscured (Minimum) - When something receives keyboard focus, it's not entirely hidden by other content
2. 2.4.13 Focus Appearance - Focus indicators meet minimum size and contrast requirements
3. 2.5.7 Dragging Movements - Functionality requiring dragging has a single-pointer alternative
4. 2.5.8 Target Size (Minimum) - Clickable targets are at least 24×24 CSS pixels
5. 3.2.6 Consistent Help - Help mechanisms appear in consistent locations
6. 3.3.7 Redundant Entry - Don't make users re-enter information already provided
7. 3.3.8 Accessible Authentication (Minimum) - No cognitive function tests for login

Level AAA (Enhanced):

1. 2.4.12 Focus Not Obscured (Enhanced) - No part of focused element is hidden
2. 3.3.9 Accessible Authentication (Enhanced) - Even stricter authentication requirements

What Was Removed

One criterion from WCAG 2.1 was removed:

• 4.1.1 Parsing - HTML validation errors no longer a WCAG failure

This was removed because modern browsers handle parsing errors gracefully, and the criterion caused confusion.

Impact Assessment for Higher Education

High Impact (Likely Affects Your Institution)

2.5.8 Target Size (Minimum)

Requirement	What It Means
24×24 CSS pixels	Minimum clickable area for interactive elements
Exceptions	Inline links in text, user-customizable, essential size

Why it matters for universities:

• LMS navigation (small buttons, icons)
• Mobile learning (touch targets)
• Quiz interfaces (radio buttons, checkboxes)
• Interactive simulations

Likely violations:

• Small "X" buttons to close modals
• Tiny navigation arrows
• Compact icon-only buttons
• Closely spaced multiple-choice options

2.5.7 Dragging Movements

Requirement	What It Means
Single-pointer alternative	Any drag-and-drop must also work with clicks/taps

Why it matters for universities:

• Drag-to-reorder quiz questions
• Drag-and-drop matching exercises
• Canvas/Blackboard drag-to-rearrange modules
• Interactive lab simulations

Likely violations:

• Matching exercises that only work with drag-and-drop
• Reordering activities with no alternative
• Interactive maps requiring drag to navigate

3.3.8 Accessible Authentication (Minimum)

Requirement	What It Means
No cognitive function tests	Can't require users to remember, recognize, or solve puzzles to log in
Allowed	Password fields with paste enabled, passkeys, SSO

Why it matters for universities:

• CAPTCHAs on login pages
• "Select all images with traffic lights" verification
• Security questions requiring memory
• Picture-based password systems

Likely violations:

• CAPTCHA without audio/accessible alternative
• Image-based verification
• Mandatory security questions

Medium Impact (May Affect Some Content)

2.4.11 Focus Not Obscured (Minimum)

Keyboard focus must be at least partially visible.

University context:

• Sticky headers covering focused elements
• Modal dialogs not managing focus
• Chat widgets overlaying content
• Cookie consent banners

3.2.6 Consistent Help

Help mechanisms (contact info, chat, FAQ links) should be in the same relative location across pages.

University context:

• Most LMS platforms already do this
• Check custom-built department websites
• Ensure consistent placement of support links

3.3.7 Redundant Entry

Don't make users re-enter information already provided in the same process.

University context:

• Multi-page forms (applications, registrations)
• Checkout processes (bookstore, parking permits)
• Survey instruments

Lower Impact (Probably Already Compliant)

2.4.13 Focus Appearance

Focus indicators need specific size and contrast.

University context:

• Most modern CSS frameworks include visible focus styles
• Canvas and Blackboard have reasonable defaults
• Main risk: custom styling that removes/reduces focus indicators

What Regulators Are Saying

United States (DOJ/OCR)

Current position: April 24, 2026 deadline requires WCAG 2.1 AA

Future: DOJ has indicated potential updates to incorporate WCAG 2.2, but no timeline announced

Practical guidance: Achieve 2.1 AA by deadline, document 2.2 roadmap

Australia (AHRC)

Current position: DDA requires "accessibility" with WCAG 2.1 as reference standard

Future: AS EN 301 549 (Australian ICT standard) will likely update to reference 2.2

Practical guidance: WCAG 2.1 AA is sufficient for current DDA compliance

European Union

Current position: EN 301 549 references WCAG 2.1

Future: Update to WCAG 2.2 expected by 2025-2026

Practical guidance: International students/partnerships may require 2.2 earlier

Migration Planning: 2.1 → 2.2

Phase 1: Achieve 2.1 AA (Now - April 2026)

Focus all resources on WCAG 2.1 AA compliance:

• This is the legal requirement
• This is what auditors will check
• This is sufficient for most accessibility

Phase 2: Assess 2.2 Gaps (Q2-Q3 2026)

After achieving 2.1 AA:

• Audit against new 2.2 criteria
• Identify highest-impact gaps
• Estimate remediation effort

Key assessment areas:

• Target sizes (2.5.8) - likely biggest gap
• Drag-and-drop (2.5.7) - depends on interactive content
• Authentication (3.3.8) - check all login flows

Phase 3: Remediate 2.2 (2026-2027)

Prioritize based on:

1. User impact (how many students affected)
2. Legal trajectory (when will 2.2 be required)
3. Effort required (quick wins vs. major rebuilds)

Phase 4: Target 2.2 AA (2027-2028)

Update formal compliance target once:

• Regulatory guidance references 2.2
• Tools and testing mature
• Vendor products support 2.2

Tool Support for WCAG 2.2

Current State (2026)

Tool	WCAG 2.2 Support
axe DevTools	Full support
WAVE	Partial support
Lighthouse	Partial support
Adobe Acrobat	Not yet
Microsoft Office	Limited
Canvas	Not yet
Blackboard Ally	Partial
Aelira	Full 2.1, 2.2 in roadmap

What This Means

• Automated testing for 2.2 is still maturing
• Some criteria require manual testing
• Focus on 2.1 automated testing now
• Plan for 2.2 as tools improve

Practical Checklist: WCAG 2.2 Readiness

Already Compliant (If You Meet 2.1 AA)

You probably already meet these 2.2 criteria if you:

• Use modern CSS frameworks with visible focus styles (2.4.13)
• Have consistent navigation and help placement (3.2.6)
• Don't use CAPTCHA on login (3.3.8)

Likely Need Attention

Review these areas for 2.2 gaps:

• [ ] Target sizes: Check all buttons and interactive elements for 24×24px minimum
• [ ] Drag-and-drop: List all drag interactions, verify alternatives exist
• [ ] Authentication: Audit all login flows for cognitive tests
• [ ] Focus visibility: Check sticky headers don't obscure focused elements
• [ ] Redundant entry: Review multi-page forms for re-entry requirements

Quick Wins

Easy 2.2 improvements you can make now:

1. Increase button sizes in custom CSS (24px minimum)
2. Enable paste in password fields (if disabled)
3. Add alternative to CAPTCHAs (audio, accessible checkbox)
4. Reduce sticky header size to minimize focus obstruction

The Bottom Line

For 2026 compliance:

• Target WCAG 2.1 AA (it's the legal requirement)
• Don't get distracted by 2.2 until 2.1 is solid

For future-proofing:

• Understand what 2.2 adds
• Avoid building new content that violates 2.2
• Plan migration for 2027-2028

Key differences that matter for universities:

• Target sizes (affects all interactive content)
• Drag-and-drop alternatives (affects assessments, simulations)
• Accessible authentication (affects login flows)

The standard evolved. Your compliance target will too. But first, achieve 2.1.

Learn more about Aelira's WCAG support | View compliance features