accessibility-compliance
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
87
82%
Does it follow best practices?
Impact
93%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its accessibility-focused domain with specific capabilities and explicit trigger conditions. It uses appropriate technical terminology that developers would naturally use while remaining accessible. The description effectively distinguishes itself from general UI development skills through its specific focus on WCAG compliance and assistive technologies.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Implement WCAG 2.2 compliant interfaces', 'mobile accessibility', 'inclusive design patterns', and 'assistive technology support'. Uses third person voice correctly. | 3 / 3 |
Completeness | Clearly answers both what (implement WCAG 2.2 compliant interfaces with various accessibility features) AND when (explicit 'Use when...' clause covering auditing, ARIA patterns, screen readers, and inclusive UX). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'accessibility', 'WCAG', 'ARIA patterns', 'screen readers', 'inclusive', 'assistive technology'. These are terms developers naturally use when seeking accessibility help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on accessibility and WCAG compliance. The specific mentions of WCAG 2.2, ARIA, screen readers, and assistive technology create distinct triggers unlikely to conflict with general UI/UX or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid accessibility reference with excellent, production-ready code patterns that demonstrate proper ARIA usage, focus management, and screen reader support. The main weaknesses are verbosity in explaining concepts Claude already knows, lack of explicit audit/implementation workflows with validation steps, and a monolithic structure that could benefit from splitting into focused sub-documents.
Suggestions
Add an explicit accessibility audit workflow with validation checkpoints (e.g., '1. Run axe-core, 2. Fix violations, 3. Test with VoiceOver, 4. Verify keyboard navigation, 5. Check color contrast')
Trim the 'Core Capabilities' section - Claude knows what ARIA roles, states, and properties are; focus on project-specific patterns instead
Split detailed patterns into a separate PATTERNS.md file and keep SKILL.md as a concise overview with quick reference table and links to detailed content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some explanatory content Claude already knows (e.g., explaining what WCAG principles mean, basic ARIA concepts). The 'Core Capabilities' section could be trimmed as it restates well-known accessibility fundamentals. | 2 / 3 |
Actionability | Excellent executable code examples throughout - the button, modal, form, skip link, and live region patterns are all copy-paste ready with TypeScript types and complete implementations. The contrast ratio utility is also directly usable. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for conducting an accessibility audit or implementing compliance. Missing validation checkpoints like 'run axe-core after implementing' or 'test with screen reader before committing'. The 'When to Use' section lists tasks but doesn't sequence them. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~350 lines) that could benefit from splitting detailed patterns into separate files. The external resources at the end are good, but internal progressive disclosure (e.g., PATTERNS.md, TESTING.md) would improve navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- haniakrim21/everything-claude-code
- Commit
ae2cadd
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.