accessibility

Identify and remediate accessibility barriers for WCAG 2.2 conformance.

1|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/gmagnenat/focus-flow-app --skill accessibility-gmagnenat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/gmagnenat/focus-flow-app/tree/main/skills/accessibility
Command: npx skills add https://github.com/gmagnenat/focus-flow-app --skill accessibility-gmagnenat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility following WCAG 2.2 guidelines to help teams make sites usable by people with disabilities.

Core Features & Use Cases

  • Provides WCAG 2.2 reference material, patterns, checklists, and practical examples for implementing accessible UI.
  • Covers keyboard navigation, focus management, semantic markup, ARIA usage, and testing workflows to verify conformance.
  • Use cases include audit sprints, code reviews for accessibility, and integrating checks into CI pipelines.

Quick Start

Audit a page for WCAG 2.2 conformance and apply the recommended patterns to fix issues.

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 conformance?

To audit a website for WCAG 2.2 conformance, evaluate text alternatives, keyboard navigation, focus management, semantics, ARIA patterns, and live regions. Apply the provided references and practical code patterns to identify and remediate accessibility barriers across your web content.

What is the best way to implement keyboard accessibility and ARIA patterns?

The best way to implement keyboard accessibility and ARIA patterns is by applying semantic markup and proper focus management techniques. Use the provided practical code patterns and testing workflows to verify keyboard navigation and ARIA usage conform to WCAG 2.2 guidelines.

Can I integrate accessibility checks into my CI pipeline?

You can integrate accessibility checks into CI pipelines using the provided testing workflows and reference checklists. These resources help verify WCAG 2.2 conformance automatically during code reviews, ensuring text alternatives, semantics, and keyboard navigation meet accessibility standards.

How do I fix focus management issues in web apps?

Fix focus management issues by applying the recommended ARIA patterns and semantic markup structures. The provided practical code patterns guide focus management implementation to ensure keyboard navigation and focus states align with WCAG 2.2 accessibility requirements.

Does WCAG 2.2 cover live regions and dynamic content accessibility?

WCAG 2.2 covers live regions and dynamic content accessibility through specific ARIA patterns and semantic markup guidelines. The provided references detail how to implement and test live regions, ensuring dynamic updates are properly announced to assistive technologies.

What ARIA patterns should I use for accessible UI components?

Use ARIA patterns that ensure proper semantics, keyboard navigation, and focus management for accessible UI components. The provided references and practical code patterns detail WCAG 2.2 compliant implementations for common interface elements like live regions and interactive widgets.