accessibility-expert

Identify WCAG and ARIA accessibility issues on web interfaces and propose remediation.

218|14|Updated Apr 5, 2025
One-click install
npx skills add https://github.com/cin12211/orca-q --skill accessibility-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-expert
Source: https://github.com/cin12211/orca-q/tree/main/.agent/skills/accessibility-expert
Command: npx skills add https://github.com/cin12211/orca-q --skill accessibility-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility issues in web interfaces lead to barriers for users with disabilities. The Accessibility Expert skill helps teams identify WCAG 2.1/2.2 violations, ARIA misconfigurations, keyboard navigation gaps, and screen reader challenges, guiding rapid remediation.

Core Features & Use Cases

  • Audits & guidance: Detect WCAG/ARIA violations across content, forms, navigation, and dynamic widgets, and provide actionable remediation steps.
  • Inclusive design workflows: Assist designers and developers to implement accessible components, landmarks, and keyboard interactions during development and QA.
  • Use Case: When shipping a new UI, run checks to surface accessibility hotspots, generate a prioritized fix plan, and track improvements.

Quick Start

Run the accessibility-expert against a page to surface issues and generate a remediation plan.

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 interface for WCAG and ARIA accessibility violations?

To check web interface accessibility, audit frontend components against WCAG 2.1/2.2 and ARIA standards to detect issues in content, forms, navigation, and dynamic widgets, then generate a prioritized remediation plan.

What is the best way to fix keyboard navigation gaps for screen reader users?

Fixing keyboard navigation involves identifying interaction gaps and ARIA misconfigurations, then applying remediation steps to implement accessible landmarks and keyboard interactions for screen reader compatibility.

How do I integrate accessibility testing into my frontend development and QA workflows?

Integrate accessibility testing by applying checks during development and QA to surface violations, generate fixes for inclusive design workflows, and track improvements across content pipelines.

Can I use this to generate a prioritized fix plan when shipping a new UI?

Yes, when shipping a new UI you can run accessibility checks to surface hotspots, generate a prioritized fix plan for WCAG and ARIA issues, and track remediation improvements.

Does this accessibility audit tool require any specific testing dependencies or components?

No specific dependencies or components are required to run the accessibility audit; it applies common accessibility tooling and checks to evaluate frontend components and content workflows directly.

Why does my dynamic widget still fail automated accessibility checks after adding ARIA?

Dynamic widgets fail automated checks when ARIA is misconfigured or keyboard navigation is incomplete; surface these specific violations and apply documented remediation steps to satisfy best-practice guidance.