Most arguments about accessibility are really arguments about defaults

Most arguments about accessibility are really arguments about defaults.

A component library offers forty ways to build a button. The team picks the one that looks right. Nobody checks the focus state, the contrast at small sizes, the screen-reader label — because the component didn't make them.

That's why we build highly opinionated components. Each one ships with exactly one right way to use it: focus indicators that can't be turned off, color pairs that pass contrast, labels the component requires rather than suggests. Flexibility is the enemy — every option is a chance to exclude someone.

This isn't a restriction on designers. It's the opposite. When the accessible choice is the default, designers stop spending energy on the basics and spend it on the experience.

Accessible procurement, accessible design systems, accessible teams — they're all the same idea: make the right thing the easy thing.

That's what we're striving for. One component at a time.