Break markers are often too small to notice, equal to unmarked

What it is

A broken axis stakes all its safety on one visual token: the wavy line or double slash whose job is to say "a stretch is missing here." That token is usually too small to notice — a few millimetres of squiggle tucked at the axis end, competing for attention against the page's other furniture (gridlines, borders, watermarks). An unnoticed annotation equals a nonexistent one in effect: readers finish the chart under the "uniform axis" assumption, and the previous leaf's distance and slope distortions collect in full. The standard for a break is therefore not "a marker was drawn" but "the marker was seen."

Why it happens

The wavy token is a signal diluted by convention: it is not in readers' natural visual vocabulary (unlike arrows or colours, it carries no innate meaning) and works only on trained readers — and even they search for it only when actively auditing the axis; the glance-and-read habit bypasses it entirely. Attention allocation settles it: first-pass fixations land almost entirely on data elements, and a tiny end-of-axis token is one grain of noise in low-resolution peripheral vision. The result is a mismatch of responsibility: the chart-maker believes "marked means absolved," the reader never received the message, and the distortion proceeds on schedule.

Where it stops holding

Enlarging the marker helps partly without curing: it raises the probability of notice yet still conveys neither the gap's size nor the conversion difference between sides (the mark's drawn width corresponds to no value). What truly communicates a break is text: "axis interrupted at X–Y, scales differ on the two sides" in the caption or beside the axis — and text helps only if read, so it suits reports that get close reading; in mass communication even this is unreliable, leaving "don't use breaks" (fifth leaf). Interactive settings can prompt "crossing a break" on hover — annotation made dynamic.

Applying it

• Marker specification: break marks at least several times the data stroke height, placed directly over the data line to obstruct it (an unavoidable visual event), plus a textual note.
• Review shifts from "marked" to "measured": spot-check with inattentive viewing (a three-second scan); readers who cannot recall the break's position count as unmarked.
• Verification: test three marker sizes (decorative / conventional / exaggerated plus text) and count readers detecting the break; take the smallest tier passing half-awareness as the specification floor.

Related

• Same group: U3.02.1 A broken axis removes a value interval from the middle of the scale · U3.02.2 Across the break, equal distances no longer mean equal values · U3.02.4 Length encodings crossing the break lose all comparability · U3.02.5 Facets or log scales usually replace the broken axis
• Nearby: U3.03.3 The scale type must be prominently labelled · U1.14.1 Non-data elements consume attention while carrying no information
• Search terms: axis break marker · annotation visibility · noticed vs marked · chart decoration