accessibility-expert

Identify web accessibility issues and propose WCAG-compliant fixes including ARIA, keyboard navigation, and screen reader compatibility.

Updated Apr 9, 2024
One-click install
npx skills add https://github.com/nhonvo/Powershell --skill accessibility-expert-nhonvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-expert
Source: https://github.com/nhonvo/Powershell/tree/main/antigrafity-config/.agent/skills/accessibility-expert
Command: npx skills add https://github.com/nhonvo/Powershell --skill accessibility-expert-nhonvo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides expert guidance on web accessibility, WCAG 2.1/2.2 compliance, ARIA implementation, screen reader optimization, keyboard navigation, inclusive design patterns, and accessibility testing automation, to help teams build inclusive web experiences and prevent accessibility regressions.

Core Features & Use Cases

  • WCAG-focused evaluation and ARIA implementation guidance to improve accessibility across web apps and design systems.
  • Keyboard navigation and screen reader optimization strategies to ensure usable interfaces for all users.
  • Automated and manual testing recommendations, with concrete steps to validate accessibility improvements in production.

Quick Start

Initiate an accessibility review against your web app, identify violations, and apply fixes to achieve WCAG conformance.

Frequently Asked Questions about accessibility-expert

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

FAQPage Schema
How do I fix WCAG compliance issues in my web app?

Fix WCAG compliance issues by evaluating semantic HTML, proper labeling, focus management, and accessible naming, then applying actionable updates to ARIA implementation and keyboard navigation to achieve WCAG 2.1/2.2 conformance.

What is the best way to implement ARIA roles for screen reader compatibility?

Implement ARIA roles by evaluating semantic HTML structure and applying proper accessible naming to ensure screen reader compatibility. This approach optimizes interfaces for users relying on assistive technologies across modern web apps.

How do I test keyboard navigation for accessibility conformance?

Test keyboard navigation by following automated and manual testing workflows that validate focus management and accessible interactions. This ensures usable interfaces for all users and prevents accessibility regressions in production.

Does this accessibility review apply to design systems and modern web apps?

Yes, this accessibility review applies to modern web apps and design systems. It provides WCAG-focused evaluation and inclusive design patterns to improve accessibility and prevent regressions across your entire component library.

Why does my screen reader announcement not match the visual UI element?

Your screen reader announcement may not match the visual UI due to missing or incorrect ARIA implementation and accessible naming. Evaluating semantic HTML and applying proper labels will resolve these accessibility discrepancies.

When do I need automated testing workflows for web accessibility?

You need automated testing workflows for web accessibility when validating WCAG conformance in production. These workflows provide concrete steps to identify violations, apply fixes, and prevent accessibility regressions across your web app.