WCAG 2.2 Accessibility Audit skill that systematically evaluates web pages against 8 core Success Criteria (1.1.1, 1.4.3, 1.4.11, 2.1.1, 2.1.2, 2.4.3, 2.4.7, 4.1.2) using accessibility tree inspection and visual analysis.
SkillScore65Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/14/2026
What it changes
Passed 12 of 19 test cases with the skill, and 10 of 19 without it.
Without skill52%
With skill65%
Checks it passed that the model alone missed
Groups findings into Critical, Serious, Moderate, and Minor severity tiers.
Confirms target scope or priority success criteria with the user prior to auditing.
Specifies the tool download_current_chat_report_zip for packaging report artifacts.
and 2 more in the full report
5 fixed10 passed either way6 still failing2 broke
Pass-rate lift
+13 pp
Tokens
+164%
Agent turns
0%
Response time
-23%
Model gemini-3.6-flashMeasured 8/14/2026v115 of 23 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
The accessibility audit Markdown report has just been presented in the chat along with screenshot placeholders `[[screenshot:1]]` and `[[screenshot:2]]`. What final step should be offered to the user to deliver the complete report package?
What was checked, without and with the skill
Checked
Without skill
With skill
Offers to export the accessibility audit report as a ZIP file.
Passed
Passed
Specifies the tool download_current_chat_report_zip for packaging report artifacts.
Missed
Passed
case-22 · gemini-3.6-flash · 8/14/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md628 linessingle file
WCAG 2.2 Accessibility Audit Skill
When to Use This Skill
Use this skill when the user wants to:
Perform accessibility testing or auditing on a live webpage
Evaluate a page against WCAG 2.2 Success Criteria
Identify accessibility barriers for keyboard and screen reader users
Generate a structured accessibility audit report with evidence
Tool Usage Strategy (IMPORTANT)
This skill uses a hybrid approach combining structured accessibility tree analysis and visual inspection.
Priority Order
PRIMARY: Accessibility Tree (search_elements)
Use search_elements(tabId, query) to retrieve structured accessibility information
This provides role, name, value, checked, expanded, disabled, focused, etc.
Best for: 1.1.1, 2.1.1, 4.1.2 and element identification for other SCs
SECONDARY: Visual Analysis (Screenshot + LLM)
Use capture_screenshot(sendToLLM=true) for visual inspection
Essential for: 1.4.3, 1.4.11, 2.4.7 (contrast and focus visibility)
Insert [[screenshot:N]] placeholders in the report for evidence
KEYBOARD INTERACTION: computer tool
Use computer(action='key', text='Tab') for keyboard navigation testing
Essential for: 2.1.1, 2.1.2, 2.4.3, 2.4.7
Capture screenshots at key moments to document focus path
Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.