← ClaudeAtlas

cognitive-accessibilitylisted

Evaluate a website, app, screenshot, or Figma design for cognitive accessibility using 9 research-based heuristics for neurodivergent and cognitively diverse users (sensory load, plain language, guidance, progressive disclosure, customization, cohesion, consistency, error tolerance, focus management). Returns short, scannable findings with fixes tiered quick / structural / foundational. Use when asked to audit, review, or improve a digital product for cognitive accessibility, neurodivergent users, autistic users, neuroinclusive design, cognitive load, sensory overload, or when a WCAG-style review needs to cover cognition rather than only perception and motor access.
amachador/cognitive-accessibility-skill · ★ 1 · Web & Frontend · score 71
Install: claude install-skill amachador/cognitive-accessibility-skill
# Cognitive Accessibility 9 heuristics for **neurodivergent people and anyone whose processing differs**. They cover what WCAG and Nielsen miss: **focus, memory, learning, decision-making, communication, masking**. Formulated from research with autistic adults of working age (Alejandro Machado R., 2025). | | Heuristic | Do this | |---|---|---| | **H1** | Purposeful sensory stimulus | Let people regulate how much stimulus they get. | | **H2** | Clarity and straightforwardness | Explicit, direct language. No metaphor, no manipulation. | | **H3** | Assistance | Show the steps and what each one produces. | | **H4** | Progressive discovery | Information in parts. Gradual change. | | **H5** | Control and customization | Let people reshape how information is processed. | | **H6** | Cohesion | Logical hierarchy, familiar names, minimal fragmentation. | | **H7** | Consistency and standards | Use the patterns other products already taught them. | | **H8** | Resilience and error tolerance | Errors fast to understand, easy to recover from. | | **H9** | Focus management | Support concentration, hyperfocus, and time. | ## 1. Context Ask once, in one short message, then proceed: > Who is the user (familiarity, and any traits that matter — sensitive to motion, reads > literally, prone to hyperfocus)? And what specific task are they finishing? No answer → state the assumption in the report header and continue. Never block. ## 2. Depth — decide it yourself | Input | Format | |---|---|