Under finger occlusion, pressed feedback must extend into a visible area
Aliases: finger occlusion · touch feedback · visible press feedback · touch occlusion
What it is
Touch occlusion-aware feedback ensures that evidence of a pressed state is not confined to pixels under a finger, but extends into an area the person can still see. During a tap, the target center, label, and subtle fill change may be covered by skin; feedback occurring only there is visually absent. An outer ring, change in an adjacent area, motion cue, lifted object preview, or paired haptic signal lets someone confirm which target was recognized before lifting their hand.
Why it happens
Touch separates the input point from usable vision: fingers are wider than cursors, and thumb or one-handed posture often covers a target from the side. People look at the visible edge around contact or the expected result, not the occluded center. When pressed feedback changes only a buried fill or fine text, confirmation comes after release and removes the chance to adjust or cancel while holding. Extending the cue beyond the occlusion boundary projects the input event back into available visual space.
Studying it
Record contact and display with varied device sizes, finger sizes, grips, thumb/index use, and screen edges. Observe visible portions of press feedback and whether people can identify the recognized target before release. Compare central fill, outer ring, adjacent-label change, layer, and haptic combinations for confirmation, cancellation, and repeated-tap behavior. Static screenshots are insufficient: occlusion depends on posture and movement. Also check that extension does not make a neighboring object appear selected.
Where it stops holding
Not every tap needs a large animation or layer. Excessive spread obscures more content, disrupts dense lists, and weakens object attribution. Large controls may already expose enough visible surface, while external pointers and mice do not require a finger-occlusion solution. Visual extension does not replace adequate hit areas, haptics, or semantic access; it solves visible evidence during contact, not every mistap.
Applying it
- Check each consequential touch control against real finger coverage; at least one target-bound cue must remain outside occlusion while pressed.
- For small targets, favor an outer outline, adjacent state label, visible drag proxy, or light haptic cue over center-only color change.
- Test thumb and index use separately in edge zones, bottom controls, and dense lists; do not let expanded feedback cross into ambiguous neighbors.
- Ask users to name the recognized target and try cancellation before release. Wrong answers, delayed confirmation after lift, and retapping indicate remaining occlusion.