Chrome DevToolsChrome DevTools MCP server, 54k+ stars4,100 installs on skills.shA11y Debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines.
Use Edge to load the skill a11y-debugging from chromedevtools/chrome-devtools-mcp for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
2 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
What it does
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.
Why Chrome DevTools
Chrome DevTools team open-source projects. Each fact links its public source.
- chrome-devtools-mcp, 54k+ stars
The Chrome DevTools MCP server for coding agents has 54k+ GitHub stars.
GitHub repo - Awesome DevTools list, 7.1k+ stars
The awesome-chrome-devtools list has 7.1k+ GitHub stars.
GitHub repo
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads A11y Debugging.
Related skills
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.
Accessibility patterns for React and Next.js — semantic HTML, ARIA attributes, form labeling, keyboard navigation, focus management, and screen reader support. Use when building or reviewing forms, modals, dropdowns, too
Audits and implements web accessibility (a11y) following WCAG 2.1 guidelines with ARIA patterns, keyboard navigation, screen reader support, and contrast checking. Use when users request "accessibility audit", "a11y revi
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.
Design for everyone by treating accessibility as a first-class design discipline, not a compliance checklist. Part of the Intent design strategy system. Covers WCAG 2.2 for designers, screen reader experience design, key
Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, o
No evidence record yet
No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Static scans check the code, not how well the skill works.
State definitionsSelect the Files tab to load SKILL.md.
Skill details
Security scansReviewed
2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.
Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.
Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
- Edge static checks
- Pass · 0 counted findings · 2026-11-17
- Edge committed-secret checks
- Pass · 0 counted findings · 2026-11-17
Creator, source & licencechromedevtools
From the chromedevtools public repository. Edge did not write or edit this skill.
- Repository
- chromedevtools/chrome-devtools-mcp
- Skill file
- View source at revision
- Revision
- 47c5b3753d9bc6da32e261838a033e6427940cf0
- Package hash
- sha256:fb139a727c3e28ac410ab8ac1bec0448597ba344843dfd49769a5851fc18c31e
- Licence
- Apache-2.0
- Description
- 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.
Quoted from the skill’s own description
Read skill files2 files
2 files, 8.5 KB at revision 47c5b3753d9b.
Questions about A11y Debugging
What does A11y Debugging do?
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Published by Chrome DevTools (chromedevtools/chrome-devtools-mcp).
Is A11y Debugging safe to use?
Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 17, 2026). The Evidence tab shows the scan.
How do I use A11y Debugging in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.