Skip to content
TrustedSkillsbeta
Back to all skills

A11Y Debugging

Checked
chromedevtools·vlatest·frontend·Apache-2.0

Automated accessibility checks using Chrome DevTools to identify and report WCAG violations in web applications.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add chromedevtools/chrome-devtools-mcp --skill a11y-debugging -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

chromedevtools

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned chromedevtools/chrome-devtools-mcp at 47c5b3753d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
47c5b3753d
Manifest
skills/a11y-debugging/SKILL.md
Scanned
2 files, 175 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

a11y-debugging

What it does

This skill enables AI agents to inspect and debug web accessibility issues directly within the Chrome DevTools environment. It provides deep visibility into how browsers interpret HTML elements regarding screen reader support, keyboard navigation, and visual contrast compliance.

When to use it

  • Investigating why a specific form field fails automated accessibility audits.
  • Debugging complex dynamic content that loses focus management after JavaScript updates.
  • Verifying color contrast ratios on custom UI components against WCAG standards.
  • Analyzing the semantic structure of error messages for screen reader compatibility.

Key capabilities

  • Direct integration with Chrome DevTools accessibility audit panels.
  • Real-time inspection of ARIA attributes and roles in live browser contexts.
  • Identification of missing or incorrect landmark regions in page layouts.
  • Detection of keyboard trap scenarios within interactive widgets.

Example prompts

  • "Run an accessibility audit on the current tab and list all elements flagged for missing labels."
  • "Inspect the navigation menu's ARIA structure and suggest fixes for any broken focus order."
  • "Check the color contrast of the primary call-to-action button against the background and report compliance status."

Tips & gotchas

Ensure the target website is fully loaded before initiating an audit, as dynamic content may not yet be rendered for analysis. This skill relies on Chrome DevTools; it cannot analyze accessibility in non-Chromium browsers or purely server-side rendered content without a browser instance.