Agent skill

Accessibility Review

by markmead in markmead/hyperui

Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

MITAuto-check passedFrontend & Design

Install Accessibility Review

skills CLI
$ npx skills add markmead/hyperui --skill accessibility-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install markmead/hyperui accessibility-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/markmead/hyperui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/accessibility-review .claude/skills/accessibility-review && rm -rf skills-src

Use ~/.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/

Facts

Skill name
accessibility-review
GitHub stars
12k
Used in
1 other repo
Token cost
~1.1k tokens
SKILL.md length
291 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

  • Works in 8 steps: Insufficient color contrast → Missing form labels → No keyboard access to interactive elements → …
  • With audit accessibility
  • SKILL.md covers Usage, WCAG 2.1 AA Quick Reference, Common Issues and Testing Approach, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Accessibility Review is an agent skill from markmead/hyperui. Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Accessibility. It works with Tailwind CSS. The repository describes itself as: Free Tailwind CSS v4 components for your next project, designed to enhance your web development with the latest features and styles 🚀. The licence is MIT.

When your agent uses it

  • With audit accessibility
  • Is this accessible?
  • Reviewing a design for color contrast
  • Keyboard navigation

Example prompts

  • “audit accessibility”
  • “check a11y”
  • “is this accessible?”
  • “/accessibility-review”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Insufficient color contrast
  2. Missing form labels
  3. No keyboard access to interactive elements
  4. Missing alt text on meaningful images
  5. Focus traps in modals
  6. Missing ARIA landmarks
  7. Auto-playing media without controls
  8. Time limits without extension options

What it can do on your machine

Read from SKILL.md and the folder at commit 2b5aebb. 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 (its code samples are markdown).

    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

Accessibility Review loads about 1.1k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 291 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 markmead/hyperui at commit 2b5aebb, republished under its MIT licence (© markmead). 291 words, ~1,063 tokens.

