skills.rest
themewagon
themewagonOFFICIAL
Explore all skills by this author →
WebsiteGitHub

accessibility

Identify and fix UI accessibility gaps to meet WCAG 2.1 AA standards.

1|Updated Apr 20, 2026
Search Tags:#accessibility#a11y#wcag#lighthouse#contrast#keyboard#aria
One-click install
npx skills add https://github.com/themewagon/astrodeck --skill accessibility-themewagon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/themewagon/astrodeck/tree/main/.claude/skills/accessibility
Command: npx skills add https://github.com/themewagon/astrodeck --skill accessibility-themewagon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility gaps in UI can prevent users with disabilities from effectively interacting with software. This skill provides systematic guidelines and patterns to ensure interfaces are perceivable, operable, and understandable.

Core Features & Use Cases

  • ARIA patterns, focus management, and skip links to improve keyboard navigation.
  • WCAG 2.1 AA-compliant checks for contrast, semantic markup, and alt text.
  • Guidance for integrating accessibility reviews into design and development workflows.

Quick Start

Audit your UI project for accessibility issues and apply ARIA patterns and color-contrast improvements.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I fix WCAG 2.1 AA compliance gaps in my web UI components?▼

WCAG 2.1 AA compliance requires addressing interactive controls, semantic markup, and color contrast. Systematic ARIA role implementation and keyboard navigation checks ensure interfaces are perceivable and operable for users with disabilities.

How do I improve keyboard navigation using ARIA patterns and focus management?▼

ARIA patterns improve keyboard navigation by managing focus across interactive elements. Implementing skip links and proper ARIA roles ensures users can effectively navigate web applications without relying on a mouse.

What's the best way to pass Lighthouse accessibility criteria for color contrast and alt attributes?▼

Lighthouse accessibility criteria evaluate proper alt attributes, semantic markup, and color contrast. Auditing UI projects to verify contrast ratios and adding missing alt text ensures interfaces meet perceivable content standards.

Does this accessibility audit approach work for interactive web application controls?▼

This accessibility audit applies directly to interactive controls, navigation, and content across web applications. It systematically identifies gaps in ARIA roles and keyboard operability to ensure interfaces are understandable.

When do I need to implement skip links and semantic markup for UI accessibility?▼

Skip links and semantic markup are needed when UI components lack perceivable structure for assistive technologies. Implementing these patterns ensures keyboard operability and meets WCAG standards for content navigation.

Related Skills

Explore More Design & Creative Skills→
peopleforresterpeopleforrester
3

accessibility-checker

Audit web content for WCAG 2.1 AA accessibility issues and output a prioritized remediation report.

Community
Basic
sdcorejssdcorejs
2

sdcorejs-review-accessibility-angular-portal

Run Lighthouse, pa11y, and axe audits plus Angular-specific accessibility checks.

Community
Advanced
aroidoaroido

accessibility-audit

Audit web components for WCAG 2.1 AA accessibility issues.

Official
Intermediate
RepairYourTechRepairYourTech
6

accessibility

Audit web accessibility against WCAG 2.1 guidelines and provide code examples.

Community
Intermediate