C3.14.3Visible fallback for back gesturedesignresearch

A back gesture must have a visible fallback entrance

Aliases: back button · close control · gesture fallback

What it is

A back gesture can be the fluent user’s main channel. It cannot be the only way off the current page. The screen needs a recognizable back or close: an arrow, an X, a system navigation bar. Gestures are fragile to discovery, motor ability, and system toggles; a visible entrance is the retreat when those frailties fire together.

Why it happens

An edge swipe leaves no residue. After a first use, a phone switch, or gesture navigation being turned off, people hunt for something tappable. When the system retired a virtual back key in favor of gestures, it still owed a shared visible cue (a home indicator) or an arrow that stayed in the nav bar. An app that also hides the nav-bar arrow, leaving only fullscreen content, withdraws the retreat as well. Assistive tech often cannot issue an app-level edge gesture; a visible control can appear in the accessibility tree. When the gesture is switched off by accident (child lock, demo mode, an external display), no button means being stuck on the detail.

Studying it

Three groups: people who have never used gesture navigation, people who just turned system gestures off, screen-reader users. The task is leaving a detail. Record the first entrance they find and the failure rate. Contrast “gesture only” with “gesture plus arrow.” Do not use engineers who edge-swipe back every day as the only participants.

Where it stops holding

A few pages of a system-wide gesture tutorial may be gesture-only; they are teaching the gesture itself. An immersive player can delay the arrow during playback, but a first touch or a downward drag should summon a visible exit. A modal’s close X is a kind of fallback; do not also stack an edge swipe that fights system back unless that swipe clearly closes the modal.

Applying it

  • Keep a visible back or close on every page that can be pushed on a stack. The gesture accelerates; it does not replace the button.
  • In fullscreen immersion, reveal close on first touch or a pull-down; do not assume everyone will swipe the edge.
  • Turn off gesture navigation in system settings and ask someone to leave your detail. They should be able to tap an arrow or an X. If they must turn gestures back on to leave, the fallback does not exist.

Related

  • Same group: C3.14.1 Back-gesture direction is bound to platform convention · C3.14.2 Back-stack semantics are not the same as “up one level”
  • Adjacent: C3.20 Gesture discoverability · C3.24 Accessible alternatives to gestures
  • Search: back button · gesture fallback · close affordance

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/C3.14.3