skills.rest
p-o-ke-nae
p-o-ke-naeCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-compliance

Fix accessibility violations in web and mobile interfaces with WCAG 2.2 and ARIA.

Updated May 16, 2026
Search Tags:#accessibility#screen reader#keyboard navigation#wcag#aria#mobile accessibility
One-click install
npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill accessibility-compliance-p-o-ke-nae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/accessibility-compliance
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill accessibility-compliance-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams identify and fix accessibility gaps so web and mobile interfaces work for keyboard users, screen readers, and people with diverse visual, motor, and cognitive needs.

Core Features & Use Cases

  • WCAG 2.2 Guidance: Apply perceivable, operable, understandable, and robust patterns that align with modern accessibility requirements.
  • ARIA and Semantic HTML: Choose native elements first, then add correct ARIA roles, states, and properties when custom behavior needs extra support.
  • Keyboard and Focus Management: Build predictable tab order, visible focus states, skip links, dialogs, menus, and other fully keyboard-operable interactions.
  • Mobile Accessibility: Support VoiceOver, TalkBack, touch target sizing, dynamic text scaling, reduced motion, and accessible gestures.
  • Use Case: Use this Skill when reviewing a checkout flow, fixing an inaccessible modal, or auditing a product UI for WCAG 2.2 compliance before release.

Quick Start

Ask the accessibility-compliance skill to audit the current interface, identify WCAG 2.2 issues, and rewrite the affected components with accessible HTML, ARIA, keyboard, screen reader, and mobile support.

Frequently Asked Questions about accessibility-compliance

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

FAQPage Schema
How do I fix WCAG 2.2 violations in web and mobile interfaces?▼

Fix WCAG 2.2 violations by applying semantic HTML, correct ARIA roles, visible focus states, and screen reader compatibility to remediate forms, dialogs, menus, and touch targets across web and mobile platforms.

What is the best way to implement keyboard navigation and focus management for custom dialogs?▼

Implement keyboard navigation by ensuring predictable tab order, visible focus states, skip links, and fully keyboard-operable interactions for custom dialogs, menus, and tabs using native elements and ARIA support.

Does this accessibility audit support mobile screen readers and touch target sizing?▼

This accessibility audit supports mobile screen readers by verifying VoiceOver and TalkBack compatibility, touch target sizing, dynamic text scaling, reduced motion behavior, and accessible gesture interactions.

When do I need ARIA roles versus native semantic HTML for accessibility compliance?▼

You need ARIA roles when custom behavior requires extra support beyond native semantic HTML, ensuring correct name-role-value exposure for screen readers while prioritizing native elements first for accessibility compliance.

How do I audit a product UI for screen reader compatibility before release?▼

Audit a product UI for screen reader compatibility by checking perceivable, operable, understandable, and robust WCAG 2.2 patterns, verifying name-role-value exposure, and remediating live regions and focus states.

Why does my modal dialog fail keyboard operability and screen reader focus?▼

Modal dialogs fail keyboard operability when they lack proper focus management, visible focus states, and correct ARIA attributes, requiring remediation to ensure predictable tab order and screen reader compatibility.

Related Skills

Explore More Software Engineering Skills→
VMRam95VMRam95

web-design-guidelines

Audit React and HTML code for WCAG accessibility and Vercel design compliance.

Community
Intermediate
aquariuscookaquariuscook

accessibility-testing

Test WCAG 2.2 compliance with axe-core and screen reader validation.

Community
Advanced
dembrandtdembrandt
33

button-states

Define complete visual interaction states for buttons and clickable elements.

Official
Intermediate
veerababumanyamveerababumanyam

accessibility

Validate UI components against WCAG 2.1 AA accessibility standards.

Community
Basic