WCAG Mobile Requirements — Complete Guide for App & Web Developers 2026

If you're developing mobile apps or mobile websites, understanding WCAG mobile requirements is essential. The Web Content Accessibility Guidelines (WCAG) 2.1 and WCAG 2.2 include specific success criteria designed for mobile accessibility — covering touch targets, gestures, orientation, reflow, and screen reader compatibility.

This comprehensive guide covers all WCAG mobile requirements — from touch target size and pointer gestures to orientation and reflow. Learn how to test, common violations, and best practices for mobile accessibility.

Why WCAG Mobile Requirements Matter

WCAG mobile requirements are essential for several reasons:

• Legal Compliance: ADA Title III, Section 508, and the European Accessibility Act (EAA) apply to mobile apps and mobile websites. Courts have increasingly ruled that mobile apps must be accessible.
• Massive User Base: Over 7 billion people use mobile devices. Over 2.2 billion people have some form of visual impairment.
• App Store Rankings: Google and Apple prioritize accessibility in their algorithms. Accessible apps rank higher in app store search results.
• Legal Protection: ADA lawsuits targeting mobile apps have increased significantly. Testing and remediating your mobile app reduces your legal risk.

WCAG Mobile Requirements — Complete List

1. 1.3.4 — Orientation (Level AA)

Content should not be restricted to a single orientation. Users must be able to view content in both portrait and landscape modes.

What to Test:

• ✅ App works in both portrait and landscape orientation
• ✅ Content is fully accessible in both orientations
• ✅ No content is cut off or hidden when orientation changes

Common Violation: App locked to portrait or landscape only.

Fix: Support both portrait and landscape orientations unless a specific orientation is essential (e.g., a game that requires landscape).

2. 1.4.10 — Reflow (Level AA)

Content must reflow to fit the screen without requiring horizontal scrolling. The equivalent of 320px width.

What to Test:

• ✅ No horizontal scrolling required
• ✅ Text wraps to fit the screen when zoomed
• ✅ Content is readable at 400% zoom

Common Violation: Content requires horizontal scrolling on small screens.

Fix: Use responsive design with proper viewport settings. Avoid fixed-width layouts.

3. 1.4.11 — Non-text Contrast (Level AA)

UI components (buttons, icons, focus indicators) must have sufficient contrast (3:1).

What to Test:

• ✅ Buttons have 3:1 contrast against background
• ✅ Icons have 3:1 contrast against background
• ✅ Focus indicators have 3:1 contrast

Common Violation: UI components with low contrast against the background.

Fix: Check color contrast for all UI components. Use our color contrast checker.

4. 1.4.12 — Text Spacing (Level AA)

Users can adjust text spacing for readability. Requires line height, spacing, and word spacing adjustments.

What to Test:

• ✅ Text spacing can be adjusted without breaking content
• ✅ Line height can be set to 1.5 times font size
• ✅ Paragraph spacing can be set to 2 times font size

Common Violation: Text spacing adjustments break layout or hide content.

Fix: Use relative units (em, rem) and avoid fixed height containers.

5. 2.5.1 — Pointer Gestures (Level A)

All multi-touch gestures (like pinch-to-zoom) must have a single-tap alternative.

What to Test:

• ✅ Multi-touch gestures have single-tap alternatives
• ✅ Pinch-to-zoom has a zoom button alternative
• ✅ Swipe gestures have button alternatives

Common Violation: Features only accessible via multi-touch gestures.

Fix: Provide alternative controls for all gestures. For example, add zoom buttons for pinch-to-zoom.

6. 2.5.2 — Pointer Cancellation (Level A)

Users must be able to cancel pointer actions (like accidental taps).

What to Test:

• ✅ Accidental taps can be canceled
• ✅ Actions execute on "up" events (touchend), not "down" events (touchstart)
• ✅ Users can slide finger away to cancel

Common Violation: Actions execute immediately on touch (touchstart).

Fix: Use "up" events (touchend) instead of "down" events (touchstart) for critical actions.

7. 2.5.3 — Label in Name (Level A)

Accessible names must match visual labels for voice control compatibility.

What to Test:

• ✅ Accessible name matches visual label
• ✅ Voice control users can interact with elements
• ✅ Buttons have matching labels and accessible names

Common Violation: Accessible name doesn't match visual label (e.g., "Submit" button with "Confirm" accessible name).

Fix: Ensure accessible names match visible text labels.

8. 2.5.4 — Motion Actuation (Level A)

Users must be able to disable motion-based controls (like shake to undo).

What to Test:

• ✅ Motion actuation can be disabled in settings
• ✅ Alternative controls exist for motion-based actions
• ✅ Users with mobility disabilities can access all features

Common Violation: Features only accessible via motion (shake, tilt).

Fix: Provide a setting to disable motion actuation. Provide alternative controls for motion-based actions.

9. 2.5.7 — Dragging Movements (Level AA — WCAG 2.2)

Dragging actions must have a single-tap or alternative interaction.

What to Test:

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

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.

10. 2.5.8 — Target Size (Minimum) (Level AA — WCAG 2.2)

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.

WCAG Mobile Requirements — Quick Reference Table

How to Test WCAG 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.1 and 2.2 standards.

Step 2: Manual Testing with Mobile Screen Readers

Test your mobile app with actual screen readers:

• VoiceOver on iOS (iPhone, iPad)
• TalkBack on Android
• Navigate using only touch gestures and audio feedback

Step 3: Touch Target Testing

Check that all touch targets are at least 24x24 pixels. Use developer tools or manual measurement.

Step 4: Color Contrast Testing

Test color contrast using our color contrast checker or mobile contrast checker tools.

Step 5: Gesture Testing

Test all gestures (pinch, swipe, drag, shake) and verify alternatives exist.

Mobile Accessibility Checklist

Frequently Asked Questions — WCAG Mobile Requirements

Internal Links — Mobile Accessibility Resources