cognitive-accessibility

Assess cognitive load in web and mobile interfaces and document intrinsic, extraneous, and germane load.

234|55|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designpowers --skill cognitive-accessibility-owl-listener
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cognitive-accessibility
Source: https://github.com/Owl-Listener/designpowers/tree/main/skills/cognitive-accessibility
Command: npx skills add https://github.com/Owl-Listener/designpowers --skill cognitive-accessibility-owl-listener

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The hardest accessibility barriers to see are cognitive ones. A screen reader user encounters a missing label and knows immediately. A person with a processing difference encounters an interface that demands too much of their working memory and just... leaves. This skill makes cognitive demands visible and manageable.

Core Features & Use Cases

  • Assess Cognitive Load — evaluate intrinsic, extraneous, and germane load for each screen or flow.
  • Reduce Extraneous Load — apply progressive disclosure, consistent patterns, clear defaults, and chunking to simplify interfaces.
  • Wayfinding & Focus Management — ensure clear location, accessible navigation, and interruption-safe flows.
  • Error Recovery & Documentation — support undo, forgiving formatting, and document cognitive considerations for each screen/flow.
  • Integration & Review — coordinate with related skills, align with cognitive considerations, and feed design reviews.
  • Quick Reference — maintain a concise cognitive-accessibility checklist for fast audits.

Quick Start

Run a cognitive-load assessment on the current UI flow and generate a prioritized list of simplifications.

Frequently Asked Questions about cognitive-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess cognitive load in a multi-step web or mobile app flow?

Assess cognitive load by documenting intrinsic, extraneous, and germane demands for each screen to improve usability for users under stress. This evaluation identifies where working memory is overtaxed in multi-step processes and navigation structures.

What is the best way to reduce extraneous load in interface design?

Reduce extraneous load by applying progressive disclosure, consistent patterns, clear defaults, and chunking to simplify interfaces. These techniques remove unnecessary processing demands, allowing users to focus on essential tasks without distraction.

How do I improve wayfinding and focus management for distracted users?

Improve wayfinding and focus management by ensuring clear location indicators, accessible navigation, and interruption-safe flows. These measures help users recover context and maintain orientation when time pressure or distraction is present.

Why does cognitive accessibility matter for users under time pressure?

Cognitive accessibility matters because high memory demands cause users under stress to abandon interfaces. Making cognitive demands visible and manageable prevents silent drop-offs that occur when working memory is overwhelmed.

How do I design error recovery for interfaces with high cognitive demands?

Design error recovery by supporting undo actions and forgiving formatting to reduce memory demands. Documenting cognitive considerations for each flow ensures users can easily correct mistakes without excessive mental effort.

Can I integrate cognitive load assessment into my existing design review process?

You can integrate cognitive load assessment into design reviews by maintaining a concise cognitive-accessibility checklist for fast audits. This feeds prioritized simplifications directly into your review cycle and coordinates with related skills.