Category: Tokens
-
how to bake wcag aa into your token file from day one
Contrast ratios, touch targets, focus rings, semantic pairing — here’s exactly what to write in your token file to bake WCAG AA in from day one.
-
density tokens: the row height nobody agreed on
—
by
in Accessibility, Buttons, Components, css, Educational, Sites, Styleguides, Tokens, UI KIt, UI/UX, WCAG, Web DesignEvery screen ends up with its own row height, because nobody wrote down when to use which one. Dashboards, settings pages, and email templates all render the same kind of row, but each one usually gets a hand-picked pixel value: 36px here, 51px there, whatever looked right in the moment. Density tokens fix this by…
-
border radius tokens: rounding corners on purpose instead of by accident
4px on the input, 6px on the card, 12px on the modal — nobody decided the modal should be softer. Here’s how to name four radius steps on purpose.
-
fluid type scale: the clamp() token that ends breakpoint math
—
by
in Accessibility, Buttons, Components, css, Educational, Sites, Styleguides, Tokens, UI KIt, UI/UX, WCAG, Web DesignA type scale hardcoded to four breakpoints is four separate guesses about how big text should be, not one decision. Most font-size tokens still live inside media queries: 28px on mobile, 34px at 640px, 40px at 768px, 48px at 1024px, each value picked by eye and none of them connected to the others. The gaps…
-
data visualization tokens: the chart color category most systems skip
—
by
in Accessibility, Buttons, Components, css, Educational, Sites, Styleguides, Tokens, UI KIt, UI/UX, WCAG, Web DesignSix chart colors, chosen by six different people, is not a palette – it’s six separate guesses that happen to render next to each other. Most design systems name every color except the ones inside a chart. Marketing’s dashboard uses orange for churn risk, support’s uses red, and nobody decided that on purpose – each…
-
breakpoint tokens: naming the width so nobody has to guess it
767px or 768px? Every developer picks their own tablet breakpoint. Here’s how naming four fixed boundaries once ends the guessing for good.
-
button state tokens: the three states nobody designs
A button has five real states, not two. Default and hover get designed; active, disabled, and loading get left to accident. Here’s how to name and token all five.
-
dark mode tokens: why inverting your palette doesn’t work
Flip every hex value for dark mode and the depth disappears — a card that read as “elevated” in light mode goes flat, because that depth was never really in the color. The instinct to treat dark mode as an inversion makes sense on the surface: light backgrounds become dark, dark text becomes light, done.…
-
-
