A clickable data point has to be big enough for a fingertip, not merely big enough to see

What it is

Clickable or tappable chart elements (data points, legend items, drill entries) have a size floor beyond "visible"—they must be "touchable": a fingertip contacts roughly 7-9 mm of screen, and mainstream platform specs (Apple HIG 44pt, Material 48dp, WCAG 2.5.8 minimum 24px) all set floors for interactive targets. A 4-px dot in a scatter plot or a 2-px hit line under a thin trend is nearly impossible to hit accurately on touch screens, and motor-impaired users' error rates amplify the problem. Visual size and hit size are two independent engineering quantities, and interactive marks must satisfy both.

Why it happens

The touch-target mechanism rests on the accuracy distribution of finger input: the fingertip's contact area exceeds most data marks, and the probability of the touch landing inside the target changes steeply with target size—too small, and success depends on landing luck rather than intent. The standard engineering solution decouples hit area from visual area: the visible part keeps its design size (the 4-px dot still renders 4 px, preserving visual density) while a transparent extended hit zone (20-24 px square) is attached; touching the zone equals touching the mark. Hit zones of dense marks overlap, and the hit-testing policy then decides the experience: nearest-mark snapping (the touch gravitates to the nearest point) beats coverage-based testing (whoever is covered wins), optionally with a magnifier or a selection mode (enter selection state, then tap). The keyboard equivalent (the same group's keyboard traversal) complements touch targets: hit areas solve "can be touched," keyboard traversal solves "can be reached," and together they span the motor-ability spectrum.

Where it stops holding

Hit-area floors tension against mark density: expanding every scatter point to a 24-px zone in a dense chart means massive overlap; the remedy is not shrinking zones but layered interaction (zoom to sparsify, box-select aggregation, nearest-neighbor snapping). Minimum-size specs differ (44pt / 48dp / 24px) because platforms trade off mistouch tolerance differently; cross-platform products should adopt the strictest applicable value. Enlarged hit areas have a negative boundary too: oversized zones "steal" touches from neighboring marks or background interactions (legend items whose zones cover the plot), so expansion requires regression testing against adjacent interactive elements.

Applying it

• Give every interactive mark a hit area of at least 24px (44px/48dp preferred on mobile), configuring visual size and hit size independently.
• Use nearest-neighbor hit testing on dense marks, with zoom or box-select as alternative selection paths in high-density regions.
• Regression-test after hit-area expansion: confirm no occlusion of neighboring marks' hits or other page interactions.
• Verification: on a touch device, have 5 users (including one with a motor impairment) tap specified data points and record first-tap success; below 80% means target size is insufficient.

Related

• Same group: U11.04.1 Chart marks need discernible contrast against the background · U11.04.2 Mark-vs-background contrast and adjacent-category contrast are two independent requirements · U11.04.3 Too-thin lines vanish on low-contrast screens and projectors · U11.04.4 In-chart text minimum size is judged by final rendered size, not the design file
• Nearby: U11.01.3 Interactive charts must support keyboard traversal · U7.08.5 Drillable elements need a clickable visual cue
• Search terms: touch target · hit area · pointer target size