fixing-accessibility
Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.
97
96%
Does it follow best practices?
Impact
99%
1.06xAverage 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 well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually use, explicitly states both what the skill does and when to use it, and carves out a distinct niche in accessibility that won't conflict with other HTML/CSS skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors.' This provides clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Audit and fix HTML accessibility issues including...') AND when ('Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'accessibility', 'ARIA labels', 'keyboard navigation', 'focus management', 'color contrast', 'form errors', 'WCAG compliance', 'interactive controls', 'forms', 'dialogs'. Good coverage of both technical and common terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on HTML accessibility with distinct triggers like 'ARIA', 'WCAG', 'accessibility', 'focus management'. Unlikely to conflict with general HTML or CSS skills due to the specific accessibility focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality accessibility skill that efficiently covers critical WCAG concerns with actionable, concrete guidance. The priority-based organization and executable HTML examples make it immediately useful. Minor improvement could come from splitting detailed widget patterns into separate reference files for complex components.
Suggestions
Consider adding a separate reference file for complex widget patterns (dialogs, menus, comboboxes) with more detailed examples, keeping SKILL.md as the overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using tables and bullet points to convey rules without explaining basic concepts Claude already knows. Every section earns its place with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready HTML examples in the 'common fixes' section, specific rules with exact attributes to use (aria-label, aria-describedby, aria-invalid), and clear guidance on what to report when reviewing files. | 3 / 3 |
Workflow Clarity | Clear two-mode usage (apply constraints vs review file), explicit priority ordering for rule categories, and specific review guidance that sequences work (fix critical first, prefer native HTML, quote snippets). The workflow for file review includes validation steps (quote exact line, state why it matters, propose fix). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a priority table, but all content is inline in a single file. For a skill of this length (~100 lines), some sections like detailed ARIA patterns for complex widgets could be split into reference files. | 2 / 3 |
Total | 11 / 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
- ibelick/ui-skills
- Commit
95d0e08
- 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.