Switch access
A scanning interface that highlights choices in turn so someone can operate the device with one or a few simple switches.
See it
What it is
Switch access lets a person operate a device with one or a few simple inputs instead of precise pointer movement. The switch itself can be a single large button, a sip-and-puff tube, a head or cheek switch, or anything plugged into the 3.5mm ports on an Xbox Adaptive Controller. Apple Switch Control and Android Switch Access scan a highlight through actionable items; the user activates a switch when the highlight reaches the item they want. Scanning can advance automatically or with a second switch.
A site that already has semantic controls, logical focus order, visible focus, and keyboard operation has most of the right foundation. Keep targets large, avoid actions that require dragging or simultaneous presses, and offer a simple button alternative for gesture-heavy tasks.
Every unnecessary focus stop costs time because the user may have to wait through the whole scan to reach the next action. Custom controls that never enter the Tab order disappear from many scanning paths, while focus traps can leave the user cycling inside one region. Test the actual order, not just whether each item can receive focus.
Ask AI for it
Make this flow usable with Apple Switch Control scanning. Use native buttons, links, and form controls in DOM order, remove positive tabindex values, and provide a strong :focus-visible indicator on every action. Remove decorative or duplicate elements from the focus order, replace drag-only and multi-touch actions with labelled buttons, and ensure no focus trap blocks the route to Close or Continue. Keep targets at least 24 by 24 CSS pixels and avoid short timeouts; when a timeout is essential, provide controls to extend or disable it. Write the exact scan sequence for completing the primary task and count how many switch activations it takes.