Component States

An interactive control is a lifecycle, not a resting style. Map applicable states to semantics, visible treatment, and recovery.

Decision order and evidence

1. Name role, interaction model, owner, and applicable states.
2. Give each state ARIA/DOM mapping, visible non-color treatment, trigger, and recovery.
3. Test keyboard, focus-visible, contrast, reduced motion, and async completion.

Report one evidence row per state; n/a needs a subject-absence reason. Hand field validation to form-ux, emptiness to empty-states, and missing tokens back as gaps, never fallbacks.

Async/destructive controls

Name one semantic owner; visual states only present its lifecycle.