WCAG 2.2 Mobile Success Criteria — Complete Guide for App & Web Developers 2026

If you're developing mobile apps or websites, understanding WCAG 2.2 mobile success criteria is essential. WCAG 2.2 was published in October 2023 and introduced several new success criteria specifically for mobile accessibility — including Target Size (2.5.8) and Dragging Movements (2.5.7).

This comprehensive guide covers all WCAG 2.2 mobile success criteria — from new requirements and changes from WCAG 2.1 to how to test and implement them.

What is WCAG 2.2?

WCAG 2.2 (Web Content Accessibility Guidelines 2.2) was published in October 2023. It builds on WCAG 2.1 and introduces 9 new success criteria — 5 of which are particularly relevant to mobile accessibility.

WCAG 2.2 is the latest version of the international standard for web accessibility. It is referenced by ADA Title III, Section 508, the European Accessibility Act (EAA), and most other accessibility laws.

WCAG 2.2 includes all success criteria from WCAG 2.0 and 2.1, plus new criteria that address emerging needs in mobile accessibility, cognitive accessibility, and user experience.

WCAG 2.2 Mobile Success Criteria — Complete List

1. 2.5.7 — Dragging Movements (Level AA)

All dragging movements must have a single-tap or alternative interaction. Users must be able to complete actions without dragging.

What to Test:

• ✅ Dragging has single-tap alternatives
• ✅ Users can tap to adjust values instead of dragging
• ✅ Drag-and-drop has alternative controls
• ✅ Sliders can be tapped to adjust values

Common Violation: Features only accessible via dragging (e.g., sliders, drag-and-drop).

Fix: Provide alternative controls for drag interactions. For sliders, provide tap-to-adjust functionality.

/* Example: Slider with tap alternatives */
<input type="range" min="0" max="100" value="50">
<div class="slider-controls">
    <button onclick="adjustSlider(-10)">-10</button>
    <span id="sliderValue">50</span>
    <button onclick="adjustSlider(10)">+10</button>
</div>

2. 2.5.8 — Target Size (Minimum) (Level AA)

Touch targets must be at least 24x24 pixels (with exceptions).

What to Test:

• ✅ All touch targets are at least 24x24px
• ✅ Buttons, links, form fields meet minimum size
• ✅ Spacing between targets is adequate

Common Violation: Small touch targets that are hard to tap.

Fix: Ensure touch targets meet 24x24px minimum. Consider 44x44pt for iOS and 48x48dp for Android recommendations.

3. 2.4.11 — Focus Not Obscured (Level AA)

Focus indicators must not be hidden by the keyboard or other UI elements.

What to Test:

• ✅ Focused elements aren't hidden by keyboard
• ✅ Focused elements aren't obscured by overlays
• ✅ Users can see where they are when navigating

Common Violation: Keyboard covers focused input fields.

Fix: Ensure keyboard doesn't obscure focused elements. Use scrollIntoView() to bring focused elements into view.

4. 2.4.12 — Focus Appearance (Level AAA)

Focus indicators must have at least 3:1 contrast and be at least 2px thick.

What to Test:

• ✅ Focus indicators have 3:1 contrast
• ✅ Focus indicators are at least 2px thick
• ✅ Focus indicators cover the full element

Common Violation: Invisible or low-contrast focus indicators.

Fix: Add visible focus indicators with sufficient contrast.

5. 3.3.7 — Redundant Entry (Level A)

Autofill should reduce redundant data entry where possible.

What to Test:

• ✅ Autofill attributes are used correctly
• ✅ Users can autofill common fields (name, address, email)
• ✅ Previously entered information is reused

Common Violation: Users must repeatedly enter the same information.

Fix: Use HTML autofill attributes: <input autocomplete="name">

WCAG 2.2 vs WCAG 2.1 — Mobile Changes

How to Test WCAG 2.2 Mobile Requirements

Step 1: Use Our Free Mobile Accessibility Checker

Upload your app or enter your mobile website URL in our mobile accessibility checker for automated testing against WCAG 2.2 standards.

Step 2: Manual Testing

Test each WCAG 2.2 criterion manually:

• 2.5.7 Dragging: Check if sliders and drag interactions have tap alternatives
• 2.5.8 Target Size: Measure touch targets (24x24px minimum)
• 2.4.11 Focus Not Obscured: Check if keyboard covers focused elements
• 2.4.12 Focus Appearance: Check focus indicator contrast and size
• 3.3.7 Redundant Entry: Check autofill support

Step 3: Test with Screen Readers

Test with VoiceOver (iOS) and TalkBack (Android) to verify screen reader compatibility.

WCAG 2.2 Mobile Checklist

Frequently Asked Questions — WCAG 2.2 Mobile

Internal Links — Mobile Accessibility Resources