Hover information needs another route on touch screens
Aliases: touch alternative · hover-only content · progressive disclosure · tooltip
What it is
A hover alternative is an equivalent, intentional route to information or an operation otherwise available only when a pointer passes over an element. Tooltips, row actions, previews, and hidden explanations do not naturally appear when a finger pauses. Long press can supplement a design but cannot be the sole substitute: it is hard to discover, slow, and may conflict with text selection, system menus, or dragging. Equivalence does not require copying a desktop animation; people must be able to obtain the same consequential content and complete the same task without guessing a secret gesture.
Why it happens
Hover creates a consequence-free “inspect, then decide” stage, while a touch tap usually activates a target directly. If information exists only in that stage, touch users must explore at the risk of triggering an action or never learn it exists. Fingers also occlude the target, making transient layers harder to read. An explicit details control, expandable row, context menu, or first-use cue restores exploration as a discoverable, reversible interaction rather than mechanically mapping mouse behavior to long press.
Studying it
Have pointer and touch participants perform equivalent understanding, comparison, and action tasks. Record discovery of supplementary information, accidental activation, time to reach it, and interpretation of the entry point. Test first use, one-handed holding, screen readers, zoom, and poor performance; emulator taps do not reveal occlusion or discovery cost. For long press, measure spontaneous use, understanding during its delay, and conflict with platform gestures.
Where it stops holding
Purely decorative previews need not gain an entry point everywhere. Information that changes choice, price, permission, risk, understanding of abbreviated content, or a subsequent action cannot be hover-only. Alternatives should not fill a page with identical “more” buttons; choose a persistent summary, on-demand expansion, or contextual entry according to importance. When desktop hover merely accelerates expert work, touch may use a different but acceptably efficient flow, but still cannot omit information required for understanding.
Applying it
- Inventory every hover-only label, preview, and command; mark whether it affects understanding or decision, then define touch, keyboard, and assistive-technology routes for consequential items.
- Make the touch route discoverable before its primary action, using visible details, expandable summaries, or named overflow—not an undocumented long press.
- Anchor potentially occluded layers where they remain visible, provide dismissal and return, and avoid treating a tap as both exploration and confirmation.
- Validate on first-use touch tasks: people should find the information without triggering consequences and explain how the route relates to its desktop hover counterpart.