Download SKILL.mdSave it as .claude/skills/accessibility-review/SKILL.md (or your agent's skills folder).
name
accessibility-review
description
Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.
argument-hint
<Figma URL, URL, or description>

/accessibility-review

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Audit a design or page for WCAG 2.1 AA accessibility compliance.

Usage

/accessibility-review $ARGUMENTS

Audit for accessibility: @$1

WCAG 2.1 AA Quick Reference

Perceivable
  • 1.1.1 Non-text content has alt text
  • 1.3.1 Info and structure conveyed semantically
  • 1.4.3 Contrast ratio >= 4.5:1 (normal text), >= 3:1 (large text)
  • 1.4.11 Non-text contrast >= 3:1 (UI components, graphics)
Operable
  • 2.1.1 All functionality available via keyboard
  • 2.4.3 Logical focus order
  • 2.4.7 Visible focus indicator
  • 2.5.5 Touch target >= 44x44 CSS pixels
Understandable
  • 3.2.1 Predictable on focus (no unexpected changes)
  • 3.3.1 Error identification (describe the error)
  • 3.3.2 Labels or instructions for inputs
Robust
  • 4.1.2 Name, role, value for all UI components

Common Issues

  1. Insufficient color contrast
  2. Missing form labels
  3. No keyboard access to interactive elements
  4. Missing alt text on meaningful images
  5. Focus traps in modals
  6. Missing ARIA landmarks
  7. Auto-playing media without controls
  8. Time limits without extension options

Testing Approach

  1. Automated scan (catches ~30% of issues)
  2. Keyboard-only navigation
  3. Screen reader testing (VoiceOver, NVDA)
  4. Color contrast verification
  5. Zoom to 200% — does layout break?

Output

markdown
## Accessibility Audit: [Design/Page Name]
**Standard:** WCAG 2.1 AA | **Date:** [Date]

### Summary
**Issues found:** [X] | **Critical:** [X] | **Major:** [X] | **Minor:** [X]

### Findings

#### Perceivable
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [1.4.3 Contrast] | 🔴 Critical | [Fix] |

#### Operable
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [2.1.1 Keyboard] | 🟡 Major | [Fix] |

#### Understandable
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [3.3.2 Labels] | 🟢 Minor | [Fix] |

#### Robust
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [4.1.2 Name, Role, Value] | 🟡 Major | [Fix] |

### Color Contrast Check
| Element | Foreground | Background | Ratio | Required | Pass? |
|---------|-----------|------------|-------|----------|-------|
| [Body text] | [color] | [color] | [X]:1 | 4.5:1 | ✅/❌ |

### Keyboard Navigation
| Element | Tab Order | Enter/Space | Escape | Arrow Keys |
|---------|-----------|-------------|--------|------------|
| [Element] | [Order] | [Behavior] | [Behavior] | [Behavior] |

### Screen Reader
| Element | Announced As | Issue |
|---------|-------------|-------|
| [Element] | [What SR says] | [Problem if any] |

### Priority Fixes
1. **[Critical fix]** — Affects [who] and blocks [what]
2. **[Major fix]** — Improves [what] for [who]
3. **[Minor fix]** — Nice to have

If Connectors Available

If ~~design tool is connected:

  • Inspect color values, font sizes, and touch targets directly from Figma
  • Check component ARIA roles and keyboard behavior in the design spec

If ~~project tracker is connected:

  • Create tickets for each accessibility finding with severity and WCAG criterion
  • Link findings to existing accessibility remediation epics

Tips

  1. Start with contrast and keyboard — These catch the most common and impactful issues.
  2. Test with real assistive technology — My audit is a great start, but manual testing with VoiceOver/NVDA catches things I can't.
  3. Prioritize by impact — Fix issues that block users first, polish later.

© markmead, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/accessibility-review of markmead/hyperui.

Open the folder on GitHubat commit 2b5aebb

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in markmead/hyperui, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Accessibility Review 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.

Accessibility Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Accessibility Review this skillmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Baseline UIibelick/ui-skills9.6k8 repos~855Automated safety check: PassMIT
UI/UX Design System AdvisorGalaxy-Dawn/claude-scholar5.7k1 repos~1.1kAutomated safety check: PassMIT
Extract DesignManavarya09/design-extract4.2k—~786Automated safety check: NotesMIT
Better Colorstrycompai/crm11k—~1.9kAutomated safety check: PassMIT
Accessibility ReviewThibautBaissac/rails_ai_agents665—~2.9kAutomated safety check: NotesMIT

Similar skills

  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.6k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed
  • UI/UX Design System Advisor

    Galaxy-Dawn/claude-scholar

    Turns a vague UI request into a concrete design system with style, palette, typography and layout guidance from a search script, plus stack-specific implementation advice.

    5.7k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Extract Design

    Manavarya09/design-extract

    Extract the full design language from any website URL. An agent skill from Manavarya09/design-extract.

    4.2k GitHub stars~786 tokensUpdated yesterday
    Frontend & DesignAuto-check: notes
  • Better Colors

    trycompai/crm

    OKLCH color space and color usage for web projects. An agent skill from trycompai/crm.

    11k GitHub stars~1.9k tokensUpdated 29 days ago
    Frontend & DesignAuto-check passed
  • Accessibility Review

    ThibautBaissac/rails_ai_agents

    Audits Rails application accessibility against WCAG 2.2 Level AA, detects violations with axe-core / Lighthouse / Pa11y, and reports remediation guidance for ERB views, ViewComponents, Stimulus…

    665 GitHub stars~2.9k tokensUpdated 4 mo ago
    Frontend & DesignAuto-check: notes
  • Vrt

    marigold-ui/marigold

    DST — Trigger the Visual-Regression-Tests (Chromatic) GitHub Actions workflow on the current or a given branch.

    146 GitHub stars~787 tokensUpdated today
    Frontend & DesignAuto-check passed

Works with

Questions about Accessibility Review

What does Accessibility Review do?

Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui. Accessibility Review is an agent skill from markmead/hyperui.1 AA accessibility audit on a design or page.

When should I use Accessibility Review?

Accessibility Review fits situations like: with audit accessibility; is this accessible?; reviewing a design for color contrast; keyboard navigation.

How do I install Accessibility Review in Claude Code?

Run `npx skills add markmead/hyperui --skill accessibility-review -a claude-code`. Or copy the skill folder (.agents/skills/accessibility-review in markmead/hyperui) into .claude/skills/accessibility-review in your project. Claude Code loads it when a task matches its description.

How do I install Accessibility Review in Codex?

Run `npx skills add markmead/hyperui --skill accessibility-review -a codex`. Or copy the skill folder (.agents/skills/accessibility-review in markmead/hyperui) into .agents/skills/accessibility-review in your project. Codex loads it when a task matches its description.

Can I use Accessibility Review 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 markmead/hyperui --skill accessibility-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/accessibility-review, .gemini/skills/accessibility-review, .github/skills/accessibility-review and .opencode/skills/accessibility-review in your project.

What does Accessibility Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Accessibility Review is instructions for the agent only.

Does Accessibility Review 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 Accessibility Review 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 Accessibility Review use?

Accessibility Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Accessibility Review use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Accessibility Review?

Skills that share tags, products or a category with Accessibility Review: Baseline UI (ibelick/ui-skills, 9.6k stars), UI/UX Design System Advisor (Galaxy-Dawn/claude-scholar, 5.7k stars), Extract Design (Manavarya09/design-extract, 4.2k stars) and Better Colors (trycompai/crm, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Accessibility Review?

markmead (a GitHub user) maintains it in markmead/hyperui, which has 12,254 GitHub stars. The repository was last updated on September 26, 2026.

Source: markmead/hyperui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.