The double-click interval must be adjustable

What it is

The double-click interval specifies how far apart two clicks may fall and still be read as one double click rather than two independent singles. It is a temporal grouping window for turning discrete actions into a compound gesture: too short, and an intended double click gets split into two singles; too long, and two genuinely separate clicks get merged, while single-click confirmation is also delayed because the system must wait out the window first. Windows and macOS both ship a default double-click speed on the order of a few hundred milliseconds — usually labelled "double-click speed" in system settings — and both let people adjust it.

Why it happens

After detecting a first click, the system opens a timing window and watches for a second click near the same object; a second click before the window closes counts as a double, otherwise the first click stands alone. Reaction speed, finger and wrist motor precision, button travel distance, and trackpad press style vary widely across people and devices, so a single fixed window cannot fit everyone by construction. Letting people adjust it hands the judgment of "how fast counts as continuous" back to individual tempo, but the adjustment itself reshuffles the balance between two error types — loosening it for slower movers also enlarges the chance of merging two genuinely separate clicks.

Studying it

Across different threshold values, record double-click success, false-merge rate (two intended singles read as one double), the felt wait after the first click, positional drift between the two clicks, and the distribution of settings people actually choose. The sample needs to cover practiced users, slower-moving users, and multiple devices — mouse, trackpad, an external mouse on a touch device — rather than defining a "universal" threshold from the average reaction time of young, able-bodied lab participants; that number is inherently person-dependent, and treating one sample's median as the standard would systematically exclude people at either tail of the tempo distribution.

Where it stops holding

Adjustability does not remove the underlying demand for two precise, consecutive endpoints — it only eases the time dimension, while the spatial dimension still requires both clicks to land near the same small target. When single and double click carry different nested meanings on the same object, lengthening the interval has a side effect: single-click confirmation is also pushed back, because the system must wait for the window to close before ruling out a double in progress. Mobile tap gestures and system-level gestures, such as two-finger actions or a platform back swipe, often follow entirely different rules from desktop and cannot simply inherit the desktop threshold.

Applying it

• Offer a discoverable double-click-speed setting paired with immediate, testable feedback — clicking twice should show whether the system judged it a success or a failure — rather than handing people an abstract millisecond number to guess at.
• Respect the operating system's double-click speed setting instead of quietly using a shorter window inside the application; doing otherwise makes the same person's double-click feel inconsistent across apps with no visible cause.
• Track miss rate, false-merge rate, and single-click response delay separately across candidate thresholds, and choose the default according to the task's actual error cost — reversibility and frequency — rather than intuition.

Related

• Same group: C1.07.2 Nested single and double semantics cause waiting delay · C1.07.3 Double clicking is a barrier for people with motor-control impairments · C1.07.4 Mobile functions should not rely only on double tap
• Nearby: C1.06 Hover states and their absence on touchscreens · J1 Motor and interaction accessibility
• Search terms: double-click interval · multi-click threshold · input timing