wcag22-a11y-audit

1# WCAG 2.2 Accessibility Audit Skill
2 
3## When to Use This Skill
4 
5Use this skill when the user wants to:
6 
7- Perform accessibility testing or auditing on a live webpage
8- Evaluate a page against WCAG 2.2 Success Criteria
9- Identify accessibility barriers for keyboard and screen reader users
10- Generate a structured accessibility audit report with evidence
11 
12---
13 
14## Tool Usage Strategy (IMPORTANT)
15 
16**This skill uses a hybrid approach combining structured accessibility tree analysis and visual inspection.**
17 
18### Priority Order
19 
201. **PRIMARY: Accessibility Tree (search_elements)**
21   - Use `search_elements(tabId, query)` to retrieve structured accessibility information
22   - This provides `role`, `name`, `value`, `checked`, `expanded`, `disabled`, `focused`, etc.
23   - Best for: 1.1.1, 2.1.1, 4.1.2 and element identification for other SCs
24 
252. **SECONDARY: Visual Analysis (Screenshot + LLM)**
26   - Use `capture_screenshot(sendToLLM=true)` for visual inspection
27   - Essential for: 1.4.3, 1.4.11, 2.4.7 (contrast and focus visibility)
28   - Insert `[[screenshot:N]]` placeholders in the report for evidence
29 
303. **KEYBOARD INTERACTION: computer tool**
31   - Use `computer(action='key', text='Tab')` for keyboard navigation testing
32   - Essential for: 2.1.1, 2.1.2, 2.4.3, 2.4.7
33   - Capture screenshots at key moments to document focus path
34 
35### Workflow for Each Test
36 
37```
381. Identify scope (page/component/flow)
392. Collect evidence via search_elements and/or screenshot
40…