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.
Install / Use
npx skills add AIPexStudio/AIPex --skill wcag22-a11y-auditInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of wcag22-a11y-audit
wcag22-a11y-audit scores 91/100 on our quality scale, 1084th of 4,700 Development & Engineering skills we index (top 24%).
Its SKILL.md is 18 KB long, well organised into 37 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
With 1,254 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so wcag22-a11y-audit is actively maintained.
- Our last check on 2026-10-29 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
wcag22-a11y-audit compared with similar skills
All 4 of these similar skills score higher than wcag22-a11y-audit; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| wcag22-a11y-audit (this skill)by AIPexStudio | 91 | 1.3k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install wcag22-a11y-audit?
- Run
npx skills add AIPexStudio/AIPex --skill wcag22-a11y-audit. The install tabs above show the steps for each supported agent. - Which AI agents does wcag22-a11y-audit work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is wcag22-a11y-audit safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is wcag22-a11y-audit still maintained?
- The repository was last updated about 3 months ago, so wcag22-a11y-audit is actively maintained.
Skill content
View source on GitHubname: wcag22-a11y-audit description: 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. version: 1.0.0
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
- Use
-
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
- Use
-
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
- Use
Workflow for Each Test
1. Identify scope (page/component/flow)
2. Collect evidence via search_elements and/or screenshot
3. Apply SC-specific judgment rules
4. Record Pass/Fail with evidence references
5. Provide actionable fix recommendations
Threat Context & Privacy Notes
IMPORTANT: This audit may capture sensitive information.
- Screenshots and accessibility tree dumps may contain: account names, order details, personal data, auth tokens, internal URLs.
- DO NOT include raw sensitive data in the final report.
- If a screenshot contains PII, note this and recommend masking before sharing.
- Contrast/visual judgments are estimates—always recommend verification with dedicated tools (e.g., WebAIM Contrast Checker, axe DevTools).
Pre-Audit Setup (Recommended)
Before starting the audit, confirm with the user:
- Target Scope: Full page, specific component, or user flow?
- Target Audience: Who are the primary users? (general public, internal staff, specific disability considerations)
- Priority SCs: Test all 8 SCs or focus on specific ones?
- Known Issues: Any existing accessibility issues to verify?
Success Criteria Test Procedures
SC 1.1.1 Non-text Content (Level A)
Goal: All non-text content (images, icons, controls) must have text alternatives.
Test Steps:
-
Find images and icons:
search_elements(tabId, "image | img") search_elements(tabId, "button | link | menuitem | tab | switch") -
Evaluate each element:
- Check if
nameattribute exists and is meaningful - FAIL conditions:
nameis empty or missingnameis generic: "icon", "image", "button", "img", "graphic", file names (e.g., "logo.png")nameduplicates visible text unnecessarily (redundant)
- PASS conditions:
nameaccurately describes purpose or equivalent information
- Check if
-
For decorative content:
- If truly decorative, element should have
role="presentation"orrole="none", orname=""(explicitly empty)
- If truly decorative, element should have
Common Failures:
- Icon buttons with no accessible name (screen reader announces "button" only)
- Images with
alt="image"oralt="logo.png" - SVG icons without
aria-labelor visually hidden text
Fix Recommendations:
- Add meaningful
alttext to images - Use
aria-labeloraria-labelledbyfor icon buttons - Use native semantic elements where possible (
<button>instead of<div>)
SC 1.4.3 Contrast (Minimum) (Level AA)
Goal: Text must have sufficient contrast against its background.
Requirements:
- Normal text: ≥ 4.5:1 contrast ratio
- Large text (≥24px regular or ≥18.66px bold): ≥ 3:1 contrast ratio
Test Steps:
-
Capture page states:
capture_screenshot(sendToLLM=true)- Default state
- Hover/focus states (use
computerto trigger) - Error/disabled states if applicable
-
Visual analysis prompt (for LLM):
"Analyze this screenshot for text contrast issues. Identify any text that appears to have low contrast against its background. Focus on:
- Small/body text that may be below 4.5:1
- Placeholder text in input fields
- Disabled state text
- Text overlaid on images or gradients List suspicious elements with their approximate location."
-
Record findings:
- Note: Visual analysis provides estimates only
- Flag elements for manual verification with contrast checker tools
Common Failures:
- Light gray text on white backgrounds
- Placeholder text with insufficient contrast
- Text on image backgrounds without overlay
Fix Recommendations:
- Increase text color darkness or background lightness
- Add semi-transparent overlay behind text on images
- Use contrast checker tools to verify exact ratios
SC 1.4.11 Non-text Contrast (Level AA)
Goal: UI components and graphical objects must have ≥ 3:1 contrast.
Applies to:
- Input field borders
- Button borders
- Focus indicators
- Icons conveying information
- State indicators (checkboxes, toggles, radio buttons)
Test Steps:
-
Identify UI components:
search_elements(tabId, "textbox | combobox | checkbox | radio | switch | button | slider") -
Capture states:
capture_screenshot(sendToLLM=true)- Document default, hover, focus, active, disabled states
-
Visual analysis prompt:
"Analyze this screenshot for non-text contrast issues. Check if:
- Input field borders are clearly visible (≥3:1 against background)
- Button boundaries are distinguishable
- Icons are clearly visible
- Focus indicators have sufficient contrast
- Checkbox/radio/switch states are visually distinct List any elements that appear to have insufficient contrast."
-
State coverage matrix: Document which states were tested for each component type.
Common Failures:
- Light gray input borders on white backgrounds
- Focus rings with low contrast
- Icon-only buttons where icon color is too light
Fix Recommendations:
- Increase border thickness and/or darkness
- Ensure focus indicators have ≥3:1 contrast
- Test all interactive states, not just default
SC 2.1.1 Keyboard (Level A)
Goal: All functionality must be operable via keyboard.
Test Steps:
-
Identify key tasks: Ask user or determine primary interactive flows
-
Attempt keyboard-only completion:
computer(action='key', text='Tab') // Navigate forward computer(action='key', text='shift+Tab') // Navigate backward computer(action='key', text='Enter') // Activate buttons/links computer(action='key', text='Space') // Activate buttons, toggle checkboxes computer(action='key', text='Escape') // Close dialogs/menus computer(action='key', text='ArrowDown') // Navigate within widgets -
At each step:
- Verify focus is visible (relates to 2.4.7)
- Verify expected action occurs
- If blocked, capture screenshot and note the element
-
Cross-reference with accessibility tree:
search_elements(tabId, "*")- Check if blocking element has appropriate
role - Check if element is
focusable/disabled
- Check if blocking element has appropriate
Common Failures:
- Custom components using
<div>withonClickbut no keyboard handler - Drag-and-drop only interfaces without keyboard alternative
- Focus not reaching all interactive elements
Fix Recommendations:
- Use native interactive elements (
<button>,<a>,<input>) - Add
tabindex="0"and keyboard event handlers to custom components - Provide keyboard alternatives for mouse-only interactions
SC 2.1.2 No Keyboard Trap (Level A)
Goal: If focus can enter a component, it must be able to exit via keyboard.
Test Steps:
-
Identify potential trap components:
- Modals/dialogs
- Dropdown menus
- Rich text editors
- Embedded iframes
- Custom widgets
-
For each component:
- Tab into the component
- Attempt to Tab out (forward and backward)
- Attempt Escape to close (if applicable)
- Document entry point and exit behavior
-
Capture evidence:
capture_screenshot(sendToLLM=true)- Screenshot when entering
- Screenshot showing focus location
- Note if any special keys are required and whether instructions are provided
Common Failures:
- Modal dialogs that don't close on Escape
- Focus getting "stuck" in embedded content
- Custom dropdown menus that don't release focus
Fix Recommendations:
- Implement focus trapping in modals with Escape to close
- Ensure all custom widgets have documented exit mechanism
- Provide visible instructions if non-standard keys are required
SC 2.4.3 Focus Order (Level A)
Goal: Focus order must preserve meaning and operability.
Test Steps:
-
Tab through the page:
computer(action='key', text='Tab')- Document the sequence of focused elements
-
Compare with visual order:
capture_screenshot(sendToLLM=true)- Focus sequence should match left-to-right, top-to-bottom reading order
- Related elements should be adjacent in focus order
-
Test dynamic content:
- Open a modal → focus should move to modal
- Close modal → focus should return to trigger or logical position
- Expand accordion → new content should be reachable
- Show error message → focus should move to or near error
-
Check for problematic patterns:
search_elements(tabId, "tabindex")- Positive
tabindexvalues (>0) cause unpredictable order
- Positive
Common Failures:
- Focus jumps to unrelated page sections
- Positive
tabindexvalues creating chaotic order - Dynamic content inserted but not reachable in logical sequence
Fix Recommendations:
- Use DOM order to control focus order (avoid positive tabindex)
- Manage focus programmatically for dynamic content
- Return focus to logical position after dialog/overlay closes
SC 2.4.7 Focus Visible (Level AA)
Goal: Keyboard focus indicator must be visible.
Test Steps:
-
Ensure keyboard-only mode:
- Do not use mouse during this test
- Use Tab to navigate
-
At each focused element:
capture_screenshot(sendToLLM=true)- Verify focus indicator is clearly visible
- Check various element types: buttons, links, inputs, custom controls
-
Visual analysis prompt:
"Is there a visible focus indicator on the currently focused element in this screenshot? The indicator should be clearly distinguishable (outline, border, background change, underline, or similar). Describe what you see and whether it provides sufficient visual distinction."
-
Cross-reference:
search_elements(tabId, "*focused*")- Confirm which element has
focusedstate
- Confirm which element has
Common Failures:
- Global
outline: nonewith no replacement style - Focus style too subtle (e.g., 1px light gray)
- Focus style matches hover style (can't distinguish keyboard vs mouse)
Fix Recommendations:
- Never remove focus outline without providing alternative
- Ensure focus indicator has ≥3:1 contrast (links to 1.4.11)
- Use
:focus-visiblefor keyboard-on
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
