skills.rest
yuhle-qug
yuhle-qugCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-expert

Identify and fix accessibility issues in web interfaces using WCAG 2.1/2.2 and ARIA.

Updated Jan 2, 2026
Search Tags:#accessibility#a11y#frontend#wcag#screen-reader#aria#keyboard-navigation
One-click install
npx skills add https://github.com/yuhle-qug/Parking_Management_System --skill accessibility-expert-yuhle-qug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-expert
Source: https://github.com/yuhle-qug/Parking_Management_System/tree/main/.agent/skills/accessibility-expert
Command: npx skills add https://github.com/yuhle-qug/Parking_Management_System --skill accessibility-expert-yuhle-qug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures web interfaces meet WCAG 2.1/2.2, implements proper WAI-ARIA, and optimizes screen reader compatibility so users with disabilities can interact with your product.

Core Features & Use Cases

  • WCAG & ARIA Compliance: Guidance, checks, and patterns to achieve accessible interfaces.
  • Screen Reader & Keyboard Optimization: Improve focus management, landmarks, and descriptive text for assistive technologies.
  • Use Case: A frontend team auditing a dashboard can invoke this Skill to identify ARIA gaps, keyboard traps, and semantic HTML improvements.

Quick Start

Audit a new page for ARIA roles, keyboard navigation, and screen reader hints to surface accessibility improvements.

Frequently Asked Questions about accessibility-expert

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

FAQPage Schema
How do I check my web app for WCAG 2.1 and ARIA compliance issues?▼

Check WCAG 2.1 and ARIA compliance by auditing your web interface to identify missing ARIA roles, keyboard traps, and semantic HTML gaps. This process surfaces actionable accessibility improvements across dashboards and forms.

What is the best way to fix keyboard navigation traps in a frontend dashboard?▼

Fixing keyboard navigation traps involves reviewing focus management and landmarks to optimize keyboard interactions. Auditing your dashboard identifies specific focus barriers and generates improvements for assistive technologies.

How does screen reader optimization work for content-rich web pages?▼

Screen reader optimization works by improving descriptive text, landmarks, and WAI-ARIA attributes on content-rich pages. This ensures users with disabilities can navigate and interact with your product effectively.

Can I use automated checks alongside manual reviews for web accessibility?▼

Yes, you can use automated checks alongside manual reviews to identify accessibility issues in web interfaces. This combined approach supports WCAG 2.1/2.2 compliance and screen reader optimization across frontend projects.

Do I need semantic HTML to pass WAI-ARIA accessibility audits?▼

Yes, semantic HTML is required to pass WAI-ARIA accessibility audits because it provides the foundational structure and roles for assistive technologies. Auditing your pages identifies specific semantic improvements needed for compliance.

Related Skills

Explore More Software Engineering Skills→
nanorepublicananorepublica
61

Frontend Accessibility

Enforce frontend accessibility compliance in HTML, CSS, and JavaScript components.

Community
Basic
esneiderbravoesneiderbravo
1

accessibility-standards

Audit UI accessibility for WCAG 2.2 AA compliance with automated and manual checks.

Community
Intermediate
shwilliamsonshwilliamson

css-standards

Enforce BEM naming, CSS variables, and responsive patterns for CSS/SCSS.

Community
Basic
wredziowredzio

accessibility

Identify and remediate WCAG 2.1 AA accessibility issues in web pages.

Community
Advanced