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.
81
85%
Does it follow best practices?
Impact
55%
1.01xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Lighthouse audit workflow and report parsing
Lighthouse mode: navigation
50%
50%
outputDirPath set
60%
70%
Programmatic report parsing
100%
100%
Filters by score < 1
100%
100%
Extracts selector/snippet
100%
100%
Score reported
100%
100%
Failed audits listed
100%
100%
No large files left
100%
100%
audit.sh is executable/runnable
100%
100%
report.md present
100%
100%
Form labels, keyboard navigation, and focus management
Orphaned inputs snippet used
35%
42%
evaluate_script used for labels
0%
0%
Tab key navigation tested
50%
0%
take_snapshot used for focus tracking
0%
0%
Focus sequence documented
100%
100%
Modal focus trap checked
100%
100%
Accessible name check
60%
70%
Browser issues checked
0%
0%
includePreservedMessages used
0%
0%
Tap targets, color contrast, and global page checks
take_snapshot for UIDs
0%
0%
Tap target snippet used
0%
0%
UID passed to tap target snippet
0%
0%
48x48 threshold applied
0%
100%
list_console_messages for contrast
0%
0%
Color contrast snippet used
0%
0%
Global page checks snippet used
33%
33%
Document settings reported
100%
100%
Contrast ratios numeric
100%
100%
Three report sections present
100%
100%
1b857c9
Table of Contents
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.