Questions answered by this guide
- What changed between WCAG 2.1 and 2.2?
- Do I need to redo my accessibility work if I already targeted 2.1?
- What is the new Target Size success criterion?
- What's the Dragging Movements requirement in WCAG 2.2?
- Which WCAG version should my course target?
What you'll learn
- WCAG 2.2 adds new criteria on top of 2.1, it doesn't replace or contradict anything you've already implemented
- The most eLearning-relevant additions: Target Size (Minimum), Dragging Movements, and Focus Appearance
- This Learning Hub already covers the underlying concepts (Tap Target Size Guide, Focus Order Guide), this page frames them as what's new in 2.2 specifically
What's inside
Accessibility specialists and L&D teams tracking which WCAG version their courses should target
- 012.2 is additive, not a replacement
- 02Target Size (Minimum)
- 03Dragging Movements
- 04Focus Appearance
- 05What was removed: Parsing
- 06Which version should you target
Why it matters
WCAG versions build on each other, but a team that hasn't looked at what's new can miss real, specific requirements, particularly ones like target size and dragging alternatives that map directly onto common eLearning interaction patterns (small icon buttons, drag-and-drop questions) rather than abstract technical edge cases.
Best practices
- Target Size (Minimum), WCAG 2.5.8: interactive targets should generally be at least 24 by 24 CSS pixels, or have enough spacing from neighboring targets, directly relevant to small icon buttons and closely packed hotspots. This is the same concept Tap Target & Button Size Guide already covers.
- Dragging Movements, WCAG 2.5.7: any drag-based interaction needs a non-dragging alternative (like a tap-to-select-then-tap-to-place pattern), directly relevant to matching and sorting quiz questions, see Accessible Assessments Guide.
- Focus Appearance, WCAG 2.4.13 (AAA): the visible focus indicator should be large and high-contrast enough to actually see, an enhanced-level criterion worth targeting even at AA if your course already has a custom focus style.
- You don't need to re-audit everything from scratch, review specifically against the new criteria above, most of a 2.1-conformant course carries forward unchanged.
Common mistakes
- Assuming a 2.1-conformant course needs a full re-audit, in practice, only the specific new criteria need checking.
- Overlooking Dragging Movements for a drag-and-drop quiz question that has no alternative selection method.
- Not noticing small icon-only buttons (like a custom "?" help icon) fall under the new Target Size minimum.
How A11yCheck reviews this
A11yCheck's Accessibility checks already include WCAG 2.5.7 (Dragging Movements, via keyboard alternative checks) and 2.5.8 (Target Size, via button/tap-target checks). Focus Appearance (2.4.13, AAA-level) is not currently an automated check, treat it as a manual design review if you're targeting AAA.
Frequently asked questions
Do I need to redo accessibility work I already did against WCAG 2.1?
No, 2.2 is additive. Review specifically against the new criteria (target size, dragging alternatives, focus appearance) rather than re-auditing everything.
What was removed in WCAG 2.2?
Success Criterion 4.1.1 Parsing was dropped, it was originally about HTML parsing errors confusing assistive technology, and is now considered obsolete given how modern browsers and assistive technology actually handle malformed markup.
Which version should a new course target?
2.2 where practical, since it's the more current standard and its new criteria address real, common eLearning patterns. If your organization has a formal policy naming a specific version (common in Section 508 or contract language), follow that instead.
Related Guides
WCAG for eLearning: A Practical Introduction→
What WCAG actually is, and what it means for a Storyline or Rise course. No legal jargon.
Tap Target & Button Size Guide→
How big a button or tap target needs to be, and how to fix ones that are too small or too close together, in Storyline and Rise.
Accessible Assessments Guide→
Quiz interactions fail accessibility in specific, recurring ways: an answer choice reachable only by mouse, feedback that appears but is never announced, a matching or drag-and-drop question with no keyboard path to a correct answer at all.
Focus Order Guide→
Focus order is the order Tab moves through a slide's interactive elements. It should match the order things appear on screen, and it's checked by pressing Tab and watching where focus lands each time.
Section 508 vs WCAG for eLearning→
Section 508 is a U.S. federal law requiring federal agencies (and, by extension, many contractors and federally funded programs) to make electronic content accessible. It doesn't define its own separate technical rules for what "accessible" means, it incorporates WCAG 2.0 Level A and AA by reference. In practice, meeting WCAG AA is what satisfies Section 508's technical requirement.
Summary
WCAG 2.2 adds new criteria on top of 2.1 rather than replacing it, most notably Target Size, Dragging Movements, and Focus Appearance, all directly relevant to common eLearning interaction patterns. A 2.1-conformant course needs a targeted review against what's new, not a full re-audit.
Review your course before you publish it.
A11yCheck reviews Storyline and Rise courses for:
- Accessibility
- Course Quality
- Course Engagement
www.a11ycheck-dev.com