accessibility

Name: accessibility
Availability: InStock
Author: sonpaier

Audit web accessibility against WCAG 2.2 guidelines.

Updated Aug 27, 2026

Search Tags:#accessibility #a11y #screen reader #web development #WCAG #usability

Ready to run

npx skills add https://github.com/SonPaier/carfect --skill accessibility-sonpaier

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/SonPaier/carfect/tree/main/.claude/skills/accessibility
Command: npx skills add https://github.com/SonPaier/carfect --skill accessibility-sonpaier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make digital content usable by everyone, including individuals with disabilities, by adhering to accessibility standards.

Core Features & Use Cases

WCAG Compliance: Audits and guides improvements based on Web Content Accessibility Guidelines (WCAG) 2.2.
Accessibility Principles: Covers Perceivable, Operable, Understandable, and Robust (POUR) principles.
Use Case: When developing a new website feature, use this Skill to ensure it meets WCAG AA standards for keyboard navigation, color contrast, and screen reader compatibility before launch.

Quick Start

Use the accessibility skill to audit the provided webpage for WCAG 2.2 compliance.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I audit my website for WCAG 2.2 compliance?▼

Automated accessibility testing with tools like Lighthouse and axe-core identifies common WCAG 2.2 violations such as missing text alternatives and poor color contrast. Manual testing checklists are also supported to catch keyboard navigation and screen reader compatibility issues.

What are the WCAG POUR principles for web accessibility?▼

WCAG POUR principles require web content to be Perceivable, Operable, Understandable, and Robust. They ensure users can perceive interface components, navigate interfaces, comprehend content, and access information reliably across different assistive technologies like screen readers.

How do I fix keyboard navigation and focus visibility for screen reader users?▼

Fix keyboard navigation and focus visibility by auditing operability against WCAG 2.2 guidelines. Ensure all interactive elements are reachable via keyboard, focus states are clearly visible, and ARIA attributes are correctly implemented to support screen reader compatibility.

Does this accessibility audit support automated testing with axe-core and Lighthouse?▼

Yes, this accessibility audit supports automated testing with tools like Lighthouse and axe-core. It uses these tools to identify automated WCAG 2.2 violations while also providing manual testing checklists for comprehensive coverage of perceivable and operable principles.

What is the best way to ensure ARIA usage meets WCAG AA standards?▼

The best way to ensure ARIA usage meets WCAG AA standards is auditing your web development components against WCAG 2.2 guidelines. Evaluate robust and operable principles to verify ARIA attributes correctly enhance screen reader compatibility without causing usability issues.