skills.rest
AIPexStudio
AIPexStudioOFFICIAL
Explore all skills by this author →
GitHub

wcag22-a11y-audit

Audit live web pages for WCAG 2.2 accessibility compliance.

1.2k|128|Updated Aug 22, 2024
Search Tags:#accessibility#a11y#WCAG#audit#contrast#report#keyboard
One-click install
npx skills add https://github.com/AIPexStudio/AIPex --skill wcag22-a11y-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wcag22-a11y-audit
Source: https://github.com/AIPexStudio/AIPex/tree/main/packages/browser-runtime/src/skill/built-in/wcag22-a11y-audit
Command: npx skills add https://github.com/AIPexStudio/AIPex --skill wcag22-a11y-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams verify and document accessibility conformance of web pages against WCAG 2.2. It automates evidence collection to identify barriers for keyboard users and screen readers, reducing manual testing time and risk.

Core Features & Use Cases

  • Hybrid audit approach combining structured accessibility tree analysis and visual verification for accurate findings.
  • Generates a structured accessibility audit report with evidence, screenshots, and remediation recommendations.
  • Use Case: QA teams or developers auditing a live page to identify blockers and create actionable fixes.

Quick Start

Run the wcag22-a11y-audit on a live page URL to generate an accessibility audit report.

Frequently Asked Questions about wcag22-a11y-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a web page for WCAG 2.2 compliance?▼

To audit web pages for WCAG 2.2 compliance, analyze the live URL using a hybrid approach that inspects the accessibility tree, captures visual screenshots, and tests keyboard navigation to produce a structured report with evidence.

What is the best way to identify keyboard navigation barriers on a live page?▼

Identifying keyboard navigation barriers requires testing the live page to surface actionable findings that block keyboard users and screen readers, reducing manual testing time by automating the evidence collection process.

Can I automatically generate an accessibility audit report with remediation recommendations?▼

You can automatically generate a structured accessibility audit report that includes evidence, screenshots, and remediation recommendations by verifying eight core WCAG success criteria during the live page analysis.

Does this WCAG audit process verify visual elements like color contrast?▼

The WCAG audit verifies visual elements like color contrast by combining structured accessibility tree analysis with visual verification, capturing screenshots to accurately surface compliance findings against WCAG standards.

What do QA teams need to perform a WCAG 2.2 accessibility audit?▼

QA teams need a live page URL to perform a WCAG 2.2 accessibility audit, which automates evidence collection to identify blockers and creates actionable fixes without requiring complex manual environmental setup.

Why use a hybrid approach for accessibility testing instead of manual inspection?▼

A hybrid accessibility testing approach combines structured accessibility tree inspection with visual analysis to accurately surface findings, reducing the risk and time associated with purely manual WCAG compliance verification.

Related Skills

Explore More Legal & Compliance Skills→
brandonjjonbrandonjjon

accessibility

Identify web page accessibility issues and guide WCAG 2.2 remediation.

Community
Advanced
AskTinNguyenAskTinNguyen

audit

Audit UI interfaces for accessibility, performance, theming, and responsive issues.

Community
Advanced
lushly-devlushly-dev
4

test-components

Run Playwright E2E tests with visual regression and axe-core accessibility checks.

Official
Intermediate
a53alia53ali

accessibility-testing

Test web and mobile applications for WCAG 2.1/2.2 AA conformance using automated tools and manual techniques.

Community
Advanced