accessibility-review
SkillDev toolsAudit a component or section for WCAG 2.1 AA accessibility issues and produce a structured fix plan. Use when the user asks for an accessibility review/audit of a component or section.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the accessibility-review skill
What this skill tells your AI
The instructions your AI receives, as published by ecomexperts-io/base in .claude/skills/accessibility-review/SKILL.md and read by ahel’s review.
Purpose: Audit a component or section for WCAG 2.1 AA accessibility issues and produce a structured fix plan.
Invocation: /accessibility-review <component-or-section-name>
Example: /accessibility-review component-filters-sidebar
Converted from the orphaned
.cursor/prompts/fix-accesibility-issue.mdprompt, which referenced a non-existentfetch_rulestool. This skill replaces those tool calls with direct reads.
Steps
- Read the target
.liquidfile and its corresponding.jsfile (if any). - Check against these categories. Instead of any
fetch_rulescall, read the relevant.claude/rules/*.mddirectly (the canonical source;.cursor/rules/*.mdcis generated from it) and read the component file to discover its existing ARIA patterns:- ARIA roles: the role must be on the element that directly contains the items; no role on wrapper divs above the semantic container.
- Keyboard navigation: all interactive elements reachable by Tab; custom elements handle
keydownfor Enter/Space/Escape where appropriate. - Focus management: focus is not lost on open/close of drawers, modals, dropdowns; use
focus()or theinertattribute. - Screen reader text: icon-only buttons must have an
aria-label; usearia-labelledbyto reference existing visible text rather than duplicating witharia-label. - Contrast: flag any hardcoded colors that may fail the 4.5:1 ratio; recommend
var(--color-*)tokens instead. - Motion: verify CSS animations respect
prefers-reduced-motion. - Alpine.js components:
x-datacomponents should have correctaria-expanded,aria-controls, andaria-selectedattributes reflecting Alpine state.
- Output a structured issue list: issue description, current code snippet, recommended fix, and the WCAG criterion.
- Do not auto-apply fixes — the developer reviews and approves.
Key differences from the original prompt
- Removes all
fetch_rulestool calls. - Removes references to
accordion-accessibility,carousel-accessibility, etc. as separate fetch targets — the relevant patterns are read directly from the component file and the relevant.mdcrule. - Adds Alpine.js-specific ARIA guidance (relevant given the many
x-datadeclarations in this codebase).
Signals
- GitHub stars
- 28
- Forks
- 18
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
accessibility-review-ecomexperts-io- Source
- github.com/ecomexperts-io/base