skills.rest
calcosmic
calcosmicCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility

Audit frontend components for WCAG 2.2 AA accessibility compliance.

9|1|Updated Feb 1, 2026
Search Tags:#accessibility#frontend#wcag#ux#screen-reader#aria#keyboard-navigation
One-click install
npx skills add https://github.com/calcosmic/Aether --skill accessibility-calcosmic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/calcosmic/Aether/tree/main/.aether/skills-codex/domain/accessibility
Command: npx skills add https://github.com/calcosmic/Aether --skill accessibility-calcosmic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help teams achieve WCAG 2.2 AA accessibility compliance for web and mobile interfaces, providing actionable guidance on ARIA patterns and assistive technology compatibility.

Core Features & Use Cases

  • ARIA patterns and semantic HTML guidance
  • Keyboard navigation and focus management best practices
  • Screen reader testing and accessibility audits
  • Use Case: migrating legacy components to accessible equivalents and validating with assistive technologies

Quick Start

Audit frontend components for accessibility issues and apply ARIA patterns to improve usability for all users.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I make my frontend components meet WCAG 2.2 AA accessibility standards?▼

Meet WCAG 2.2 AA accessibility by auditing frontend components and applying ARIA patterns, semantic HTML, and keyboard navigation best practices to ensure assistive technology compatibility.

What ARIA patterns should I use for keyboard navigation and focus management?▼

For keyboard navigation and focus management, apply standard ARIA patterns and semantic HTML guidance to ensure logical focus order and usable interfaces for screen readers.

How do I migrate legacy web interfaces to be screen reader compatible?▼

Migrate legacy web interfaces to screen reader compatible equivalents by replacing non-compliant markup with semantic HTML and validating the updated components with assistive technologies.

Does this accessibility audit approach work for both web and mobile interfaces?▼

Yes, this accessibility audit approach works for both web and mobile interfaces, providing actionable guidance on ARIA patterns and assistive technology compatibility across component architectures.

What is the best way to test frontend accessibility for screen reader compatibility?▼

The best way to test frontend accessibility for screen reader compatibility is to conduct accessibility audits that validate ARIA patterns and keyboard navigation against assistive technologies.

Related Skills

Explore More Software Engineering Skills→
pingwupingwu
12

frontend-ui-ux

Design accessible, mobile-first frontend UI/UX for modern web apps.

Community
Advanced
BWCbewchanBWCbewchan
5

web-accessibility

Implement WCAG-aligned ARIA patterns and keyboard navigation in web applications.

Community
Intermediate
RSHVRRSHVR
1

elite-accessibility

Apply motion accessibility patterns to CSS and GSAP web animations.

Community
Advanced
sharondevssharondevs

a11y-auditor

Audit web pages for WCAG 2.1 AA violations using live browser checks.

Community
Advanced