Can't touch this - Different ways users interact with their mobile devices

Panula introduces alternatives to touch for people who cannot see or use a touchscreen easily. She outlines screen readers, physical keyboards, switch devices, voice recognition, and screen magnification, then explains why developers should consider and test these methods.

Screen readers such as TalkBack and VoiceOver provide speech or Braille feedback and navigation options; text-to-speech reads selected text but does not offer the same navigation. Physical keyboards can help people with motor disabilities or tremors avoid small touch targets. Modified keyboards and keyboard-mimicking devices use the same events, so developers can begin testing with a regular keyboard.

Switch devices let users navigate and select items with one or two controls, which may be buttons, eye tracking, facial expressions, joysticks, or sip-and-puff controls. Panula notes that Stephen Hawking used a cheek switch to navigate and communicate. Voice recognition supports spoken commands, while larger text, device zoom, and screen magnification can help people with low vision.

For keyboard users, Panula recommends visible focus styles with enough contrast against both the background and the highlighted component. Screen reader users benefit from headings marked programmatically with an accessibility role. Use semantic controls such as buttons where possible; custom elements need an accessible name, role, and relevant state.

Panula says to respect the operating system's reduced motion setting, which can help people avoid distraction, nausea, or dizziness. In React Native, developers can check it with AccessibilityInfo's isReduceMotionEnabled method and omit animations or use reduced versions when enabled. She closes by urging developers to learn accessibility semantics and test with screen readers, keyboards, and switches.