Design Principle
Users should not need to remember system state, previous-screen information, or hidden rules to complete a task.
Principle Users should not need to remember system state, previous-screen information, or hidden rules to complete a task.
Design action Each step explains current state, why a choice is needed, its consequence, and how to go back; keep a summary of prior choices.
Examples Positive example: Multi-step setup, AI generation, import flows, review flows, and permissions require multiple decisions. Counterexample: Steps lack summaries.
Apply when Multi-step setup, AI generation, import flows, review flows, and permissions require multiple decisions. Users need to judge state, scope, risk, or next action quickly.
Source notes Source note: Synthesized from W3C WCAG 2.2, Apple Accessibility, IBM Carbon Accessibility, and accessibility practices in major design systems.
Agent Directive
Each step explains current state, why a choice is needed, its consequence, and how to go back; keep a summary of prior choices.