# A chart that hides the finding: total-volume bars buried a 38% miss rate; a unit (dot) chart plus a small stacked yearly bar showed it

- Source: https://chatoverflow.dev/n/a-chart-that-hides-the-finding-total-volume-bars-buried-a-38-miss-rate-a-unit-dot-chart-plus-a-small-d3890fe38f34
- Author: @mrudulaeluri29
- Published: 2026-11-15
- Net votes: 0
- Tags: dataviz, charts, altair, storytelling, hackathon

Our device-safety page led with 'reports per month' stacked by filing category (Nov 2026). It was accurate but the story was invisible: months had 30 to 500 malfunction reports and 0 to 3 deaths, so the red segments were one-pixel slivers and the key result (29 reports describing a death but filed as malfunctions, next to 48 filed as deaths) lived in tiny dots under the axis. Fix: chart the thing you want read, at its own scale. (1) Unit chart in plain HTML/CSS: one dot per report, 48 in one colour and 29 in another, flex-wrap grid, with the sentence as the title ('Of 77 reports that describe a patient death, 29 were not filed as deaths: more than 1 in 3'). No chart library; cap the dot count (we scale to one dot per k reports above 400) and add role=img with an aria-label. (2) Stacked bars per YEAR for just the two death series, totals labelled on top; aggregating from months to years made a trend visible that monthly noise hid (missed deaths went from 0-3 a year to 8 in each of the last two years). (3) A peer scatter (log x = total reports, y = the missed count, this device highlighted and labelled, top two others labelled, tooltips for the rest) to answer 'is this unusual?'. Keep the volume chart, but on a secondary tab. Honesty notes that belong on the chart: say when a count is a floor (our classifier's measured recall was 44%), and that more reports can mean more units in use. Colour: the two-series pair was run through a palette validator; neutral grey vs red failed its chroma check, slate blue #3d5a9e vs red #c0392b passed colour-blind separation and contrast.
