Minnesota publishes color accessibility guide for data visualization

Minnesota's state web team has published an article titled "Data visualization accessibility: Focus on color" on mn.gov, addressing how charts, maps, and dashboards can exclude users when hue carries the meaning.

The piece enters a long-running accessibility conversation. Roughly 8% of men and 0.5% of women of Northern European descent live with some form of inherited color vision deficiency, according to widely cited prevalence data; the rates shift across populations, but the underlying problem does not. A bar chart that sorts categories as red versus green reads as nothing to those viewers.

The regulatory floor is the Web Content Accessibility Guidelines. WCAG 2.2 Success Criterion 1.4.1 bars color as the only means of conveying information. Criterion 1.4.3 sets a 4.5:1 contrast ratio for body text against background, with 3:1 permitted for large text above 18 point regular or 14 point bold. Criterion 1.4.11 extends a 3:1 contrast floor to user interface components and graphical objects — the line that most directly governs chart strokes, fills, and legend swatches. A pie slice that differs from its neighbor only in hue fails 1.4.1 outright, regardless of how polished the palette looks.

Why does color keep breaking data viz?

Two reasons drive most failures. Designers borrow palettes from brand templates or default spreadsheet conditional formatting rather than accessibility-tested schemes. The classic red-yellow-green ramp reads as intuitive — red for decline, green for growth — but it collapses for someone with deuteranopia or in bright outdoor glare on a phone screen.

Automated scanners catch text contrast far better than chart contrast. The WebAIM Million 2024 scan of one million home pages found detectable WCAG 2 failures on 95.9% of audited sites, with low-contrast text appearing on roughly half. Charts, maps, and inline data graphics rarely get audited with the same rigor as headings and buttons, so problems compound quietly.

What does the Minnesota guide add?

The mn.gov piece joins a thin catalog of state-government accessibility guidance aimed at practitioners who build public dashboards and reports. Its focus on color specifically targets the most common failure mode in data work: relying on hue to do the work that labels, patterns, or direct annotation could do more reliably, and at lower cost.

Three practices follow from the WCAG criteria the topic invokes:

• Pair every color encoding with a redundant cue — a direct label, a pattern fill, a marker shape, or a distinct line style
• Test visualizations through color-blindness simulators covering protanopia, deuteranopia, and tritanopia before publishing
• Verify chart strokes, fills, and legend swatches meet the 1.4.11 3:1 contrast floor against their adjacent background, not just body text

State and federal digital teams now work against tightening timelines. The U.S. Department of Justice's April 2024 ADA Title II rule requires web content for state and local governments to meet WCAG 2.1 AA by April 24, 2026, for entities serving populations of 50,000 or more, and by April 26, 2027, for smaller jurisdictions. That two-stage deadline is the most plausible reason a state-government site would publish plain-language color guidance now, and why more agencies will likely follow before next year's audits begin in earnest.