The key WCAG 2.2 changes affecting eLearning content and LMS platforms, and the practical steps to stay compliant.
What Changed Between WCAG 2.1 and 2.2
WCAG 2.2 became a W3C Recommendation in October 2023, adding nine new success criteria on top of WCAG 2.1 while retiring one (4.1.1 Parsing, deemed no longer necessary given modern browser behaviour). For eLearning teams, the new criteria concentrate heavily on two areas that show up constantly in course interfaces: focus visibility and interactive target usability.
Most existing WCAG 2.1 AA-conformant courses will need targeted fixes, not a full rebuild, but the fixes touch UI patterns that appear on nearly every screen: buttons, form fields, navigation controls, and drag interactions.
The New Success Criteria That Matter Most for eLearning
| Success Criterion | Level | What It Requires |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | Keyboard-focused elements must not be entirely hidden by other content, like sticky headers or footers |
| 2.4.13 Focus Appearance | AAA | Focus indicators must meet minimum size and contrast requirements |
| 2.5.7 Dragging Movements | AA | Any drag-and-drop interaction must have a single-pointer alternative that doesn't require dragging |
| 2.5.8 Target Size (Minimum) | AA | Clickable targets must be at least 24x24 CSS pixels, with limited exceptions |
| 3.2.6 Consistent Help | A | Help mechanisms (contact info, chat, FAQ links) must appear in the same relative order across pages |
| 3.3.7 Redundant Entry | A | Information already entered by a user should not need to be re-entered in the same process |
| 3.3.8 Accessible Authentication (Minimum) | AA | Login processes cannot rely solely on cognitive function tests like memorising or transcribing |
What This Means for Your Existing Content Library
- Audit every drag-and-drop interaction. Scenario-based and gamified modules use drag interactions constantly for sorting, matching, and sequencing exercises — each one now needs a click-based or keyboard-based alternative path.
- Check clickable target sizes across your LMS and custom interactions. Icon-only navigation buttons and small quiz option targets are common failure points.
- Review focus indicator visibility against sticky UI elements. Course players with persistent headers, progress bars, or footers frequently obscure focus outlines for keyboard users.
- Map help and support link placement for consistency across every course template your organisation uses.
- Flag any login or re-authentication flow inside your LMS that depends on cognitive tasks without an accessible alternative.
Practical Steps L&D Teams and EdTech Platforms Should Take
- Run a WCAG 2.2 gap audit against your current content library and LMS shell, not just new content going forward
- Prioritise fixes by criterion, starting with target size and dragging movements, since these affect the widest range of existing interaction types
- Update your instructional design and development templates so new content is built 2.2-conformant from the start, rather than retrofitted later
- Brief your accessibility QA process explicitly on the nine new criteria — a 2.1-trained reviewer will not automatically catch 2.2-specific issues
- Budget remediation work as a distinct project phase rather than assuming it can be absorbed into ongoing production capacity
Why This Isn't Optional
WCAG 2.2 compliance is increasingly referenced directly in procurement requirements for government, higher education, and enterprise L&D contracts, and legal exposure under accessibility statutes in multiple jurisdictions is assessed against the current WCAG version, not whichever version content was originally built to. Treating 2.2 as optional creates both a procurement risk and a legal one.
The Bottom Line
WCAG 2.2's changes are targeted rather than sweeping, but they hit UI patterns that appear throughout almost every eLearning course. A focused audit against the nine new criteria, followed by prioritised remediation, is a manageable project for most organisations — provided it starts before a procurement requirement or an accessibility complaint forces the timeline.
Margo Learning's accessibility audits and remediation work are built around the current WCAG version, including the 2.2 criteria most likely to affect real eLearning interfaces.