Category: UI/UX
-
button state tokens: the three states nobody designs
—
by
in Accessibility, Buttons, Components, css, Educational, Sites, Styleguides, Tokens, UI KIt, UI/UX, WCAG, Web DesignA 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.
-
scrollbar tokens: the rail nobody designed
Every browser draws the scrollbar its own way, and none of those defaults were a decision anyone actually made. Chrome on Windows draws a scrollbar you can’t miss: wide, gray, square-edged. Firefox draws something thinner. Safari on macOS hides its scrollbar’s thumb until the cursor gets near the edge, and then it’s a faint blob…
-
the pipeline that posts itself: how m4d’s instagram content actually ships
Every post on @march4orthdesign is decided, built, and shipped by one file, and nobody opens it to check what’s next. Most content calendars are a decision someone has to keep making: what format today, what topic, who’s writing the caption. M4D replaced that decision with a state machine. `content/queue.md` holds the whole rotation — carousel,…
-
focus ring tokens: the accessibility feature people delete without meaning to
`outline: none;` is one line of CSS that quietly breaks keyboard navigation for every user tabbing through the page. Here’s how to token a real focus ring instead.
-
tabs tokens: the underline isn’t deciding anything on its own
Every tab bar in your product slides to a slightly different beat because nobody named the four decisions that actually control it. A settings page, a dashboard, an email client: three different surfaces, and in most codebases, three different opinions about how far apart the tab labels sit, how much padding wraps each one, how…
-
form input tokens: the four states nobody agreed on
Default and focus get styled. Error and disabled get invented on the spot, differently, every time. Here’s how to name and token all four input states.
-
skeleton tokens: name the wait, not just the shape
—
by
in Accessibility, Buttons, Components, css, Educational, Sites, Styleguides, Tokens, UI KIt, UI/UX, WCAG, Web DesignThe four seconds before content arrives are not a mystery state. They are a design decision waiting for tokens. Most design systems cover the loaded state in detail and leave the loading state to whatever the frontend framework ships by default, usually a spinner with no clock and no shape. Skeleton tokens close that gap…
-
empty states: the screen everyone forgets to design
—
by
in Accessibility, Buttons, Components, css, Educational, Sites, Styleguides, Tokens, UI KIt, UI/UX, WCAG, Web DesignThe loaded state gets a spec. The empty one gets whatever someone types at 2am before launch. Every product has a moment where a screen has nothing in it yet: a new account with no files, a search with no results, a dashboard before the first data point lands. Teams spend real time on the…
-
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…
