Glossary / Cognitive load
Cognitive load
Cognitive load is the mental effort required to understand information, remember context, make decisions, and complete a task. Accessible interfaces reduce avoidable complexity without removing necessary information or user choice. Clear language, consistent patterns, meaningful grouping, predictable behavior, visible progress, and forgiving recovery help people with cognitive and learning disabilities, situational stress, limited literacy, fatigue, and unfamiliarity with the product.
What to know
- Distinguish intrinsic complexity (inherent to the task) from avoidable complexity introduced by the interface. Simplify the latter while preserving decision-relevant information.
- Break long tasks into understandable steps; show progress and let users review or correct work. Do not surprise users with context changes or expiring data.
- Use plain language, descriptive headings, concrete labels, consistent terms, and examples. Avoid unexplained jargon, ambiguous icons, dense instructions, and double negatives.
- Reduce memory demands: keep instructions visible, preserve entered data, provide summaries, defaults that are safe, and contextual help.
- Consistency and predictability reduce relearning. Avoid changing control labels, location, or behavior across screens without a reason.
- Cognitive accessibility is not one checklist; needs vary. Support adjustable complexity and alternate formats where practical, and test with users.
- WCAG criteria overlap: labels, error prevention, timing, focus order, consistent help, and clear instructions all affect cognitive effort.
Engineering practice
Observe where users hesitate, repeat steps, abandon, or make recoverable mistakes. Use analytics as a signal, then validate with usability sessions and accessibility research. Design progressive disclosure carefully: hide secondary detail without hiding prerequisites. Make errors specific and recovery reversible. Avoid unnecessary time limits, autoplay, modal interruptions, and memory-based authentication challenges. Make help available consistently and ensure assistance does not remove user autonomy.
Interview questions
- How do you reduce cognitive load? Reduce unnecessary decisions and memory demands, use plain and consistent language, provide context/progress, and make recovery easy.
- What is progressive disclosure? Showing essential information first and revealing further detail when needed; it must not conceal information required for a decision.
- How do you know a flow is cognitively difficult? Combine observed user behavior, task completion/error data, and direct testing with diverse users.
- Why preserve entered data after an error? It reduces memory and re-entry burden and supports recovery.
- Can simplified UI harm accessibility? Yes, if it removes context, precision, user control, or meaningful choices; simplification should be validated with users.