Mis-tapping between adjacent controls that look identical
Aliases: adjacent target confusion · fat finger problem · lookalike adjacent buttons
What it is
The most common concrete instance of a description-similarity error is a mis-tap between two or more controls that sit next to each other and look nearly identical — same icon, same size, same color. The user's internal description of the target was never more specific than "the button around that spot," and once two candidate controls both satisfy "around that spot," they become indistinguishable at the level of description; which one actually gets hit depends heavily on the precision of the finger or pointer's landing point rather than on the user's intent. What sets this case apart is that it stacks two sources of error at once — visual indistinguishability plus physical landing-point error — and the combination causes far more mis-taps than either source would on its own.
Why it happens
Whenever a finger touches a screen or a hand presses a physical key, the landing point carries some inherent physical error — a property of the motor system itself that "being more careful" cannot reduce to zero. When the gap between two controls is small enough for that error range to bridge the space between them, and the two controls look similar enough that visual anticipation before the touch can't rule either one out in advance, a landing point that falls on the wrong control gets executed by the system as a perfectly ordinary, deliberately-aimed input. The system has no way of telling whether that touch was a motor error or genuine intent — which is also why this kind of error rarely comes with any felt sense that something's off: from the hand's point of view, a mis-tap and a correct tap feel exactly the same.
Studying it
This problem is typically studied using the classic target-acquisition paradigm, systematically varying target size and spacing while measuring the distribution of landing-point offsets relative to the target's center, and tallying how often that offset falls into a neighboring control's area. This line of work has established a quantitative relationship between control size, spacing, and mis-tap rate, giving an empirical basis for deciding "how much spacing, how much size counts as safe" rather than guessing from intuition. Studies in this area also separate out error distributions across input methods — finger on a touchscreen, stylus, mouse pointer — because a finger's contact error range is noticeably larger than a pointer's, so the same spacing produces a different mis-tap rate depending on the input method in use.
Where it stops holding
This kind of error is most pronounced on touchscreens and other direct-contact input devices, because a fingertip's contact area is far larger than a precision pointing device's (mouse, stylus), giving it a wider error range; on interfaces driven mainly by mouse or stylus, the same control spacing produces a noticeably lower mis-tap rate. A user's dynamic state amplifies this error too — operating a phone while walking, or using a large touchscreen with one hand, reduces finger stability and widens the error range, so a spacing measured safe under static test conditions may not be safe enough in those real-use settings.
Applying it
For controls that sit adjacent to each other and look alike, check first whether their spacing is clearly larger than the typical magnitude of touch error — especially for pairs with asymmetric consequences, like "Cancel" sitting right next to "Confirm." Where spacing can't be widened enough on its own, add a difference in shape and wording as a supplement rather than asking spacing alone to carry the full burden of discrimination. Verification: have testers complete a batch of tasks requiring selection between adjacent controls under normal-use postures — including walking and one-handed use — and log which control pair each mis-tap involved along with the direction of the offset relative to the target's center. If offsets cluster in a particular direction, the spacing or mis-tap buffer in that direction needs to be widened specifically.
Related
- Same group: A10.04.1 selecting the wrong object because its description fails to distinguish similar candidates · A10.04.4 a destructive action sharing its shape with a routine one is a high-risk configuration
- Nearby: A8.09 the speed–accuracy trade-off
- Search terms:
fat finger problem·target spacing·touch accuracy
Cards in the same group
- A10.04.1Selecting the wrong object because its description fails to distinguish similar candidates
- A10.04.3Mis-selecting files, contacts, or options with near-identical names
- A10.04.4A destructive action sharing its shape with a routine one is a high-risk configuration
- A10.04.5Use position, shape, and wording together to widen discriminability
- A10.04.6A confirmation step must present the specific features that distinguish the object