accessibility

Name: accessibility
Availability: InStock
Author: nima

Audit web interfaces for WCAG 2.2 AA conformance.

25|3|Updated Jul 14, 2026

Search Tags:#accessibility #a11y #frontend #wcag #keyboard #aria

Ready to run

npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill accessibility-nimadorostkar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/nimadorostkar/Claude-Skills-collection/tree/main/skills/frontend/accessibility
Command: npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill accessibility-nimadorostkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the gap between visual design and functional accessibility, ensuring interfaces are usable by everyone regardless of physical ability or assistive technology usage.

Core Features & Use Cases

WCAG 2.2 AA Auditing: Provides a structured framework to evaluate components against specific success criteria.
Semantic Implementation: Guides the correct use of HTML and ARIA to ensure screen-reader compatibility and keyboard navigation.
Use Case: When building a custom modal or complex form, use this skill to verify focus trapping, keyboard escape patterns, and proper announcement of dynamic content.

Quick Start

Use the accessibility skill to audit the current component code for WCAG 2.2 AA compliance and suggest necessary semantic improvements.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I audit my frontend components for WCAG 2.2 AA compliance?▼

To audit frontend components for WCAG 2.2 AA compliance, evaluate semantic HTML structure, keyboard navigation, and screen-reader behavior against specific success criteria. This process identifies focus management, contrast ratio, and ARIA implementation issues.

How do I implement focus trapping and keyboard escape patterns in a custom modal?▼

Implement focus trapping and keyboard escape patterns in a custom modal by applying proper ARIA roles and semantic HTML. This ensures dynamic content is announced correctly and keyboard navigation remains contained within the interface boundaries.

What is the correct way to use ARIA attributes for screen-reader compatibility?▼

The correct way to use ARIA attributes for screen-reader compatibility is pairing them with semantic HTML elements. This combination ensures dynamic content announcements and fulfills WCAG 2.2 AA requirements for accessible interfaces.

Can I use this approach to remediate automated accessibility scan findings?▼

Yes, you can remediate automated accessibility scan findings by applying structured WCAG 2.2 AA conformance checks. This workflow targets semantic HTML corrections, keyboard navigation gaps, and ARIA implementation errors identified during scanning.

Why does my complex form fail keyboard navigation and screen-reader tests?▼

Complex forms fail keyboard navigation and screen-reader tests due to missing semantic HTML and improper ARIA implementation. Auditing focus management and dynamic content announcements resolves these WCAG 2.2 AA conformance gaps.