What Changed in WCAG 2.2 for eLearning?

You finally got your team comfortable with the Web Content Accessibility Guidelines (WCAG) 2.1. Templates updated, checklists printed, testers trained. Then WCAG 2.2 arrived, and now clients are asking whether your courses meet it. Is it a big rewrite or a few tweaks? Which changes matter for courses, and which are about websites you'll never build? Thankfully, the WCAG 2.2 eLearning changes are focused and very doable. What changed in WCAG 2.2, and what do course builders need to do about it?

WCAG 2.2 added nine new success criteria and removed one obsolete one, and six of the new criteria sit at Levels A and AA, where most eLearning teams aim. For courses, the most important changes are about focus not being hidden behind sticky player bars, alternatives to drag-and-drop, minimum target sizes for buttons, consistent placement of help, not asking learners to re-enter information, and login steps that don't depend on memory puzzles. Everything from WCAG 2.1 still applies. The World Wide Web Consortium (W3C) published WCAG 2.2 as a Recommendation in October 2023, and content that meets 2.2 also meets the earlier versions. Most teams get there by updating templates and adding a few tests.

What Are the New WCAG 2.2 Success Criteria?

Here's the full list of additions, with a plain-language note on what each means for a course. The official wording is in the WCAG 2.2 Recommendation.

One criterion was removed: 4.1.1 Parsing. It dealt with code errors that modern browsers and assistive technologies now handle on their own, so the W3C marked it obsolete.

Who Do the New Criteria Help?

The additions mostly help three groups that earlier versions served less well. People with motor disabilities benefit from larger targets and alternatives to dragging. People with low vision and keyboard users benefit from focus that stays visible. People with cognitive and learning disabilities, including memory difficulties, benefit from consistent help, no repeated typing and logins that don't rely on recall.

Mobile learners benefit considerably as well, because bigger targets and tap-based alternatives to dragging make courses much easier to use on a phone, with or without a disability. That's a nice reminder that accessibility work rarely helps only one group.

Which WCAG 2.2 Changes Hit eLearning Hardest?

Focus Hidden Behind the Player

Many course players have a fixed navigation bar at the top or bottom, and many courses add sticky headers, pop-up glossaries or notification banners. When a keyboard user tabs to a button that sits underneath one of these, they can't see where they are. Criterion 2.4.11 says the focused item can't be entirely hidden by content you added.

Test it by tabbing through every screen, especially ones with long scrolling content. If focus disappears under a bar, adjust the layout, add scroll padding or make the overlay close when focus moves.

Drag-and-Drop Interactions

This is the most significant change for course builders, because drag-and-drop sorting, matching and labeling activities are everywhere in eLearning. Criterion 2.5.7 requires that the same task can be done with single clicks or taps, without dragging, unless dragging is essential.

A common fix is a "select, then place" pattern: click an item, then click its destination. Another is to offer a dropdown or multiple-choice version of the same activity. Keyboard access was already required under earlier versions, so if you've built a good keyboard alternative, you may be close already. Just check that a mouse or touch user can complete it without dragging, too.

Small Buttons and Close Controls

Player controls, close buttons on pop-ups, small "next" arrows and closely packed answer choices can fail criterion 2.5.8. Targets need to be at least 24 by 24 CSS pixels, or spaced so a 24-pixel circle around each one doesn't overlap its neighbors. There are exceptions, such as links inside a sentence. In practice, bigger targets help everyone on a phone and anyone with a tremor.

What About Help, Forms and Logins?

These three criteria often involve the learning management system (LMS) and the course together, so you may need to talk to whoever manages your platform.

• Consistent Help (3.2.6). If your course has a help button, a contact link or a support chat, keep it in the same relative position on every screen. Most templates already do this. Check any custom screens that break the pattern.
• Redundant Entry (3.3.7). If a course or registration flow asks for a learner's name, employee ID or department, don't ask again later in the same process. Fill it in automatically or let them select it. End-of-course evaluations and certificate forms are frequent offenders.
• Accessible Authentication (3.3.8). Logins shouldn't require someone to remember and type a code or solve a puzzle without an alternative. Allowing password managers and copy-and-paste into password fields goes a long way. Single sign-on through your organization's existing login also helps.

How Should You Update Your Templates and Quality Checks?

The fastest route is to fix the patterns once, in your templates, rather than course by course.

1. Audit your player and master template for focus hidden by fixed bars, small controls and help placement.
2. Rebuild your drag-and-drop interaction templates with a non-drag alternative built in.
3. Set minimum button sizes in your style guide.
4. Review registration, evaluation and certificate forms for repeated questions.
5. Ask your LMS team or vendor how login meets the authentication criterion.
6. Add the new checks to your quality assurance (QA) checklist: tab through looking for hidden focus, complete each interaction without dragging, and measure small targets.

Then update your conformance statements, because if a client asks whether your courses meet WCAG 2.2 AA, you'll want test results to show, not just a yes.

Does WCAG 2.2 Change Anything About Contrast?

No. The contrast requirements for text and interface components stayed the same as in WCAG 2.1. That's worth knowing, because contrast is still one of the most common failures in courses, especially on branded color schemes. If that's an area your team struggles with, this guide to color contrast in eLearning walks through the ratios and the quickest ways to test them.

Should You Target WCAG 2.2 Now?

For most teams, yes. It's backward compatible, the new requirements are focused, and they fix real problems learners face, like hidden focus and fiddly drag-and-drop activities. Some buyers are already moving their requirements to 2.2, and building to it now saves you from retrofitting later.

If a contract names an earlier version, meet that version at minimum, knowing that building to 2.2 AA will cover it.

Getting WCAG 2.2 Right in Your eLearning

What changed in WCAG 2.2? Nine new criteria, six of them at A and AA, and one obsolete criterion removed. For eLearning, the changes that matter most are focus not hidden by player bars, alternatives to dragging, bigger targets, consistent help, no repeated data entry and easier logins.

None of these require starting over. Update your templates, rebuild your drag-and-drop patterns, add the new checks to QA and talk to your LMS team about logins. Do that once, and every course you build afterward will be easier for more learners to use.

← All articles