a11y-debugging

Audit web page accessibility using Chrome DevTools MCP and web.dev guidelines.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/rithm84/Manor --skill a11y-debugging-rithm84
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-debugging
Source: https://github.com/rithm84/Manor/tree/main/.agents/skills/browser-related/chrome-devtools-mcp/a11y-debugging
Command: npx skills add https://github.com/rithm84/Manor --skill a11y-debugging-rithm84

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Web accessibility issues like missing labels, poor color contrast, broken keyboard navigation, and incorrect heading structures are hard to detect without assistive technology. This Skill gives an AI agent a structured workflow to audit and debug accessibility problems directly in a live browser using Chrome DevTools MCP tools. ## Core Features & Use Cases - Automated Lighthouse Audits: Run navigation-mode Lighthouse accessibility audits and parse failing audits from the JSON report with jq or Node.js one-liners instead of loading the full report into context. - Accessibility Tree Inspection: Use take_snapshot to verify heading hierarchy, semantic landmarks, accessible names, and DOM order against the visual layout. - Targeted JavaScript Snippets: Run ready-made evaluate_script snippets to find orphaned form inputs, measure tap target sizes, approximate color contrast ratios, and check global page settings like lang, title, and viewport. - Use Case: While testing a new checkout page, ask the agent to audit it. It runs Lighthouse, checks console issues for native Chrome a11y warnings, tabs through interactive elements to verify focus order, and reports every unlabeled input and low-contrast element with its selector. ## Quick Start Audit the current page for accessibility issues including labels, keyboard focus, tap targets, and color contrast, then report each failing element with its selector.

Frequently Asked Questions about a11y-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a web page for accessibility issues with Chrome DevTools?

Run a Lighthouse audit in navigation mode and save the JSON report, then filter failing audits with jq or a Node.js one-liner to extract selectors and snippets. Also check list_console_messages with the issue type for Chrome's native accessibility warnings.

How to test keyboard navigation and focus traps without a screen reader?

Use the press_key tool with Tab or Shift+Tab to move focus, then call take_snapshot to see which element is marked focused in the accessibility tree. For modals, verify focus moves into the dialog and stays trapped until it closes.

How do I find form inputs missing labels on a page?

Run the Find Orphaned Form Inputs snippet with evaluate_script. It returns every input, select, or textarea lacking a label[for], aria-label, aria-labelledby, or wrapping label element, along with its tag, id, name, and placeholder.

Can I check color contrast ratios programmatically in the browser?

Yes, first check list_console_messages for native Low Contrast issues. If none appear, use the Check Color Contrast snippet, which computes an approximate WCAG ratio from computed styles, though it does not handle gradients or background images.

What are the limitations of accessibility tree snapshots for visual issues?

The accessibility tree exposes semantics but not geometry, so it cannot show tap target sizes or visual contrast. Combine take_snapshot with take_screenshot and evaluate_script measurements to cover visual and layout-related accessibility checks.