Path-based gestures need a non-path alternative

What it is

Swipe-to-delete, draw-to-unlock, lasso select, sign along a prescribed stroke — success is defined by the path itself, not by the landing point. Contact has to travel a specified trajectory; deviation fails the gesture. For someone who cannot produce a stable path, the function does not exist. The criterion: the same function must be completable in a non-path way — tap Delete, pick a menu item, tick a list.

Non-path does not mean “a nicer swipe”. It only requires activation at a point, not along a line. How hard the trajectory is, and how deeply the alternative is buried, are not unpacked here.

Why it happens

A path-based gesture turns the task from “activate on a target” into “copy a shape over time”. Tremor, spasm, a low-precision pointer, or the stepwise movement of switch hardware all distort the shape. Single-point activation does not ask for a shape: press and release can happen in the same hit area; the travel in between is not part of the command.

Products like paths because a path can name both direction and object at once (swipe this mail toward archive). The alternative has to split those: identify the object, then issue the command. Without that split path, the function stays locked to people who can draw the line. Dragging also contains a path, but dragging adds “hold and move the object”; the next leaf asks whether a click alternative exists. This leaf covers swipes, drawings and lassos whose purpose is not dragging an object.

Studying it

List every gesture that fires only if movement follows a direction or shape. For each, look for a second entry that does not depend on a trajectory. The judgement is existence: an explicit button, menu, checkbox or keyboard command passes; none fails. Do not compare step counts between the two paths at this stage.

Watch false alternatives: a “Cancel” that appears halfway through a swipe-to-delete still requires walking the path first. That is not a non-path entry.

Where it stops holding

In handwriting and drawing, the trajectory is the content, not a command — alternatives apply to commands such as Submit or Clear, not to the ink. If a system-level back gesture (swipe from edge) cannot be turned off, the app must still provide an explicit Back control on the interface. Games whose slash or sigil drawing is the core play can offer the alternative as optional assistance rather than deleting the path from the mode; settings, pause and exit must not hang only on a path.

Applying it

• Give swipe-to-delete, swipe-to-reply, draw-to-unlock and lasso select a tap entry: a button, a menu item or a checkbox.
• Do not count a button that appears mid-swipe as a non-path alternative; the entry must be usable before any trajectory is drawn.
• How to check: with swipes and drawing disabled, complete delete, archive and select-a-set by tapping only. A command that appears only after a trajectory has been drawn has no non-path alternative.

Related

• Same group: J3.05.1 Multipoint gestures need a single-pointer alternative · J3.05.3 Dragging needs a click alternative
• Nearby: J3.11 Path-based gesture alternatives · J3.13 Pointer cancellation · A8.16 Pathological and intentional tremor
• Search terms: path-based gesture · pointer gestures · non-path alternative