Every action needs a perceivable response that says it was received and what it did.
Principle · Interaction
Tag
states
Entries tagged states, drawn from across the library. Tags cut through the section structure, which is where most of the useful connections are.
9 entries across 7 sections
Type
Category
Level
9 entries
Every interactive element needs a defined appearance for every state it can be in, and most designs specify only two.
UI foundation · Form and depth
Triggers an action. If it navigates somewhere, it should be a link instead.
Component · Actions
An immediate on or off setting, which must actually take effect immediately.
Component · Forms
The visible marker showing where keyboard focus is, which must never be removed.
Accessibility · Operable
A component is finished when its parts, its states and the reason each variant exists are all written down.
Design system · Components
Expanding a rough idea into a structured specification, which is mainly useful as a completeness check.
AI workflow · Definition
Every path through a task, including the error paths and the states most flows forget.
Template · Definition
A feature specification that covers states, edge cases and accessibility rather than only the happy path.
Template · Definition