accessibility
Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast".
87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 an excellent skill description that hits all the marks. It provides specific technical capabilities with concrete details (like the 4.5:1 contrast ratio), includes a comprehensive 'Use when' clause with both general scenarios and specific error messages users might encounter, and carves out a clear niche in web accessibility that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'semantic HTML, proper ARIA, focus management, screen reader support, color contrast (4.5:1 text), keyboard navigation, form labels, and live regions.' These are precise, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (build WCAG 2.1 AA compliant websites with specific techniques) AND when (explicit 'Use when' clause with multiple trigger scenarios including troubleshooting specific error messages). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'accessible interfaces', 'screen reader issues', 'keyboard navigation', 'focus outline missing', 'aria-label required', 'insufficient contrast', 'WCAG'. Includes both general terms and specific error messages users might search for. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on web accessibility/WCAG compliance. The specific standard (WCAG 2.1 AA), technical terms (ARIA, screen reader), and error messages make it highly distinguishable from general web development or UI skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, highly actionable accessibility skill with excellent executable code examples and clear workflows. However, it suffers from verbosity - the document tries to be both a quick reference and a complete guide, resulting in a lengthy file that could benefit from splitting detailed patterns and issue documentation into separate reference files. The core guidance is solid and practical.
Suggestions
Move the '12 Known Issues Prevention' section to a separate reference file (e.g., references/common-issues.md) and link to it, as this information is largely redundant with the Critical Rules section
Consider moving the 'Common Patterns' section to references/patterns.md since these are detailed implementations that aren't needed for quick reference
Trim explanatory text like 'Why this matters' sections - Claude understands why semantic HTML and focus management are important
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | While the skill provides valuable information, it's quite verbose at ~600 lines. Some sections explain concepts Claude likely knows (e.g., what semantic HTML is, why it matters). The 12 documented issues section is repetitive with information already covered elsewhere. | 2 / 3 |
Actionability | Excellent executable code examples throughout - React/TypeScript patterns for dialogs, tabs, forms are copy-paste ready. CSS examples are complete and specific. Decision trees provide concrete guidance for element selection. | 3 / 3 |
Workflow Clarity | Clear 5-step process with explicit validation checkpoints. Testing workflow section provides numbered steps with specific tools and commands. The complete setup checklist at the end serves as a verification checkpoint. | 3 / 3 |
Progressive Disclosure | References to external files (references/semantic-html.md, agents/a11y-auditor.md) are well-signaled, but the main document is monolithic with extensive inline content that could be split. The 12 issues section and common patterns could be separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (883 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.