accessibility

Audits web accessibility and provides WCAG 2.2-aligned improvement guidance.

Updated May 18, 2026

Search Tags:#testing #accessibility #a11y #patterns #wcag #keyboard #aria

Ready to run

npx skills add https://github.com/lucasloutayf/barberia-evolution --skill accessibility-lucasloutayf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/lucasloutayf/barberia-evolution/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/lucasloutayf/barberia-evolution --skill accessibility-lucasloutayf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessibility barriers prevent users from fully interacting with web content. This Skill provides guidance and patterns to audit and improve accessibility in alignment with WCAG 2.2, helping products reach inclusive usability.

Core Features & Use Cases

WCAG-aligned auditing across POUR principles and conformance levels (A, AA, AAA), with practical patterns and checklists.
Implementation patterns for ARIA usage, keyboard accessibility, and color-contrast best practices, with ready-made examples.
Testing guidance and references to support ongoing compliance across pages and components.

Quick Start

Audit a web page for WCAG 2.2 accessibility, identify critical issues, and apply recommended fixes in a single sprint.

Frequently Asked Questions about accessibility

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 accessibility compliance?▼

Audit web accessibility by evaluating content against WCAG 2.2 POUR principles and conformance levels (A, AA, AAA). This process identifies critical issues across keyboard operability, color contrast, and ARIA roles, providing actionable patterns and code examples to apply fixes.

What ARIA patterns and keyboard accessibility best practices should I use for inclusive design?▼

Implement ARIA patterns and keyboard accessibility by applying ready-made code examples that ensure proper focus management and screen reader compatibility. These patterns guide correct ARIA usage and keyboard operability to meet inclusive design standards.

Can I use this approach to check Lighthouse accessibility scores and fix manual conformance issues?▼

Yes, you can check Lighthouse accessibility issues and perform manual conformance tasks across websites and apps. The guidance provides testing references and actionable patterns to resolve identified keyboard, contrast, and ARIA deficits.

Does this WCAG 2.2 accessibility guidance work for auditing documents and mobile apps?▼

This WCAG 2.2 accessibility guidance applies to manual conformance tasks across websites, apps, and documents. It specifies metadata and provides testing guidance to ensure consistent inclusive usability across different content formats.

What is the best way to fix color contrast and focus management issues during a web accessibility audit?▼

Fix color contrast and focus management issues by applying implementation patterns and best practices provided during the audit. The guidance includes ready-made code examples to ensure compliance with WCAG 2.2 contrast and focus requirements.

Why do I need to check keyboard operability and ARIA roles for WCAG compliance?▼

Checking keyboard operability and ARIA roles is necessary for WCAG compliance because these barriers prevent users from fully interacting with web content. Auditing these elements ensures products reach inclusive usability standards.