a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
79
81%
Does it follow best practices?
Impact
55%
1.01xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
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 communicates its purpose, tools, and trigger conditions. It uses third person voice, lists specific concrete capabilities, includes a well-formed 'Use when...' clause with natural trigger terms, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: accessibility debugging and auditing, testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast. | 3 / 3 |
Completeness | Clearly answers both what ('accessibility debugging and auditing based on web.dev guidelines') and when ('Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'accessibility', 'a11y', 'semantic HTML', 'ARIA labels', 'focus states', 'keyboard navigation', 'tap targets', 'color contrast'. These are all terms a developer would naturally use when seeking accessibility help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: accessibility auditing via Chrome DevTools MCP with web.dev guidelines. The specific tool (Chrome DevTools MCP), domain (accessibility), and reference framework (web.dev) make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured accessibility auditing skill with clear workflow patterns covering the major a11y testing areas. Its main weakness is that several critical actionable steps (tap target measurement, contrast checking, orphaned input detection, global checks) are delegated to an external snippets file that isn't provided in the bundle, reducing immediate actionability. The content is mostly concise but could trim some explanatory passages that Claude already knows.
Suggestions
Ensure references/a11y-snippets.md is included in the bundle, or inline the most critical snippets (e.g., tap target measurement, contrast check) directly in the SKILL.md to make the workflows fully executable.
Trim the Core Concepts section — Claude already understands CSS visibility semantics and accessibility tree basics; focus on the non-obvious insight (e.g., the .md.txt URL trick is valuable, but the opacity vs display:none explanation is unnecessary).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanatory context (e.g., explaining what the accessibility tree is, explaining what Lighthouse scores mean). Some sections like the 'Core Concepts' preamble about opacity vs display:none could be trimmed since Claude knows CSS semantics. | 2 / 3 |
Actionability | Provides concrete tool names and parameters (e.g., `press_key` with `"Tab"`, `list_console_messages` with `types: ["issue"]`), and includes one executable code snippet for parsing Lighthouse reports. However, the actual evaluation snippets are deferred to a referenced file (references/a11y-snippets.md) that is not provided in the bundle, making several key steps non-executable from this file alone. | 2 / 3 |
Workflow Clarity | The eight workflow patterns are clearly sequenced with numbered steps, explicit tool calls at each stage, and validation checkpoints (e.g., 'Analyze the Summary' after Lighthouse, comparing snapshot to screenshot for reordering, checking focused element after Tab press). The troubleshooting section provides a fallback path when automated approaches fail. | 3 / 3 |
Progressive Disclosure | The skill references `references/a11y-snippets.md` multiple times for detailed code snippets, which is good progressive disclosure structure. However, the bundle files show no files were provided, so we cannot verify the referenced file exists. The main content is well-organized with clear section headers, but the repeated references to a single external file that may not exist is a concern. | 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
- ChromeDevTools/chrome-devtools-mcp
- Commit
faac61d
- 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.