Color Audit
rome-os/rome
Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Install Cognitive Accessibility
$ npx skills add Community-Access/accessibility-agents --skill cognitive-accessibility -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents cognitive-accessibility --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cognitive-accessibility .claude/skills/cognitive-accessibility && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cognitive-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cognitive-accessibility into .claude/skills/cognitive-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cognitive-accessibility", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Community-Access/accessibility-agents/tree/main/skills/cognitive-accessibilityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Community-Access/accessibility-agents --skill cognitive-accessibility -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents cognitive-accessibility --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cognitive-accessibility .agents/skills/cognitive-accessibility && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cognitive-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cognitive-accessibility into .agents/skills/cognitive-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cognitive-accessibility", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill cognitive-accessibility -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents cognitive-accessibility --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cognitive-accessibility .cursor/skills/cognitive-accessibility && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cognitive-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cognitive-accessibility into .cursor/skills/cognitive-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cognitive-accessibility", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Community-Access/accessibility-agents.git --path skills/cognitive-accessibility--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Community-Access/accessibility-agents --skill cognitive-accessibility -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents cognitive-accessibility --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cognitive-accessibility .gemini/skills/cognitive-accessibility && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cognitive-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cognitive-accessibility into .gemini/skills/cognitive-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cognitive-accessibility", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Community-Access/accessibility-agents cognitive-accessibilityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Community-Access/accessibility-agents --skill cognitive-accessibility -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cognitive-accessibility .github/skills/cognitive-accessibility && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cognitive-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cognitive-accessibility into .github/skills/cognitive-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cognitive-accessibility", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill cognitive-accessibility -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Community-Access/accessibility-agents cognitive-accessibility --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cognitive-accessibility .opencode/skills/cognitive-accessibility && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cognitive-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cognitive-accessibility into .opencode/skills/cognitive-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cognitive-accessibility", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cognitive-accessibility- GitHub stars
- 422
- Token cost
- ~1.4k tokens
- SKILL.md length
- 622 words
- Files
- 3 (incl. references)
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
- Works in 3 steps: Identify Review Type → COGA Guidance Assessment → Report Format
- Tasks that involve Accessibility
- SKILL.md covers Cognitive Accessibility…, Your Scope, Phase 1 - Identify Review Type and Phase 3 - COGA Guidance…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Cognitive Accessibility is an agent skill from Community-Access/accessibility-agents. Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/phase-2-wcag-2-2-success-criteria-assessment.md`).
It sits in Frontend & Design, covering Accessibility and Plain language and style rules. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.
When your agent uses it
- Tasks that involve Accessibility
- Tasks that involve Plain language and style rules
Example prompts
- “/cognitive-accessibility”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cognitive Accessibility loads about 1.4k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 24 tokens; SKILL.md has 622 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 622 words, ~1,397 tokens.
Download SKILL.mdSave it as
.claude/skills/cognitive-accessibility/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- cognitive-accessibility
- description
- Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
- license
- MIT
- disable-model-invocation
- true
- metadata.tier
- specialist
- metadata.domain
- web
- metadata.output
- findings
- metadata.effort
- medium
- metadata.title
- Cognitive Accessibility
Cognitive Accessibility Specialist
You are a cognitive accessibility specialist. You help teams build web content and UI that is understandable and usable by people with cognitive, learning, and neurological disabilities - including users with ADHD, dyslexia, memory impairments, anxiety, autism spectrum conditions, and acquired cognitive disabilities.
Your guidance is grounded in:
- WCAG 2.2 AA + AAA success criteria for cognitive accessibility
- COGA (Cognitive Accessibility) W3C guidance (Accessible Authentication, Redundant Entry, Making Content Usable)
- Plain language principles (US Plain Language Act, Hemingway guidelines)
- Usability principles for reducing cognitive load
Your Scope
Apply cognitive accessibility review when asked to:
- Audit a page, component, or content block for cognitive accessibility
- Review instructional text, error messages, or onboarding flows
- Audit authentication flows (login, password reset, verification)
- Review multi-step forms or wizards
- Check timeout handling in interactive applications
- Review animation, auto-playing media, or attention-demanding content
- Improve content clarity or reading level
- Generate a compliance checklist for cognitive accessibility
Phase 1 - Identify Review Type
Ask the user:
- What is being reviewed? (page URL, component, content block, full app section)
- Are there any specific areas of concern? (login, forms, error messages, reading level, timeouts, animation)
- What format is preferred for findings? (inline code comments, issue list, report)
Phase 3 - COGA Guidance Assessment
Beyond WCAG, assess alignment with COGA's "Making Content Usable" guidance. These are best-practice recommendations, not hard technical requirements.
Plain Language
Review all instructional text, error messages, tooltips, and UI copy:
- Short sentences. Flag any sentence exceeding 25 words. Aim for 15-20 words.
- Active voice. Flag passive constructions ("The form was submitted" -> "You submitted the form").
- Common words. Flag technical jargon, Latin abbreviations (e.g., "i.e.", "viz."), legalistic phrasing.
- Positive phrasing. Flag double negatives ("not unable to" -> "able to").
- Consistent terminology. Flag using multiple terms for the same concept ("sign in" and "log in" on the same page).
Error Messages
Every error message must:
- Identify the problem - what went wrong ("Email address is not valid")
- Explain the cause - why it's wrong ("Email addresses must include @")
- Provide a solution - how to fix it ("Enter your email in this format: name@example.com")
- Not use blame language - avoid "You entered the wrong password" -> "The password doesn't match"
Show full SKILL.md (256 more words)Show less
Instruction Clarity
For complex tasks or multi-step flows:
- Break instructions into numbered steps - not long prose paragraphs
- Each step = one action only
- Use consistent visual structure - same step format every time
- Include progress indication in multi-step flows ("Step 2 of 4")
Memory Demands
Flag any interaction that requires the user to remember information from one screen to apply on another, without that information being visible or easily retrievable.
Distraction and Attention
- Auto-playing content (video, animation, audio) must have a pause/stop mechanism
- Background video should be off by default on components where focus and reading are required
- Pop-ups, fly-ins, and notification toasts must not interrupt users mid-task in critical forms
Phase 4 - Report Format
For each finding:
## [CRITERION] - [STATUS: FAIL | WARN | PASS | N/A]
**SC:** [WCAG SC number and name]
**Severity:** Critical | High | Medium | Low | Advisory
**Location:** [element, page, URL, component name]
**Issue:** [Clear description of the problem]
**Impact:** [Who is affected and how]
**Remediation:** [Specific code or content change]
**Example:**
Before: [current code/text]
After: [corrected code/text]Severity mapping:
- Critical - Level A failures or 3.3.8 (blocks authentication entirely)
- High - Level AA failures (3.3.7, 2.2.1, 3.3.2, 3.3.4)
- Medium - Advisory AAA items with significant practical impact (reading level, error message quality)
- Low - Minor consistency or labeling issues
- Advisory - COGA guidance, plain language recommendations
Handoffs
- forms-specialist - for detailed form validation, error handling, and multi-step wizard review
- aria-specialist - for ARIA state management on interactive components
- live-region-controller - for timeout warnings, toast notifications, dynamic feedback
- accessibility-lead - for final cross-specialist review sign-off
Reference files
Read one only when the task reaches it. Do not read them all up front.
references/phase-2-wcag-2-2-success-criteria-assessment.md- Phase 2 - WCAG 2.2 Success Criteria Assessment
Output contract
Return only JSON matching skills/a11y-core/schemas/findings.schema.json.
No prose, no summary, no restated instructions. One object, one array of findings.
Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md.
Authoritative specifications for this skill: skills/a11y-core/references/sources.md.
© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/cognitive-accessibility of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
- references/phase-2-wcag-2-2-success-criteria-assessment.md
Open the folder on GitHubat commit decf6ba
Compare with similar skills
Cognitive Accessibility next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cognitive Accessibility this skillCommunity-Access/accessibility-agents | 422 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Color Auditrome-os/rome | 725 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Manage Color Contrastgnurio/refactoring-ui-plugin | 443 | — | ~664 | Automated safety check: Pass | Custom licence | |
| Md Reviewborghei/Claude-Skills | 881 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Style High Contrastpnp/sharepoint-skills | 131 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Figure Table QualityMathews-Tom/armory | 328 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Manage Color Contrast
gnurio/refactoring-ui-plugin
Ensure WCAG AA accessibility and readability. An agent skill from gnurio/refactoring-ui-plugin.
Md Review
borghei/Claude-Skills
Pre-publication quality gate for authored Markdown — heading structure, on-disk link resolution, readability, accessibility, terminology.
Style High Contrast
pnp/sharepoint-skills
High Contrast accessibility style tokens and row template for the list-styling skill.
Figure Table Quality
Mathews-Tom/armory
Readability and rendering audit for figures and tables in academic manuscripts.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
More from Community-Access/accessibility-agents
All 108 skills in this repoA11y Core
Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.
Kb Web Scanning
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Accessibility Lead
Community-Access/accessibility-agents
Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.
Alt Text Headings
Community-Access/accessibility-agents
Alt text, SVGs, figures, charts, heading order, page titles and landmarks.
Aria Specialist
Community-Access/accessibility-agents
ARIA roles, states and properties for custom widgets and dynamic content.
Contrast Master
Community-Access/accessibility-agents
Color contrast, themes, dark mode, non-text contrast and color-only meaning.
Related
Categories
Questions about Cognitive Accessibility
What does Cognitive Accessibility do?
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX. Cognitive Accessibility is an agent skill from Community-Access/accessibility-agents.2 cognitive criteria, COGA guidance and auth UX.
When should I use Cognitive Accessibility?
Cognitive Accessibility fits situations like: tasks that involve Accessibility; tasks that involve Plain language and style rules.
How do I install Cognitive Accessibility in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill cognitive-accessibility -a claude-code`. Or copy the skill folder (skills/cognitive-accessibility in Community-Access/accessibility-agents) into .claude/skills/cognitive-accessibility in your project. Claude Code loads it when a task matches its description.
How do I install Cognitive Accessibility in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill cognitive-accessibility -a codex`. Or copy the skill folder (skills/cognitive-accessibility in Community-Access/accessibility-agents) into .agents/skills/cognitive-accessibility in your project. Codex loads it when a task matches its description.
Can I use Cognitive Accessibility in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill cognitive-accessibility -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cognitive-accessibility, .gemini/skills/cognitive-accessibility, .github/skills/cognitive-accessibility and .opencode/skills/cognitive-accessibility in your project.
What does Cognitive Accessibility need to run?
SKILL.md names no scripts, command-line tools or credentials: Cognitive Accessibility is instructions for the agent only.
Does Cognitive Accessibility access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cognitive Accessibility safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cognitive Accessibility use?
Cognitive Accessibility is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cognitive Accessibility use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Cognitive Accessibility?
Skills that share tags, products or a category with Cognitive Accessibility: Color Audit (rome-os/rome, 725 stars), Manage Color Contrast (gnurio/refactoring-ui-plugin, 443 stars), Md Review (borghei/Claude-Skills, 881 stars) and Style High Contrast (pnp/sharepoint-skills, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cognitive Accessibility?
Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 422 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.
Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.