frameworkExperience & interface

Interaction Patterns

Interaction patterns are reusable arrangements of controls, behavior, feedback, and user expectations for recurring interface problems in a defined context.

Download Markdown (.md)

01What it means

An interaction pattern describes a recurring problem and a tested way to handle it, including structure, states, keyboard behavior, feedback, and constraints. Examples include disclosure, autocomplete, tabs, and multi-step forms. A pattern is more than a visual component: it explains when the behavior fits and what must remain true across implementations.[1][2][3]

02Why it matters

Consistent patterns reduce relearning, concentrate accessibility and engineering effort, and give teams a shared language for discussing behavior. They also preserve lessons about edge cases that mockups often omit. Used thoughtfully, patterns accelerate delivery while allowing products to adapt content and presentation to their own context.

03When to use it

Start with an established pattern when the user problem is common and the expected behavior is understood. Evaluate its suitability against task frequency, content, device, input method, and accessibility needs. Create or extend a pattern when existing choices cannot support the context—not merely to make the interface look novel.

04How it works

  1. Describe the recurring user problem, context, forces, and signals that indicate the pattern is appropriate.
  2. Specify anatomy, states, transitions, input behavior, feedback, content rules, and accessible name and focus requirements.
  3. Prototype the pattern with realistic content, edge cases, and alternative input methods.
  4. Validate comprehension and task behavior, then implement through shared components where repetition justifies it.
  5. Document evidence, known limitations, variants, and conditions for avoiding or revisiting the pattern.

05A practical example

Example

A design system team standardizes an autocomplete pattern for address search. The specification covers loading and no-result states, free-text fallback, keyboard navigation, announced result counts, mobile behavior, and what happens after selection. Teams may style the field for their service, but they preserve the behavioral contract and test with their own address data.

06Where it breaks

A familiar pattern can still be wrong for a specialized task, culture, language, or assistive technology. Pattern libraries may freeze old assumptions or hide weak evidence behind consistency. Combining individually sound patterns can also create a poor journey. Teams should test the whole task and maintain patterns as standards and platform behavior evolve.

Common mistakes

  • Treating a screenshot or component inventory as a complete interaction pattern.
  • Copying a pattern without its keyboard, focus, error, and feedback behavior.
  • Choosing novelty or internal consistency over the expectations and constraints of the task.

07Sources

  1. ARIA Authoring Practices GuideW3C Web Accessibility Initiative · Standards guidanceARIA Authoring Practices Guide
  2. ComponentsGOV.UK Design System · Government design-system guidanceComponents
  3. PatternsGOV.UK Design System · Government design-system guidancePatterns
View saved topics

Start typing to search titles, definitions, categories, and frameworks.