Switch Control: An Intro for Mobile App Teams
summary
Switch Control provides independence for people who cannot tap screens and testing uses three practical setups: screen-as-switch (iOS only, very slow), a hardware set like the AbleNet Blue2 (two switches) or the pricier Tecla Shield, and a Bluetooth keyboard (preferred — map arrows to next/previous and Enter to select, use manual scanning). VoiceOver and Switch Control reveal different failures: invisible buttons, swipe-only tabs (Kayak fails to choose dates/destinations), grouped elements that jump focus. Test full workflows, enable the speech feature, and avoid swipe- or invisible-only controls.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:33What does Switch Control do?
- 2:22What is Switch Control?
- 3:46Set up the switches
- 4:34Testing steps (happy path example)
- 8:43Three ways to test Switch Control
- 13:04AbleNet Blue2 vs. Tecla Shield
- 13:49use the screen as a switch
- 14:16use a Switch Control set
- 19:10use a Bluetooth keyboard
- 19:51Bluetooth keyboards
- 20:53What to test with Switch Control?
- 22:57Switch Control with speech
- 23:48Learn on the Home screen - part 3
- 28:05Swipe gesture fail
- 34:31Grouped elements - fail
- 35:26Troubleshooting
- 36:30Do's and Don'ts
- 37:13Where to learn more?
- 38:30Summary
related talks
52mSwitch Control in Action: Enhancing Accessibility
29mCan't touch this - Different ways users interact with their mobile devices
30mPractical Tips to Confidently Support VoiceOver and Voice Control
05mHow to use the Screen Reader you already have in your pocket
37mDeep-Dive Into Mobile Accessibility & Interactive Quiz
40mIs This App Accessible? A Live Testing Demo
12mThe Secrets of Android Accessibility
21mAccessibility 101: Getting started with assistive technology and product inclusion