Design Core C · Industry convention

Interaction State

An Interaction State shows a control's current condition. Examples include default, hover, focus, pressed, disabled, loading, error, and success.

See how it works
You might call it UI statecomponent state

See how it works

Original worked exampleInteraction State

Another example

A submit button clearly shows when it's ready, working, done, or stopped by an error.

Main parts

  1. 01State signal
  2. 02Human-readable message
  3. 03Timing or progress
  4. 04Recovery path

Use it when

Plan every state when designing a component, not only its perfect still image.

Do not use it when

Never leave a control looking unchanged while work, failure, or success happens.

Name used in code

:hover / :focus-visible / aria-disabled

Before you ship

Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience.

Request you can copy

Outcome: Use or define Interaction State to make the visual experience clear and easy to use. User context: A submit button clearly shows when it's ready, working, done, or stopped by an error. Design concept to apply: Interaction State. Why it fits: Plan every state when designing a component, not only its perfect still image. Do not use it when: Never leave a control looking unchanged while work, failure, or success happens. Design requirements: Set the content order, shared design values, and reusable components. Define how the layout changes by screen size and state. Keep useful design choices separate from decoration. Inclusion and resilience: Check contrast, zoom, languages, themes, and reduced motion when needed. Do not use color or effects as the only way to show meaning. Acceptance criteria: The design stays clear on phones and desktops, at zoom, in every theme, and in all supported languages. Interactive states stay clear and consistent. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Brand limits, amount of content, supported themes and languages, target devices, and design-system rules.

Check this request

Review the current use of Interaction State. Definition: An Interaction State shows a control's current condition. Examples include default, hover, focus, pressed, disabled, loading, error, and success. Release checks: Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

C
How official is this term?

Industry convention

People often use this term at work. The listed sources may support practice or limitations. They do not define every part of the term.

No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks.

Scope
Interaction design
Document status
recommendation
Checked on
2026-07-30

Evidence sources & scope

Authority source · W3C · recommendation Accessible Rich Internet Applications (WAI-ARIA) 1.2 Scope: Web accessibility semantics Role here: Helpful background, not a definition Source covers: canonical name, definition, semantics, implementation Authority source · Google · stable Material Design Components Scope: Material component vocabulary Role here: Helpful background, not a definition Source covers: canonical name, definition, interaction, keyboard behavior, accessibility

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.