Accessible by Default

Accessibility is part of the composition, not a final layer of polish.

Reduce guesswork

Good focus states, meaningful labels, readable contrast, and predictable navigation give more people a clear path through the same experience.
They also make the interface easier for everyone to understand when attention is divided, the room is bright, the connection is slow, or the device is unfamiliar.

I think about accessibility as a series of invitations.
A visible focus state says, "you are here."
A useful label says, "this is what will happen."
A clear error message says, "you can recover from this."
Those details reduce guesswork, which is one of the most expensive forms of friction in an interface.

Keep the character

The work is rarely about choosing between a distinctive visual language and an accessible one.
It is usually about being more deliberate with the language: using contrast as structure, typography as hierarchy, and motion only when it helps someone understand a change.

Check the experience directly

The best implementation is often the one that feels invisible because it simply works.
I still check the details directly with a keyboard, a screen reader, and reduced-motion settings because assumptions are not a substitute for experiencing the interface differently.

The best implementation is often the one that feels invisible because it simply works.