Some gesture directions follow regional reading habits
Aliases: RTL swipe · mirrored back · reading direction
What it is
Directions for “next page, back, push the content away” rewrite with reading direction. In a right-to-left (RTL) UI, back often enters from the right edge, carousel “next” moves right, and a progress bar grows right to left. The map follows the writing system; worldwide left-swipe-back is not a law of physics.
Why it happens
Reading habits anchor forward/back on a horizontal axis: in LTR, left is already-read and right is unread; RTL reverses that. When layoutDirection is RTL, systems mirror navigation gestures so the motion matches the already-mirrored back chevron and stack animation. Without mirroring, a rightward hand sees the UI retreat left, motion fighting type. Vertical direction is less bound to reading, so pull-to-refresh rarely inverts by region. Mirroring applies to navigation and paging semantics, not to the radial geometry of a pinch.
Studying it
Run back, carousel, and stepper tasks under LTR and RTL system languages. Record preferred swipe direction and errors. Native reading direction should be a factor, not only the system language switch—the switch mirrors chrome, the native habit is the model. Measures include first-swipe direction and which edge people name as “forward.”
Where it stops holding
Vertical scripts and mixed bidi text (English nested in Arabic) make horizontal mirroring incomplete. East-west on a map is geography, not reading direction, and must not mirror. Game sticks and ink strokes do not follow locale. Some people run LTR apps on an RTL system, so gesture and chrome may each mirror once. Direction mapping is the layer of regional difference that should change; it is not a change to recognizer physics.
Applying it
- Mirror navigation and paging gestures with
layoutDirection; do not change pinch, long-press, or double-tap geometry by locale. - Mirror the back chevron, stack animation, and edge hotspot together, not the icon alone.
- On an Arabic or Hebrew system, walk back and “next”: gesture direction should match the arrow.
Related
- Same group: C3.34.2 Some hand motions can offend and should not be shipped worldwide as one · C3.34.3 Teaching images of hands need skin-tone and hand-shape representation · C3.34.4 Regional difference belongs in chrome and copy, not core gesture logic
- Adjacent: C3.14 Back gestures · C3.22 Scroll direction mapping
- Search:
RTL·layoutDirection·mirrored gesture