Android Switch Access · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Start from the user’s established setup
Switch Access is an access method, not a generic performance setting. If the user already relies on it, retain the current switch assignments and scanning arrangement. Choose a harmless target in the interface and ensure that assistance or a known recovery route is available before experimenting with how selections are made.
Distinguish automatic and step scanning
Google documents auto-scanning with one switch, where the highlight advances and the switch selects, and step scanning with separate Next and Select assignments. Check the actual available method and hardware. Do not assume that a moving highlight means the app is scrolling unexpectedly or that every switch performs the same action.
Review timing deliberately
Google’s settings include scan time, an initial-item delay and the number of scans, along with methods such as linear or row-column scanning. Use the values appropriate to the person’s interaction needs. Faster is not automatically better: a target that moves away before the user can select it is a usability barrier, not an improvement.
Test a concrete non-destructive action
Use an ordinary menu item before trying any purchase or deletion control. Confirm which switch advances and which selects, and note the target’s visible state. If the app’s controls cannot be selected meaningfully, report that precise barrier. Do not interpret the scan cadence as programme buffering or change a service account to solve an input-navigation problem.
Questions, answered
Do auto-scanning and step scanning use identical switch roles?
No. Google documents different assignments.
Is the fastest scan always the best setting?
No. The target must remain usable for the person’s selection needs.