how I use color theory: one accent, tokens, measured ratios

tech · 2026-10-13 · 6 min

most color theory posts are a color wheel and a promise. this site ships with a contrast checker in its own build, and the post is about the system that checker enforces: one accent, strict roles, measured ratios. no wheel required.

one accent, strict roles

everything structural is neutral. exactly one hue carries meaning: actions, links, focus, active states. when only one color ever means do something, users learn it in seconds. sites with five competing brights teach nothing except noise. the accent on this site is user-controlled (hue and saturation are settings), and the system holds contrast across all 360 hues by construction, not by hope.

tokens, not hex codes

no component on this site owns a color. every color resolves through tokens (surface, on-surface, primary, outline...), so dark mode, AMOLED mode and custom palettes work by changing a dozen values, not a thousand. a component inventing its own hex is a bug here, and the build fails on it. boring on purpose: consistency that depends on discipline always loses to consistency enforced by tooling.

ratios, not vibes

text pairs clear 4.5:1, large text 3:1, and the build checks the whole hue circle at maximum chroma on every commit. accessibility done by vibes regresses with the first redesign. accessibility done by tests persists through all of them. vibes are how sites end up with gray-on-gray body copy that the designer could read on their calibrated monitor and nobody else can read anywhere.

FAQ

how many colors should my website use?

neutrals plus one accent. add a second accent only when two meanings genuinely need separating (success vs danger, for example), never for decoration.

does dark mode double the work?

only without tokens. with tokens it is a second value set for the same roles. the work is in the roles, once.

for the checklist this system serves: website design checklist.