wcag22-a11y-audit

# 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 1. **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 2. **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 3. **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 ### Workflow for Each Test ``` 1. Identify scope (page/component/flow) 2. Collect evidence via search_elements and/or screenshot 3. Apply SC-specific judgment...