cognitive-accessibility

Redesign task flows to reduce memory, attention, and error-recovery burdens for users.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill cognitive-accessibility-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cognitive-accessibility
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/cognitive-accessibility
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill cognitive-accessibility-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Digital task flows often force users to remember off-screen information, recover from interruptions, and reconstruct context after errors, creating avoidable cognitive burdens for people with cognitive and learning disabilities and for anyone working under distraction or fatigue. ## Core Features & Use Cases - Task-flow inspection: Identify critical paths, hidden state, orientation gaps, interruption sources, timeout risks, and error-recovery failures in multi-step flows. - Design decision rules: Externalize state, separate required from optional paths, preserve work across mistakes, limit interruptions, and handle timeouts transparently. - Verification trials: Run interruption/resume and error-recovery trials on rendered interactive artifacts instead of relying on static review. - Use Case: When redesigning a multi-step checkout or onboarding flow, use this Skill to find where users must remember prior choices, where optional upsells interrupt completion, and whether back/edit actions preserve entered data. ## Quick Start Review this multi-step onboarding flow for cognitive accessibility issues and recommend changes that reduce memory and interruption burdens.

Frequently Asked Questions about cognitive-accessibility

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

FAQPage Schema
How do I make a multi-step form more accessible for cognitive disabilities?

Map the critical path, externalize state like current step and prior selections, separate optional activities from required steps, and preserve entered data across back, edit, and validation errors. Then run interruption and error-recovery trials on the rendered flow.

What is cognitive accessibility in UX design?

Cognitive accessibility is the practice of reducing avoidable memory, attention, orientation, and error-recovery burdens in task flows. It draws on W3C COGA guidance, which supplements WCAG but is not itself a conformance requirement.

Is COGA guidance required for WCAG conformance?

No. W3C COGA Cognitive Accessibility Guidance is supplemental guidance for WCAG 2, not a conformance requirement. It informs design-time decisions about barriers that automated tools and criterion-only reviews often miss.

How should timeouts be handled for accessibility?

Avoid unnecessary timeouts, disclose required ones early, give users time to read warnings, and offer extension, save, or resume options. Preserve safely storable work after expiration rather than forcing re-entry.

When should I use cognitive accessibility review instead of an accessibility audit?

Use it at design time for task-flow issues like hidden state, interruption cost, and recovery burden that automated audits cannot detect. Use an accessibility audit for conformance checks like accessible names, contrast, keyboard, and semantics.