a11y_check
Check for accessibility compliance (WCAG).
Best use case
a11y_check is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Check for accessibility compliance (WCAG).
Teams using a11y_check 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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/a11y_check/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How a11y_check Compares
| Feature / Agent | a11y_check | 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?
Check for accessibility compliance (WCAG).
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
# A11y Check Skill Accessibility audit and compliance verification. ## When to Activate This skill is relevant when: - Auditing accessibility compliance - Reviewing UI components - Checking WCAG compliance - Ensuring inclusive design - Pre-release accessibility check - Responding to accessibility issues ## Core Principles ### Universal Access - The web is for everyone - No user left behind - Design inclusively - Remove barriers - Enable all users ### Standards - WCAG 2.1 AA is minimum - Follow established guidelines - Meet legal requirements - Industry best practices - Continuous compliance ### Real Usage - Test with screen readers - Verify keyboard navigation - Check reduced motion - Test zoom levels - Validate color contrast ### Semantic First - Use proper HTML elements - Meaningful structure - Logical document flow - Correct landmark usage - Accessible names ## Quick Checks For accessibility audit, verify: - [ ] Semantic HTML used correctly - [ ] Buttons are `<button>` elements - [ ] Navigation uses `<nav>` - [ ] Main content in `<main>` - [ ] Headers are hierarchical - [ ] Color contrast meets ratios - [ ] Text contrast ≥ 4.5:1 - [ ] Large text contrast ≥ 3:1 - [ ] ARIA attributes used correctly - [ ] No `role="button"` on divs unnecessarily - [ ] Keyboard navigation works - [ ] Tab order is logical - [ ] Focus indicators visible - [ ] No keyboard traps - [ ] All images have alt text - [ ] Alt text is meaningful - [ ] Forms have labels - [ ] Error messages accessible - [ ] Interactive elements accessible ## Accessibility Audit Areas ### Semantic HTML - Proper element usage - Document structure - Landmark regions - Heading hierarchy - List markup - Table structure ### Contrast - Text color contrast - Background contrast - Focus indicator contrast - Interactive element contrast - Error state contrast - Disabled state clarity ### ARIA - Correct role usage - Proper attributes - State management - Live regions - Labels and descriptions - Hidden content handling ### Keyboard Navigation - Tab order logical - All interactive elements reachable - Focus visible - Keyboard shortcuts - No traps - Skip links present ### Alternative Text - Images have alt text - Alt text meaningful - Decorative images marked - Complex images described - Icons labeled - SVGs accessible ### Forms - Labels associated - Required fields indicated - Error messages clear - Validation accessible - Field instructions provided - Group related fields ## WCAG 2.1 AA Requirements ### Perceivable - Text alternatives - Time-based media - Adaptable content - Distinguishable elements ### Operable - Keyboard accessible - Enough time - Seizure prevention - Navigable - Input modalities ### Understandable - Readable text - Predictable operation - Input assistance - Error prevention ### Robust - Compatible with assistive tech - Valid markup - Name, role, value - Status messages ## Remediation Priority ### Critical - Keyboard navigation broken - Missing form labels - Insufficient contrast - Missing alt text ### High - Incorrect ARIA usage - Improper heading structure - Focus management issues - Screen reader problems ### Medium - Minor contrast issues - Missing landmarks - Suboptimal tab order - Enhancement opportunities ### Low - Style improvements - Enhanced descriptions - Additional hints - Nice to have fixes
Related Skills
wireframe
Create markdown wireframes with detailed UX descriptions from a product specification. Senior UX Designer perspective inspired by Notion and Linear.
ux_redesign
Redesign a feature or page from a Principal UX Designer's perspective.
tech_review
Senior Principal Engineer performing thorough technical review of implementation plans before development.
tasks
Break down an approved implementation plan into specific, actionable tasks.
specify
Create a product specification that defines what to build and why, without prescribing how.
skeptical_review
Perform a critical, skeptical code review of the project from the perspective of a Principal Engineer.
security_agent
Perform a full security review of the codebase (Node.js & React focus).
review_plan
Review the technical implementation plan against the specification.
review_domain
Perform a thorough architectural review of a domain model.
review_constitution
Review and stress-test the technical constitution after /constitute.
retro
Reflect on the completed feature, document lessons learned, and improve workflows.
release_gate
Final Go/No-Go check and release preparation.