skills.rest
ariesanhthu
ariesanhthuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility-expert

Audits WCAG 2.1/2.2 compliance and fixes accessibility violations in web projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses and resolves web accessibility issues, ensuring compliance with WCAG standards and improving user experience for individuals with disabilities.

Core Features & Use Cases

  • WCAG Compliance: Audits and fixes issues related to WCAG 2.1/2.2 guidelines.
  • ARIA Implementation: Correctly implements WAI-ARIA roles, states, and properties.
  • Keyboard Navigation: Ensures all interactive elements are navigable via keyboard.
  • Screen Reader Optimization: Improves compatibility with screen readers like NVDA, JAWS, and VoiceOver.
  • Use Case: A developer has received feedback that their web application is not usable with a screen reader. They can use this Skill to identify and fix the underlying accessibility violations.

Quick Start

Run the accessibility expert skill to audit the current project for WCAG compliance issues.

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 violations in my web frontend?▼

Audit your frontend project against WCAG 2.1 and 2.2 guidelines to identify accessibility violations, then apply targeted code remediations using automated analysis and file editing tools.

How do I correctly implement WAI-ARIA roles and properties for screen reader compatibility?▼

Implement WAI-ARIA roles, states, and properties by analyzing your HTML structure and applying correct ARIA attributes to optimize compatibility with screen readers like NVDA, JAWS, and VoiceOver.

What is the best way to ensure keyboard navigation works for all interactive elements?▼

Ensure keyboard navigation by auditing your web application to verify that all interactive elements are fully navigable via keyboard, identifying focus issues, and modifying the underlying frontend code for compliance.

Can I automate accessibility testing for my existing web application?▼

You can automate accessibility testing by running an analysis on your current project to detect WAI-ARIA errors, keyboard navigation issues, and screen reader compatibility problems, then automatically generating the required fixes.

Why does my web application receive feedback that it is not usable with a screen reader?▼

Your web application is likely not usable with a screen reader due to underlying accessibility violations such as incorrect WAI-ARIA implementation, missing keyboard navigation, or non-compliance with WCAG standards.

Related Skills

Explore More Software Engineering Skills→
noahwins-ngnoahwins-ng
1

web-design-guidelines

Audit UI components, HTML structures, and CSS patterns against design and accessibility standards.

Community
Intermediate
mahamaneharouna9-cpumahamaneharouna9-cpu

accessibility-expert

Audit web accessibility for WCAG 2.1/2.2 compliance and ARIA errors.

Community
Advanced
calcosmiccalcosmic
9

accessibility

Audit frontend components for WCAG 2.2 AA accessibility compliance.

Community
Advanced
AIPexStudioAIPexStudio
1.2k

wcag22-a11y-audit

Audit live web pages for WCAG 2.2 accessibility compliance.

Official
Advanced