data-vizlisted

# Data Viz (honest, web-native, Tufte) Make web-native charts with honest marks: tokenized, responsive, accessible. Reuse type, spacing, surface, color tokens; one accent adds craft but never competes with data. Use Tufte tooling when present. ## Decision order 1. State comparison question, source/grain, missingness, and uncertainty. 2. Prefer a table for small exact lookup; chart shape, change, or comparison. 3. Encode honestly (zero-baseline bars; 1-D length/position; lie factor ≈1), direct-label, and remove non-data ink. 4. Provide tokenized, responsive, contrast-safe chart/table parity; keep data keyboard reachable. ## Data quality Before genre, record question, unit, time grain, source, and absent status. A missing month can mean **zero**, **not observed**, **suppressed**, **not applicable**, or **not yet reported**; these states cannot share a mark, line, or cell treatment. Name the uncertainty band (e.g. confidence interval, forecast range, or measurement error), level if known, and shared method. Missing values, units, provenance, or interval meaning means stop at a representation spec/data-request checklist. Never invent a trend, interpolate a gap, or manufacture an empty chart. For sparse monthly series, prefer an observed-month table or interval strip. If a line helps, break it at missing observations, plot estimated uncertainty only, label the gap, and never imply continuity with a continuous area. ## Genre selection | Data shape | Use | Not | |---|---