Skill

role-frontend:accessibility-expert

Audits and implements frontend accessibility for WCAG 2.2 AA compliance, ARIA roles/attributes, keyboard navigation, focus management, screen readers, and automated testing.

HTML

npx claudepluginhub rnavarych/alpha-engineer --plugin role-frontend

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/role-frontend:accessibility-expert

User invocable

Model invocable

Inline context

Default effort

Tool Access

This skill is limited to the following tools:

ReadGrepGlobBash

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

- Auditing or implementing WCAG 2.2 AA compliance

Supporting Files

references/screen-readers-forms-focus.mdreferences/testing-color-motion-legal.mdreferences/wcag-aria-keyboard.md

SKILL.md

33 lines · ~525 tokens

Similar Skills

accessibility-implementation

Implements WCAG 2.1/2.2 compliance, ARIA patterns, keyboard navigation, focus management, and accessibility testing for web components.

12 tools

accessibility-plugin

accessibility

Guides WCAG 2.2 AA compliance for web UIs: keyboard navigation, focus management, ARIA attributes, color contrast, screen readers, and SPA-specific fixes like route focus and announcements.

2 files

saas-design-principles

accessibility

Web accessibility discipline: semantic HTML first, ARIA only when needed, keyboard access always. Invoke whenever task involves any interaction with accessible web content -- writing, reviewing, refactoring, or debugging HTML/CSS/JS for WCAG compliance, ARIA usage, keyboard navigation, focus management, screen reader support, or accessible component patterns.

6 files

frontend

Stats

LanguageShell

Parent stars13

Parent forks1

MaintenanceGood

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Accessibility Expert

When to use

Auditing or implementing WCAG 2.2 AA compliance

Building interactive widgets (dialogs, tabs, comboboxes, accordions) with correct ARIA

Implementing keyboard navigation with roving tabindex or focus traps

Making forms accessible with error messages, live regions, and labels

Managing focus after dynamic content changes (route navigation, modal open/close)

Setting up automated a11y testing in CI with jest-axe or Playwright

Checking legal requirements (ADA, EAA, Section 508, AODA)

Core principles

Native HTML first — <button> beats <div role="button"> every time; ARIA is a last resort

Keyboard before mouse — if it cannot be done with Tab/Enter/Space/Arrow/Escape, it is broken

Focus must go somewhere — every dynamic change (modal, route, delete) needs explicit focus management

Color is never enough — supplement every color signal with text, icon, or pattern

Test with real screen readers — axe catches ~30% of issues; NVDA and VoiceOver catch the rest

Reference Files

references/wcag-aria-keyboard.md — WCAG 2.2 AA/AAA requirements, landmark roles, dialog/tabs/combobox ARIA patterns, states reference table, roving tabindex implementation, focus trap, skip links

references/screen-readers-forms-focus.md — live regions (polite/assertive), sr-only CSS, alt text strategy, accessible form error messages and validation, error summary, focus management after SPA navigation, accordion and tooltip patterns

references/testing-color-motion-legal.md — color contrast ratios, touch target sizing, prefers-reduced-motion, semantic document structure, jest-axe and Playwright automated testing, Pa11y CI config, manual tool comparison, legal requirements table

Accessibility Expert

When to use

Auditing or implementing WCAG 2.2 AA compliance
Building interactive widgets (dialogs, tabs, comboboxes, accordions) with correct ARIA
Implementing keyboard navigation with roving tabindex or focus traps
Making forms accessible with error messages, live regions, and labels
Managing focus after dynamic content changes (route navigation, modal open/close)
Setting up automated a11y testing in CI with jest-axe or Playwright
Checking legal requirements (ADA, EAA, Section 508, AODA)

Core principles

Native HTML first — <button> beats <div role="button"> every time; ARIA is a last resort
Keyboard before mouse — if it cannot be done with Tab/Enter/Space/Arrow/Escape, it is broken
Focus must go somewhere — every dynamic change (modal, route, delete) needs explicit focus management
Color is never enough — supplement every color signal with text, icon, or pattern
Test with real screen readers — axe catches ~30% of issues; NVDA and VoiceOver catch the rest

Reference Files

references/wcag-aria-keyboard.md — WCAG 2.2 AA/AAA requirements, landmark roles, dialog/tabs/combobox ARIA patterns, states reference table, roving tabindex implementation, focus trap, skip links
references/screen-readers-forms-focus.md — live regions (polite/assertive), sr-only CSS, alt text strategy, accessible form error messages and validation, error summary, focus management after SPA navigation, accordion and tooltip patterns
references/testing-color-motion-legal.md — color contrast ratios, touch target sizing, prefers-reduced-motion, semantic document structure, jest-axe and Playwright automated testing, Pa11y CI config, manual tool comparison, legal requirements table

role-frontend:accessibility-expert

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

role-frontend:accessibility-expert

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

Accessibility Expert

When to use

Core principles

Reference Files

Similar Skills

Help us improve

Accessibility Expert

When to use

Core principles

Reference Files