A path-gesture alternative must be as findable as the gesture itself, not buried in a menu

What it is

Once a path gesture (swipe to archive, draw-to-invoke, drag along a rail to an endpoint) has a button or menu item, that stand-in must be as seeable and guessable as the gesture. Three levels down in overflow, shown once in a coach mark, or revealed only after the user can already perform the gesture, hides the feature from people who cannot follow the path. The question is not whether a second road exists. It is whether it can be found.

Why it happens

Path gestures are learned by doing. Swipe, the mail leaves, the action is remembered. Someone who cannot complete that trajectory never gets the lesson, so they also never store “archive exists.” Parking the alternative in an overflow menu makes discovery depend on already knowing the feature and knowing to search a menu—the exact prior that gesture teaching withheld.

Discoverability also means the alternative sits at the same decision point as the gesture. If the row can be swiped but the stand-in lives under Settings → Gestures, the spaces are different tasks. The person on that row wants to deal with this item, not leave the task to open a blind box.

Studying it

Recruit people who will not or cannot perform the gesture (including motor-limited users). Give only the goal (“archive this”), with no hint of the swipe and no hint of the menu. Record the first successful path, whether they asked “where is this,” and time to abandon.

Independent variables: inline visible button, toolbar, versus overflow depth. Dependent variables: unprompted discovery rate, time to find, rate of concluding the feature does not exist.

People who can gesture will under-detect the problem. They already have a fluent path and will not audit where the other one is hidden.

Where it stops holding

Expert, rare, destructive actions may live in a menu if the item is searchable and is not the only non-gesture way to finish a daily task. System AssistiveTouch or switch remapping does not excuse a missing in-app control; do not assume those settings are on. A gesture tutorial sheet is not a discoverable alternative: after it is dismissed, the path is gone.

Applying it

• Put a visible control on the same layer as the gesture: inline Archive, Rotate in the album—not only under “…” at the corner.
• If first-run guidance draws a finger trail, also point at the button. Do not teach the trail alone.
• Verify: disable the gesture and ask someone new to the product to complete the task the gesture used to do. If they cannot ask their way to a button, discoverability failed—even if a menu item exists.

Related

• Same group: J3.11.2 If the alternative takes much longer than the gesture, it is not a working alternative · 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.07 Drag Alternatives
• Search terms: gesture alternative discoverability · pointer gesture · hidden overflow menu