accessibility-wcag

Audit web interfaces for WCAG 2.2 conformance and provide remediation guidance.

2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/hiyenwong/ai_collection --skill accessibility-wcag-hiyenwong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-wcag
Source: https://github.com/hiyenwong/ai_collection/tree/main/collection/skills/accessibility-wcag
Command: npx skills add https://github.com/hiyenwong/ai_collection --skill accessibility-wcag-hiyenwong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WCAG 2.2 guidance and audits help teams identify accessibility gaps in web interfaces and provide concrete remediation steps.

Core Features & Use Cases

  • Guided WCAG 2.2 conformance checks for common web components and patterns.
  • Remediation recommendations for keyboard navigation, ARIA usage, and screen reader compatibility.
  • Use cases include auditing pages, components, and apps to ensure inclusive design and compliance.

Quick Start

Provide a webpage or component to audit, and I will return WCAG 2.2 conformance guidance.

Frequently Asked Questions about accessibility-wcag

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

FAQPage Schema
How do I check my web app for WCAG 2.2 conformance?

To check WCAG 2.2 conformance, provide your webpage or UI component for an accessibility audit. This process identifies gaps in keyboard navigation, ARIA usage, and screen reader compatibility, returning structured, actionable remediation guidance with concrete fixes.

What is WCAG 2.2 remediation guidance for ARIA and screen reader compatibility?

WCAG 2.2 remediation guidance provides concrete fixes for incorrect ARIA usage and screen reader compatibility issues. It aligns with web standards to ensure inclusive design by delivering actionable recommendations for web interfaces.

Can I audit a single UI component for keyboard navigation and accessibility?

Yes, you can audit single UI components for keyboard navigation and accessibility. The audit applies to individual pages, components, and entire apps, evaluating them against WCAG 2.2 standards to ensure full conformance.

What's the best way to fix accessibility gaps in web interfaces?

The best way to fix accessibility gaps is through a guided WCAG 2.2 conformance check. This yields structured, actionable recommendations that target specific issues like keyboard navigation and ARIA usage with concrete fixes.

Do I need automated testing workflows to use this accessibility audit?

No, you do not need automated testing workflows to start. You simply provide a webpage or component to audit, and the process aligns results with existing testing workflows to deliver actionable remediation guidance.