Skip to content

Some people run everything with one or two switches: a large button pressed with a hand, foot, or head, a sip-and-puff tube, or even a blink. A highlight steps through the screen one item at a time, and they press when it lands on what they want. Every extra step on a page costs them time and effort.

Picture a highlight moving across the screen, one control at a time. You can only say "that one" when it lands on what you want. Miss it, and you wait for it to come all the way back around. That's scanning, the most common way switch access works.

Some setups use two switches instead, one to move and one to select. Others scan in groups: first a region of the screen, then a row, then the item. Typing means scanning an on-screen keyboard, one letter at a time.

Switch users rely on the same structure keyboard users do, so the keyboard guide applies here too. The difference is cost. Ten extra Tabs takes a keyboard user a second or two. For a switch user, it's a wait on every page, and one missed press means waiting for the whole loop again.

Common tools

Switch Control
Built into Mac, iPhone, and iPad.
Switch Access
Built into Android.
Switches
Buttons, sip-and-puff, head, and blink switches, over USB or Bluetooth.
Scanning software
Windows apps like Grid 3, with scanning and on-screen keyboards.

Most of these are small changes in the code. Where WCAG covers one, we link the success criteria it falls under.

  1. Too many stops before the content

    A header with a logo, 30 navigation links, a search box, social icons, and a cookie banner. A mouse user ignores all of it. A switch user scans past all of it, or group after group of it, on every page, before reaching what they came for.

    The fix

    Add a skip link as the first thing on the page, so one press can jump past the header to the content. Use landmarks (header, nav, main) too. Keep navigation lean, and tuck related links into menus that open on demand.

  2. Time limits and moving content

    A session times out partway through a long form. A carousel slides on before the highlight reaches it. A countdown offer expires. When each action takes several presses, short time limits shut people out.

    The fix

    Warn people before a session expires and let them extend it with one action. Don't auto-advance carousels, or give them a pause button that's easy to reach.

  3. Tiny or crowded targets

    Some switch setups point at a spot instead of stepping through items: a line sweeps across the screen, then another sweeps down, and the press lands where they cross. Small links packed close together are easy to miss, and a miss means starting the sweep over.

    The fix

    Make targets at least 24 by 24 CSS pixels, with space around them, and bigger for the main actions. 44 by 44 is a comfortable size for most things people tap.

  4. Focus that resets after every action

    Someone checks a filter, and the whole page reloads with the highlight back at the top. Changing a dropdown jumps to a new page with no warning. Each reset means scanning all the way back to where they were.

    The fix

    Update results without reloading the page, and keep focus on the control that was used. Let people choose filters and then apply them, instead of acting on every change.

  5. Asking for the same thing twice

    Typing with a switch means scanning an on-screen keyboard one letter at a time. A form that asks for the shipping address again for billing, or clears the form after one error, throws away a lot of hard work.

    The fix

    Add autocomplete attributes so the browser can fill in names, emails, and addresses. Offer "Same as shipping," keep what people entered when there's an error, and don't ask for the same information twice in one process.

    Example
    <input name="name" autocomplete="name">
    <input name="email" type="email" autocomplete="email">
    <input name="street" autocomplete="address-line1">
    <input name="zip" autocomplete="postal-code">

If you have an iPhone, you can try switch access right now, with the screen itself as the switch.

  • iPhone

    First, add Switch Control to the Accessibility Shortcut (Settings, Accessibility, Accessibility Shortcut), so a triple-click of the side button, or Home button on iPhone SE, turns it off. Then go to Settings, Accessibility, Switch Control, Switches, and tap Add New Switch. Choose Screen, then Full Screen, then Select Item. Turn on Switch Control and tap anywhere when the highlight reaches what you want. A menu opens; choose Tap.

  • No setup

    Use only Tab and Enter, and count the presses it takes to reach your main action, like "Add to cart" or "Book now." Each one is a wait for a switch user.

  • Look for

    Time limits, things that move on their own, gestures with no button, and anything that resets your place.

We're collecting stories from people who use assistive tech every day. Yours can help the people who build websites and apps see what gets in the way.

To know the road ahead, ask those coming back. We test with the same tools your users do.

No prep, no formal brief. A few sentences is plenty. Let us know what you're building and we'll take it from there. We typically respond within one business day.