An element that drills down on click needs to look clickable, or nobody will ever try

What it is

When chart elements—data points, legends, category labels—carry drill-down behavior (click to expand segments, jump to details), users need to judge "this is clickable" from appearance alone. This is affordance applied to data visualization. Unlike buttons and links, chart elements have no built-in visual convention for clickability: a clickable line looks exactly like a non-clickable one, and a bar's shape says nothing about whether it carries a behavior. Without a cue, a drill path that exists technically is, from the user's perspective, nonexistent.

Why it happens

Affordance works by visual expectation shaping behavior: users learn through millions of interactions that blue underlined text is clickable and raised buttons are pressable. Chart elements lack this convention, meaning designers must actively establish "what is clickable in this chart" through signals—common devices include: cursor changing to a pointer on hover (the bare minimum), data points enlarging or gaining a border on hover (marking them as discrete elements), color shifting to a link tone, and a hover tooltip reading "click to see breakdown by channel" (an explicit semantic invitation). Their effectiveness and cost both increase in that order. The problem is that a pointer cursor alone is insufficient: the user must first hover to discover clickability, but hovering itself presupposes expecting the element might be clickable—a chicken-and-egg loop. Breaking the loop requires placing the clickable signal where it is visible without hovering: visual styling (link color, border) or an explicit text label.

Where it stops holding

There is a ceiling on cue density: if every element on a chart gains a border or color, the clickability signal dilutes and users can no longer tell "this one is clickable" from "everything is clickable." Touch devices have no hover state—clickable visual cues must be always-visible rather than hover-revealed; many desktop-only designs fail on mobile for exactly this reason. Accessibility is another hard boundary: charts that signal clickability by color alone are unusable for color-vision-deficient users; clickable elements need a second, non-color signal (border, shape, text label).

Applying it

• Use one consistent visual signal (link color or dashed border) for all chart elements bound to drill behavior, and document that convention in the dashboard's usage notes.
• Write hover tooltips that state the click's effect ("click to see the regional breakdown"), not just the data value.
• Verification: ask 3 users who have never seen the dashboard, "which elements on this chart are clickable?" If no one identifies the drillable elements, the cues are insufficient.

Related

• Same group: U7.08.1 An anomaly found on the dashboard needs a next station toward explanation · U7.08.2 Jumping to a detail page must carry the current filter context · U7.08.3 The detail page must offer a way back that restores the dashboard's prior state · U7.08.4 A dashboard without drill-down paths can surface problems but not locate them
• Nearby: U7.08.1 An anomaly found on the dashboard needs a next station toward explanation · U7.04.5 Alerts must point to the executable next step, not just report the value
• Search terms: affordance · clickable chart · hover tooltip