Testing with Mobile Assistive Technology

Mobile accessibility testing verifies that websites and applications work
correctly with the assistive technologies built into smartphones and tablets.
The two primary platforms are iOS with VoiceOver and Android with TalkBack.
Mobile testing is increasingly important as a growing proportion of users
access the web primarily on mobile devices, and mobile assistive technology
usage is significant among users with disabilities.
^[1]

---

iOS — VoiceOver

Enabling VoiceOver on iPhone/iPad

Settings → Accessibility → VoiceOver → toggle on.

Tip: Add VoiceOver to the Accessibility Shortcut (Settings → Accessibility →
Accessibility Shortcut → VoiceOver) so it can be toggled with a triple-click
of the side button.

Core gestures

Gesture	Action
Swipe right	Next element
Swipe left	Previous element
Double tap	Activate selected element
Three-finger swipe up/down	Scroll
Two-finger tap	Pause/resume speech
Two-finger scrub (Z shape)	Back / escape
Rotor gesture (two fingers, rotate)	Change navigation mode
[2]

The VoiceOver Rotor on iOS

The Rotor (two-finger rotation gesture) provides navigation options —
headings, links, form controls, landmarks — equivalent to NVDA's elements
list. Select a category and use swipe up/down to navigate between items
of that type.

What to test on iOS

• Swipe through all content — verify everything is announced meaningfully
• Verify tap targets are reachable and activatable with double tap
• Test forms — verify labels, error messages, and input types are correct
• Test custom components — verify roles and states are announced
• Verify modals trap focus and can be dismissed with the scrub gesture

---

Android — TalkBack

Enabling TalkBack on Android

Settings → Accessibility → TalkBack → toggle on. The exact path varies
by device manufacturer and Android version.

Alternatively: press and hold both volume keys simultaneously (on most
Android devices).

Core gestures (default gesture mode)

Gesture	Action
Swipe right	Next element
Swipe left	Previous element
Double tap	Activate selected element
Three-finger swipe	Scroll
Swipe up then right	TalkBack menu
Swipe right then left	Navigate back
[3]

What to test on Android

• Swipe through all interactive elements
• Verify custom components announce role and state correctly
• Test form inputs — verify labels and error associations
• Verify pop-up dialogs and bottom sheets are announced and focusable
• Test with both Chrome and the device default browser

---

Touch target sizes

WCAG 2.5.8 (Target Size, AA in WCAG 2.2) requires interactive targets to
be at least 24×24 CSS pixels, with spacing that prevents adjacent targets
from being too close. The AAA criterion 2.5.5 recommends 44×44 pixels.

On mobile, small touch targets are a common source of failures for users
with motor impairments or reduced dexterity. Test with a physical device
rather than browser emulation where possible — touch target issues are
difficult to detect on a desktop browser.

---

Using browser DevTools mobile emulation

Chrome DevTools' device emulation (Toggle device toolbar in DevTools)
simulates mobile screen sizes and touch events. It is useful for:

• Testing responsive layout at mobile breakpoints
• Checking that reflow at 320px width does not cause horizontal scrolling
• Preliminary testing of touch interaction patterns

It does not replicate actual assistive technology behaviour. Always
supplement emulator testing with real device testing.

---

References

1. W3C Web Accessibility Initiative. Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile. https://www.w3.org/TR/mobile-accessibility-mapping/ ↑
2. Apple. Use VoiceOver on iPhone. https://support.apple.com/guide/iphone/turn-on-and-practice-voiceover-iph3e2e415f/ios ↑
3. Google. Get started on Android with TalkBack. https://support.google.com/accessibility/android/answer/6283677 ↑