accessibility-specialist

Audit web interfaces for WCAG 2.1/2.2 Level AA accessibility issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sonyho2715/lee-meadows-saas --skill accessibility-specialist-sonyho2715
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-specialist
Source: https://github.com/sonyho2715/lee-meadows-saas/tree/main/.claude/skills/accessibility-specialist
Command: npx skills add https://github.com/sonyho2715/lee-meadows-saas --skill accessibility-specialist-sonyho2715

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many web interfaces exclude users with disabilities due to missing semantic markup, poor keyboard support, insufficient color contrast, and incorrect ARIA usage; this skill helps teams find, prioritize, and fix those accessibility barriers to deliver inclusive experiences.

Core Features & Use Cases

  • Accessibility Audits: Structured WCAG 2.1/2.2 Level AA checks with severity-based prioritization and remediation plans.
  • Implementation Guidance: Concrete patterns for semantic HTML, ARIA roles, focus management, keyboard interactions, and accessible components such as modals, accordions, and tables.
  • Testing & Verification: Recommendations for automated (axe, Lighthouse) and manual testing (NVDA, VoiceOver) plus a practical checklist for QA and design handoffs.
  • Use Case: Run an audit on a single-page app to fix keyboard traps, add missing alt text, correct ARIA roles on custom components, and verify screen reader reading order.

Quick Start

Ask the accessibility specialist to run a WCAG Level AA audit on the provided frontend codebase and produce a prioritized remediation plan.

Frequently Asked Questions about accessibility-specialist

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

FAQPage Schema
How do I run a WCAG 2.1 Level AA audit on my front-end codebase?▼

To run a WCAG 2.1 Level AA audit, provide your front-end codebase to receive structured checks with severity-based prioritization and a concrete remediation plan for semantic HTML, ARIA, and keyboard interactions.

How do I fix keyboard traps and incorrect ARIA roles in a single-page app?▼

Fix keyboard traps and incorrect ARIA roles in a single-page app by applying the provided implementation guidance for focus management, keyboard interactions, and accessible component patterns.

What is the best way to verify screen reader compatibility and reading order?▼

The best way to verify screen reader compatibility and reading order is using recommended manual testing tools like NVDA and VoiceOver alongside automated checks to validate semantic correctness.

Can I use this to get accessibility testing guidance for QA and design handoffs?▼

Yes, you can use this to get accessibility testing guidance for QA and design handoffs, providing a practical checklist alongside automated and manual verification recommendations.

Does this work with component libraries and design systems for color contrast fixes?▼

Yes, this works with component libraries and design systems to identify and remediate visual color contrast issues, applying WCAG 2.1 and 2.2 Level AA compliance checks.

When do I need to remediate missing semantic markup for web accessibility?▼

You need to remediate missing semantic markup for web accessibility when interfaces exclude users with disabilities, requiring structured audits to find, prioritize, and fix those barriers.