skills.rest
holger1411
holger1411COMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility

Identify accessibility issues in UI markup and propose WCAG 2.1 AA fixes.

70|14|Updated Dec 18, 2025
Search Tags:#accessibility#a11y#wcag#screen-reader#color-contrast#aria#keyboard-navigation
One-click install
npx skills add https://github.com/holger1411/astrodeck --skill accessibility-holger1411
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/holger1411/astrodeck/tree/main/.claude/skills/accessibility
Command: npx skills add https://github.com/holger1411/astrodeck --skill accessibility-holger1411

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility issues in UI markup can block users with disabilities from accessing content, forcing teams to manually test and iterate to reach WCAG compliance.

Core Features & Use Cases

  • WCAG 2.1 AA alignment with ARIA practices and semantic HTML
  • Keyboard navigation, focus management, and visible focus styles
  • Color contrast checks and screen reader compatibility for components
  • Use case: when shipping a new interactive component like a modal or a nav menu, ensure it is keyboard accessible and properly labelled.

Quick Start

Audit your UI for accessibility issues and implement fixes following WCAG guidance.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I fix color contrast and keyboard navigation issues in my UI markup?▼

Fix color contrast and keyboard navigation issues by auditing your UI markup to identify failures against WCAG 2.1 AA standards. The skill analyzes your HTML and ARIA attributes to propose specific fixes for visible focus styles, screen reader compatibility, and proper button semantics.

What is the best way to ensure my interactive components meet WCAG 2.1 AA compliance?▼

Ensure WCAG 2.1 AA compliance for interactive components by validating semantic HTML and ARIA practices. The skill audits interactive elements like modals and nav menus, verifying they have proper labels, logical heading hierarchy, and complete keyboard accessibility.

How do I add proper ARIA attributes and alt text for screen reader compatibility?▼

Add proper ARIA attributes and alt text by analyzing your UI markup for missing or incorrect accessibility semantics. The skill identifies where screen reader support fails and proposes exact ARIA roles, attribute adjustments, and alt text additions to meet WCAG standards.

Does this accessibility audit check button semantics and visible focus styles?▼

Yes, the accessibility audit checks button semantics and visible focus styles across your components and pages. It evaluates your HTML to ensure buttons have correct semantics and that focus management provides clear visual indicators for keyboard users navigating the interface.

When do I need to audit my UI for heading hierarchy and screen reader support?▼

Audit your UI for heading hierarchy and screen reader support when shipping new interactive components like modals or nav menus. You need this check to ensure users with disabilities can access content, preventing manual testing iterations before reaching WCAG compliance.

Related Skills

Explore More Design & Creative Skills→
CrazyDubyaCrazyDubya

accessibility-auditor

Audit web applications for WCAG 2.1 Level AA accessibility compliance.

Community
Intermediate
JaivishChauhanJaivishChauhan
6

accessibility

Apply WCAG-compliant semantics to portfolio pages for keyboard and screen reader accessibility.

Community
Intermediate
artivillaartivilla

rams

Identify and remediate accessibility and visual design issues in UI components.

Community
Intermediate
warpdotdevwarpdotdev
820

web-accessibility-audit

Audit web pages against WCAG standards using automated tools and manual review.

Official
Intermediate