cognitive

Implement plain language, dyslexia-friendly typography, and reduced motion in web interfaces.

Updated Aug 23, 2026

Search Tags:#accessibility #wcag #cognitive #plain language #reduced motion #dyslexia

Ready to run

npx skills add https://github.com/lukeslp/accessibility-skills --skill cognitive

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cognitive
Source: https://github.com/lukeslp/accessibility-skills/tree/main/plugins/accessibility/skills/cognitive
Command: npx skills add https://github.com/lukeslp/accessibility-skills --skill cognitive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses cognitive and communication barriers in digital interfaces, ensuring that users with diverse needs can understand and interact with content effectively.

Core Features & Use Cases

Plain Language & Readability: Simplifies complex text and offers dyslexia-friendly typography options.
Reduced Motion: Respects user preferences to disable animations, preventing discomfort.
Predictable Interactions: Ensures consistent navigation and clear error handling.
Use Case: A user with dyslexia struggles with a complex online form. Applying the dyslexia-friendly styles and ensuring clear, plain language instructions makes the form accessible and easy to complete.

Quick Start

Apply dyslexia-friendly text styles and ensure reduced motion is respected for the current page.

Frequently Asked Questions about cognitive

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

FAQPage Schema

How do I make web content understandable for users with dyslexia?▼

To make web content understandable for dyslexia, apply dyslexia-friendly typography options and simplify complex text into plain language. This improves readability and ensures users can effectively process and interact with your interface content.

What are WCAG 2.2 AA requirements for cognitive accessibility?▼

WCAG 2.2 AA requirements for cognitive accessibility mandate plain language, predictable interactions, and consistent navigation. These guidelines ensure digital interfaces provide understandable content and clear error handling for users with diverse cognitive needs.

How do I implement reduced motion preferences to prevent user discomfort?▼

To implement reduced motion preferences, configure your web interface to detect and respect user settings that disable animations. This prevents discomfort for users sensitive to motion while maintaining core interface functionality.

Can I use plain language guidelines to simplify complex online forms?▼

Yes, you can use plain language guidelines to simplify complex online forms by applying clear instructions and dyslexia-friendly text styles. This makes forms accessible and easy for users with cognitive barriers to complete.

Does cognitive accessibility support AAC integration and captions?▼

Cognitive accessibility supports AAC integration and captions to address communication barriers in digital interfaces. This ensures users with diverse communication needs can understand and interact with content effectively across web platforms.

What is the best way to ensure predictable interactions in web interfaces?▼

The best way to ensure predictable interactions in web interfaces is to implement consistent navigation and clear error handling. This approach addresses cognitive accessibility by making interactions understandable and reliable for all users.