If the alternative takes much longer than the gesture, it is not a working alternative
Aliases: token alternative · equivalent time · gesture latency
What it is
If a swipe archives in one motion but the button path opens a menu, another level, then a confirm, the time gap turns the alternative into furniture. People who can still force a path will keep gambling on the gesture. People who cannot will drop the feature. An alternative has to live in the same time class at daily frequency, not merely be possible in theory.
Why it happens
High-frequency cost integrates over repetitions. A gesture is hundreds of milliseconds; an alternative of several seconds times every mail or photo is a tax nobody will pay all day. People pick the cheaper path. For someone with motor limits, the cheaper path is often the failing gesture, because one failure is still shorter than finishing the menu. The alternative exists in the spec and is not chosen in behaviour.
There is no universal multiplier for “much longer.” There is a task test: the stand-in must not turn a one-step act into a new navigation. Extra time spent re-orienting, waiting for motion, and reading a list is structure, not user ability.
Studying it
Have the same person complete a repeated set (twenty items) by gesture and by alternative. Log median time, errors, and mid-task switches. If the motor-limited group cannot gesture, time only the alternative and compare it with controls gesturing.
Independent variables: step count, whether the path leaves the current view, skippable animation and confirm. Dependent variables: median time ratio, abandon rate, strategy switches across repeats.
A single demo undercounts. A slow first find is discoverability. Still slow on the tenth trial is time structure.
Where it stops holding
A yearly export or a permissions change may be slower. Real-time control (volume, playhead, canvas zoom) a full order of magnitude slower is an unusable feature. The tax is harsher under switch scanning: every extra step is a whole scan. An alternative that is close in time but high in error (tiny buttons) is not a time problem; do not add steps to “buy safety.”
Applying it
- Keep high-frequency stand-ins on the current view: a toolbar button, an inline action—not Settings → Advanced → this item.
- For batch work, provide one alternative that covers many items (select all, then archive) instead of N deep menus to match N swipes.
- Verify: for a core task done ten-plus times, time gesture against alternative. If the alternative is routinely several times slower and people struggle back to the gesture, it does not hold in practice.
Related
- Same group: J3.11.1 A path-gesture alternative must be as findable as the gesture itself, not buried in a menu · J3.11.3 Precise-path gestures are nearly impossible under tremor or limited motor control · J3.11.4 The alternative must produce the same result, not a reduced approximation
- Nearby: J3.05 Single Pointer Alternatives · J3.06 Time Limits
- Search terms:
time-comparable alternative·pointer gesture·task time