skills.rest
allthingslinux
allthingslinuxOFFICIAL
Explore all skills by this author →
GitHub

accessibility-compliance

Audit and implement WCAG 2.2 compliant interfaces with ARIA patterns.

4|Updated Jan 8, 2026
Search Tags:#accessibility#ARIA#WCAG#screen-reader#keyboard-navigation#inclusive-design
One-click install
npx skills add https://github.com/allthingslinux/portal --skill accessibility-compliance-allthingslinux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/allthingslinux/portal/tree/main/.cursor/skills/accessibility-compliance
Command: npx skills add https://github.com/allthingslinux/portal --skill accessibility-compliance-allthingslinux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to building and validating accessible UI components that meet WCAG 2.2, ARIA best practices, and inclusive design principles.

Core Features & Use Cases

  • WCAG 2.2 coverage and ARIA pattern guidance across components.
  • Keyboard navigation & focus management improvements for interactive controls, dialogs, and forms.
  • Screen reader support via semantic HTML, landmarks, and meaningful alt text.
  • Use Case: A development team audits a dashboard and remediates color contrast, missing labels, and inaccessible modals to pass WCAG 2.2 AA.

Quick Start

Run an accessibility audit on the current UI and implement ARIA roles, keyboard navigation, and screen reader labels.

Frequently Asked Questions about accessibility-compliance

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

FAQPage Schema
How do I make my UI components meet WCAG 2.2 AA compliance?▼

To make UI components meet WCAG 2.2 AA compliance, audit your interfaces for correct ARIA patterns, semantic HTML landmarks, and focus management. This ensures interactive controls and forms pass accessibility validation for screen readers and keyboard navigation.

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

Fixing keyboard navigation and focus management in modals requires implementing proper ARIA patterns and focus trapping. This ensures interactive controls remain accessible and screen readers correctly announce dynamic content transitions within dialogs.

How do I add screen reader support for dynamic content announcements?▼

Add screen reader support for dynamic content announcements by using semantic HTML and ARIA live regions. This approach ensures accessibility compliance by allowing assistive technologies to audibly communicate UI state changes and updates to users.

Can I use this approach to audit both web and mobile UI accessibility?▼

Yes, you can audit both web and mobile UI accessibility using this approach. It evaluates interactive controls, form labeling, and dynamic content announcements across platforms to validate inclusive design practices and WCAG 2.2 criteria.

Why does my dashboard fail WCAG compliance despite having alt text?▼

Your dashboard may fail WCAG compliance due to insufficient color contrast, missing form labels, or inaccessible modals. Complete accessibility audits must validate ARIA roles, keyboard navigation, and screen reader compatibility beyond just providing meaningful alt text.

Related Skills

Explore More Software Engineering Skills→
wildbitcawildbitca
1

common-accessibility

Apply WCAG 2.2 and ARIA practices to UI components.

Official
Intermediate
tsuji-tomonoritsuji-tomonori

a11y-testing-manual

Standardize manual accessibility testing for WCAG 2.2 AA compliance.

Community
Intermediate
dthompsonfldthompsonfl

ui-design-system

Define and enforce a reusable UI design system for web interfaces.

Community
Advanced
jmrplensjmrplens

accessibility-audit

Run automated WCAG 2.2 AA accessibility audits with axe-core checks.

Community
Intermediate