skills.rest
EngOsamaQazan
EngOsamaQazanCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-compliance

Identify and fix WCAG 2.2 and ARIA accessibility gaps in web interfaces.

Updated Aug 27, 2026
Search Tags:#accessibility#wcag#screen-reader#aria#keyboard-navigation#inclusivedesign
One-click install
npx skills add https://github.com/EngOsamaQazan/TayseerOld --skill accessibility-compliance-engosamaqazan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/EngOsamaQazan/TayseerOld/tree/main/.cursor/skills/accessibility-compliance
Command: npx skills add https://github.com/EngOsamaQazan/TayseerOld --skill accessibility-compliance-engosamaqazan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessibility compliance is essential for inclusive user experiences; this guide provides practical patterns and checks to ensure interfaces meet WCAG 2.2 and ARIA guidelines.

Core Features & Use Cases

  • WCAG & ARIA Best Practices: Apply ARIA roles, states, and properties to interactive components to improve compatibility with screen readers and keyboard navigation.
  • Patterns & Checklists: Reusable patterns for modals, forms, navigation, and live regions to ensure consistent accessibility across applications.
  • Use Case: When auditing a web app, use these patterns to fix focus traps in modals, add skip links, and implement meaningful labels for controls.

Quick Start

Audit a sample page for WCAG 2.2 conformance and implement ARIA patterns to improve keyboard navigation and screen reader 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 keyboard navigation and focus traps in web modals?▼

Fix keyboard navigation in modals by applying ARIA roles and focus management to trap focus within dialogs and ensure operability. Reusable patterns guide focus return and restore proper navigation consistency.

What WCAG 2.2 checks should I run during a web accessibility audit?▼

Run WCAG 2.2 accessibility checks for keyboard operability, screen-reader compatibility, color contrast, motion preference handling, and robust error labeling. Apply these checks during audits, design reviews, and implementation across forms and dynamic content.

Do I need ARIA roles for all interactive components to support screen readers?▼

Apply ARIA roles, states, and properties to interactive components to improve compatibility with screen readers and keyboard navigation. Use them alongside native HTML semantics to ensure consistent accessibility across applications.

How do I add skip links and meaningful labels for accessible navigation?▼

Add skip links and meaningful labels by applying inclusive design patterns for navigation and forms. Ensure controls have descriptive labels for screen readers and implement skip links to allow keyboard users to bypass repetitive content.

Can I apply these accessibility patterns to mobile interfaces?▼

These accessibility patterns apply across web and mobile interfaces, especially for forms, dialogs, navigation, and dynamic content. WCAG 2.2 and ARIA patterns ensure keyboard operability and screen-reader compatibility across platforms.

Related Skills

Explore More Design & Creative Skills→
89jobrien89jobrien
4

web-accessibility

Audit web content for WCAG 2.1/2.2 conformance and accessibility issues.

Community
Advanced
bipinksbipinks
3

accessibility-patterns

Apply WCAG 2.1 AA/AAA patterns to improve UI accessibility.

Community
Advanced
pelcherspelchers

ensuring-accessibility

Implement WCAG 2.1 AA-compliant accessibility patterns for web interfaces.

Community
Advanced
tom-xstom-xs

accessibility-selenium-testing

Automate WCAG 2.1/2.2 accessibility audits with Selenium WebDriver and axe-core.

Community
Advanced