Agent skill · Security

wcag22-a11y-audit

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. Use this skill when you need to perform accessibility testing/auditing on a live webpage.

AIPexStudiogithub.com/AIPexStudioGitHub ↗
claude-codeMIT
Install
npx skills add AIPexStudio/AIPex --skill wcag22-a11y-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 18 KB
Bundled scripts: none
Version: 1.0.0
Path: packages/browser-runtime/src/skill/built-in/wcag22-a11y-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,230 · +1 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 -

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Tool Usage Strategy (IMPORTANT)
  3. Priority Order
  4. Workflow for Each Test
  5. Threat Context & Privacy Notes
  6. Pre-Audit Setup (Recommended)
  7. Success Criteria Test Procedures
  8. SC 1.1.1 Non-text Content (Level A)
  9. SC 1.4.3 Contrast (Minimum) (Level AA)
  10. SC 1.4.11 Non-text Contrast (Level AA)
  11. SC 2.1.1 Keyboard (Level A)
  12. SC 2.1.2 No Keyboard Trap (Level A)
  13. SC 2.4.3 Focus Order (Level A)
  14. SC 2.4.7 Focus Visible (Level AA)
More from AIPex
All skills →
About this skill
What does the wcag22-a11y-audit skill do?

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. Use this skill when you need to perform accessibility testing/auditing on a live webpage.

How do I install it?

Run `npx skills add AIPexStudio/AIPex --skill wcag22-a11y-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From AIPexStudio/AIPex, a repository with 1,230 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going