Tactile delay is noticed more readily than visual delay, because touch is often bound to a self-generated action

What it is

Given the same length of delay, if it's attached to tactile feedback that appears right after a user's own tap or press, it's noticed as "sluggish" more readily than the same delay attached to a passively observed visual event. This isn't because touch as a sensory channel is inherently sharper than vision — the key is that tactile feedback is often tied to a self-initiated action, and it's this binding itself that amplifies sensitivity to delay.

Why it happens

When an action is self-initiated, the central nervous system generates an efference copy alongside the motor command it issues, carrying a precise prediction of the action's consequences — including when they should be perceived. The sensory feedback that actually arrives afterward is then compared against this prediction, and even a small mismatch between actual and predicted timing is caught by this comparator — one of the core mechanisms underlying the sense of agency. For a purely passively observed visual event unrelated to one's own action, there's no self-generated timing prediction to compare against, so detecting a delay relies only on the sensory system's comparatively coarse sense of absolute timing, and sensitivity is correspondingly much lower. Precisely because of this, this finding applies specifically to "tactile feedback that follows a self-initiated action" — if the tactile stimulus itself is passively received (say, a reminder buzz not triggered by any action), it no longer benefits from this extra sensitivity conferred by the efference copy.

Studying it

This effect is typically verified with input-latency detection threshold measurement: subjects perform a simple active action (a tap or press), the delay between the action and the ensuing feedback is systematically varied, and the smallest delay subjects can reliably notice as "slower" is measured — repeated and compared under tactile-feedback and visual-feedback conditions. Contrasting "actively triggered feedback" against "the same feedback delivered passively, unrelated to any action" also helps confirm that the boost in delay-detection sensitivity really comes from the action binding, not from the tactile channel itself.

Where it stops holding

This heightened sensitivity only holds when the tactile feedback immediately follows a self-initiated action: a purely passive reminder vibration with no clear triggering action doesn't get this extra boost, and its delay-detection sensitivity is closer to ordinary sensory delay detection. The specific magnitude of the sensitivity boost also varies with action type (a simple tap versus a complex gesture) and feedback form (a discrete single pulse versus continuous force feedback), so a single delay threshold shouldn't be applied across the board.

Applying it

• When budgeting latency for input devices — touchscreens, styluses, VR controllers — that need to give immediate tactile confirmation right after a user's active tap or press, target the stricter threshold for action-linked tactile delay, rather than the looser threshold that applies to visual delay or ordinary passive tactile alerts.
• How to verify: measure the end-to-end delay from finger/pen contact with the device to the tactile actuator actually beginning to respond, and confirm this measured delay falls within the range that's hard to notice using an input-latency detection test (varying the delay and asking users to report whether it feels "slow"). Don't use the delay standard appropriate for a passive reminder buzz to judge the acceptable delay for an active interaction's confirmation feedback.

Related

• Same group: A4.17.1 Touch resolves rapid pulse trains worse than hearing does, but better than visual flicker resolution · A4.17.2 A tolerance window exists between tactile feedback and visual/auditory events, beyond which they're perceived as out of sync · A4.17.4 Multiple simultaneous touch points delivered too close together in time fuse into a single perceived event instead of several
• Nearby: A4.14 Force and weight perception
• Search terms: input latency perception · efference copy · sense of agency · haptic click latency