·a11y-debugging
</>

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.

79Installs·6Trend·@chromedevtools

Installation

$npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill a11y-debugging

How to Install a11y-debugging

Quickly install a11y-debugging AI skill to your development environment via command line

  1. Open Terminal: Open your terminal or command line tool (Terminal, iTerm, Windows Terminal, etc.)
  2. Run Installation Command: Copy and run this command: npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill a11y-debugging
  3. Verify Installation: Once installed, the skill will be automatically configured in your AI coding environment and ready to use in Claude Code, Cursor, or OpenClaw

Source: chromedevtools/chrome-devtools-mcp.

SKILL.md

View raw

Accessibility Tree vs DOM: Visually hiding an element (e.g., CSS opacity: 0) behaves differently for screen readers than display: none or aria-hidden="true". The takesnapshot tool returns the accessibility tree of the page, which represents what assistive technologies "see", making it the most reliable source of truth for semantic structure.

Reading web.dev documentation: If you need to research specific accessibility guidelines (like https://web.dev/articles/accessible-tap-targets), you can append .md.txt to the URL (e.g., https://web.dev/articles/accessible-tap-targets.md.txt) to fetch the clean, raw markdown version. This is much easier to read!

Chrome automatically checks for common accessibility problems. Use listconsolemessages to check for these native audits first:

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. Source: chromedevtools/chrome-devtools-mcp.

Facts (cite-ready)

Stable fields and commands for AI/search citations.

Install command
npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill a11y-debugging
Category
</>Dev Tools
Verified
First Seen
2026-02-23
Updated
2026-03-10

Browse more skills from chromedevtools/chrome-devtools-mcp

Quick answers

What is 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. Source: chromedevtools/chrome-devtools-mcp.

How do I install a11y-debugging?

Open your terminal or command line tool (Terminal, iTerm, Windows Terminal, etc.) Copy and run this command: npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill a11y-debugging Once installed, the skill will be automatically configured in your AI coding environment and ready to use in Claude Code, Cursor, or OpenClaw

Where is the source repository?

https://github.com/chromedevtools/chrome-devtools-mcp

Details

Category
</>Dev Tools
Source
skills.sh
First Seen
2026-02-23