content-cognitive-accessibility-audit

Audits interface content and task flows for cognitive accessibility barriers.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/vmitsaras/Agent-Skills --skill content-cognitive-accessibility-audit-vmitsaras
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: content-cognitive-accessibility-audit
Source: https://github.com/vmitsaras/Agent-Skills/tree/main/skills/frontend-a11y/content-cognitive-accessibility-audit
Command: npx skills add https://github.com/vmitsaras/Agent-Skills --skill content-cognitive-accessibility-audit-vmitsaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interface content, forms, and multi-step flows often create hidden barriers for users involving comprehension, memory, attention, and executive function, and teams lack a structured way to find and classify these issues without conflating them with WCAG failures. ## Core Features & Use Cases - Cognitive Accessibility Audit: Reviews headings, instructions, terminology, predictable controls, memory burden, errors, timeouts, repeated entry, authentication, distractions, and help across pages, forms, and flows. - WCAG Boundary Discipline: Separates supported WCAG findings (with version, level, and rationale) from broader COGA-informed recommendations and items needing validation. - Structured Finding Contract: Produces findings with stable IDs, severity, confidence, evidence, user impact, recommendations, and verification steps. - Use Case: Given screenshots and source for a checkout flow, audit the error messages, session timeout behavior, and repeated data entry, then receive classified findings distinguishing WCAG 2.2 issues from plain-language improvements. ## Quick Start Use the content-cognitive-accessibility-audit skill to review this checkout flow's content and task steps for cognitive accessibility barriers.

Frequently Asked Questions about content-cognitive-accessibility-audit

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

FAQPage Schema
How do I audit a website for cognitive accessibility?▼

Walk each critical task from orientation through recovery, inspecting headings, instructions, terminology, memory burden, errors, timeouts, repeated entry, authentication, distractions, and help. Record evidence per finding and classify issues as applicable WCAG findings, broader recommendations, or items needing validation.

What is the difference between WCAG findings and COGA recommendations?▼

WCAG findings require evidence that a specific success criterion's normative conditions are met within the requested version and conformance level. COGA-informed guidance covers supplemental cognitive-accessibility improvements, such as plain language or reduced memory load, that do not map to a supported WCAG failure.

Can I audit cognitive accessibility from screenshots only?▼

Yes, but only for visible wording, hierarchy, terminology, controls, and distractions. Behavior-dependent aspects like timeouts, data persistence, repeated entry, authentication, and error recovery must be marked as not verifiable without a running interface.

Does this audit rewrite unclear content?▼

No. The audit is review-only and does not edit files or replace interface copy. If implementation is requested, any proposed rewrite is delivered as a separately labeled handoff, never presented as an applied fix.

Which WCAG criteria relate to cognitive accessibility?▼

Common WCAG 2.2 candidates include 3.3.7 redundant entry, 3.3.8 accessible authentication, 2.2.1 timing adjustable, 3.2.6 consistent help, and 3.1.3 through 3.1.5 for language complexity. Each mapping requires verifying the criterion's specific normative conditions and level.