skills.rest
mralexsaavedra
mralexsaavedraCOMMUNITY
Explore all skills by this author →
Website𝕏@mralexsaavedraGitHub

accessibility

Audit web UI behavior against WCAG 2.2 and Lighthouse accessibility guidance.

41|6|Updated Nov 27, 2025
Search Tags:#accessibility#keyboard navigation#wcag 2.2#screen readers#focus management#aria#lighthouse audit
One-click install
npx skills add https://github.com/mralexsaavedra/spotiarr --skill accessibility-mralexsaavedra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/mralexsaavedra/spotiarr/tree/main/skills/accessibility
Command: npx skills add https://github.com/mralexsaavedra/spotiarr --skill accessibility-mralexsaavedra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you identify and fix accessibility barriers so people with disabilities can use your web app effectively, aligning improvements with WCAG 2.2 expectations.

Core Features & Use Cases

  • WCAG 2.2-aligned guidance: Covers the POUR principles and maps common fixes to relevant success criteria (for example: text alternatives, contrast, keyboard access, focus management, and error handling).
  • Practical implementation patterns: Provides copy-ready patterns for keyboard behavior, focus traps, skip links, live regions, and ARIA tab structure.
  • Testing and prioritization: Includes automated (Lighthouse, axe) and manual testing checklists plus an impact-based issue list to help you decide what to fix first.
  • Use cases: Use when conducting an a11y audit, preparing for accessibility compliance reviews, improving screen reader support, or hardening a UI against common WCAG failures.

Quick Start

Ask the accessibility skill to run an audit for your page and recommend the highest-impact WCAG 2.2 fixes (keyboard navigation, focus visibility, contrast, and screen reader announcements).

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit my web page for WCAG 2.2 compliance?▼

To audit your web page for WCAG 2.2 compliance, run an accessibility check against keyboard navigation, focus management, screen reader semantics, and contrast. This process yields prioritized, actionable improvements mapped to POUR principles and conformance targets.

What is the best way to fix keyboard navigation and focus management issues?▼

Fixing keyboard navigation and focus management issues involves implementing practical patterns like focus traps, skip links, and visible focus indicators. These fixes align with WCAG 2.2 criteria to ensure interactive elements are fully accessible via keyboard.

How do I improve screen reader announcements using ARIA and live regions?▼

Improve screen reader announcements by applying correct ARIA semantics and live regions to dynamic content. This ensures state changes and error messages are properly vocalized, meeting WCAG 2.2 text alternative and robustness requirements.

Can I use Lighthouse and axe automated testing for accessibility reviews?▼

Yes, you can use Lighthouse and axe automated testing to identify common accessibility failures. Combine these automated tools with manual testing checklists to verify keyboard behavior, screen reader support, and overall WCAG 2.2 conformance.

How should I prioritize accessibility fixes for interactive web pages?▼

Prioritize accessibility fixes by generating an impact-based issue list that targets high-frequency barriers first. Focus on critical keyboard access, contrast failures, and form error handling to achieve rapid WCAG 2.2 A and AA conformance.

Why does my web app fail form error handling accessibility requirements?▼

Web apps fail form error handling accessibility requirements when errors are not programmatically linked to inputs or lack descriptive text. Fix this by using ARIA attributes and live regions to announce validation errors clearly to screen reader users.

Related Skills

Explore More Design & Creative Skills→
getcrew44getcrew44
358

accessibility-review

Audit web UI against WCAG 2.1 AA and report categorized accessibility issues.

Official
Intermediate
Community-AccessCommunity-Access
387

Keyboard Navigator

Audit keyboard navigation and focus management against WAI-ARIA and WCAG standards.

Official
Advanced
a53alia53ali

accessibility-testing

Test web and mobile applications for WCAG 2.1/2.2 AA conformance using automated tools and manual techniques.

Community
Advanced
HDeiblerHDeibler
6

accessibility-perceivable

Audit UI content for WCAG Principle 1 perceivability requirements.

Community
Intermediate