Edward Tufte redrew the same bar chart three times in "The Visual Display of Quantitative Information" (1983), each version stripping out gridlines, drop shadows, and redundant labels, to make one point: most of the ink on a typical chart isn't showing data at all. He called the ratio of data-representing ink to total ink the data-ink ratio, and it's still the fastest diagnostic for a cluttered dashboard four decades later - delete anything that isn't the data, and see what's left.
The Data-Ink Ratio, in Practice
Tufte's test is mechanical: for every mark on a chart, ask whether removing it changes what a viewer can read from the data. Drop shadows on bars, 3D bevels on pie slices, background gridlines darker than the data itself, and duplicate labels all fail that test - Tufte's term for them collectively is chartjunk. A bar chart with a heavy border, a legend repeating what's already labeled on each bar, and a gradient fill can often lose all three and read faster, not slower.
The ratio isn't an argument for bare charts. Gridlines that help a viewer read a precise value, or a single reference line marking a target, earn their ink. The test is whether each mark serves comprehension or just decorates the chart.
Why the Brain Reads Some Charts Faster Than Others
Nielsen Norman Group's research on dashboard usability points to a specific mechanism: certain visual properties - length, 2D position, angle - are processed preattentively, meaning a viewer perceives them before consciously focusing, in under 250 milliseconds. Length and position are the most accurately judged of these properties; color hue and area are judged far less precisely. That's the underlying reason a bar chart usually beats a pie chart for comparing values: reading position along a shared axis is a near-instant, preattentive judgment, while comparing the area of two wedges is not.
- Comparing values: bar or column charts - length is precisely comparable.
- Showing a trend over time: line charts - position and slope read instantly.
- Showing part-to-whole with few categories: stacked bars generally outperform pie charts for anything beyond two or three slices.
- Showing distribution: histograms or box plots, not a single averaged number.
Color Is Not a Reliable Channel - WCAG Says So Explicitly
Two separate WCAG success criteria govern chart color, and both are testable, not aesthetic judgment calls. Success Criterion 1.4.11 (Non-text Contrast) requires a minimum 3:1 contrast ratio between adjacent graphical elements - two bars sitting next to each other in different colors need 3:1 contrast against each other, not just against the page background. Success Criterion 1.4.1 (Use of Color) requires that color never be the only channel carrying meaning: a red/green status indicator needs a second cue - an icon, a pattern, a label - because roughly 8% of men have some form of color vision deficiency and won't reliably distinguish red from green at a glance.
A newer contrast model, APCA (Accessible Perceptual Contrast Algorithm), is slated to replace the current WCAG 2.x contrast math in WCAG 3.0. It's built to be more accurate for the light-gray-on-white palettes common in modern dashboards, where the current ratio-based formula can flag genuinely readable text as failing, or pass genuinely unreadable combinations - worth tracking if a design system leans on subtle grays.
Designing for Dashboards Specifically
Nielsen Norman Group draws a line between two dashboard types that get designed the same way far too often: operational dashboards, built for fast, time-sensitive decisions on real-time data, and analytical dashboards, built for exploring historical data and finding patterns. An operational dashboard crowded with the drill-down filters an analytical one needs slows down the exact fast decision it exists to support.
Eye-tracking research from Nielsen Norman Group found users scan dashboards in an F-shaped pattern: a horizontal sweep across the top, a shorter sweep further down, then a vertical scan down the left edge. The practical consequence is blunt - whatever number matters most goes top-left, not centered, and not fourth in a row of five equally sized tiles.
A Working Checklist
- Pick the chart type from the comparison being made (value, trend, part-to-whole, distribution) - not from what looks most impressive.
- Remove every mark that doesn't change what a viewer reads from the data - Tufte's test, applied literally.
- Check adjacent chart-element contrast at 3:1, not just text contrast at 4.5:1.
- Never encode meaning in color alone - pair it with a shape, label, or pattern.
- Place the most important number where an F-pattern scan hits it first.
- Match dashboard type (operational vs. analytical) to what the viewer is actually trying to decide.
None of this requires new tooling. It requires being willing to delete the chart elements that exist because a template shipped with them, not because a viewer needs them.
