Best use case
accessibility is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Accessibility audit for WCAG compliance and usability
Teams using accessibility should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/accessibility/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/.claude/skills/accessibility/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/accessibility/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How accessibility Compares
| Feature / Agent | accessibility | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Accessibility audit for WCAG compliance and usability
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Audit accessibility for: $ARGUMENTS If no arguments, audit the entire frontend codebase. Steps: 1. Check semantic HTML usage (headings, landmarks, labels) 2. Verify ARIA attributes are correct and complete 3. Test keyboard navigation flow 4. Check color contrast ratios meet WCAG 2.1 AA 5. Report violations with severity and remediation steps
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.