accessibility-compliance

Evaluate and implement WCAG 2.2 compliant interfaces with ARIA patterns and keyboard navigation.

1.5k|257|Updated Nov 19, 2018
One-click install
npx skills add https://github.com/adobe/spectrum-web-components --skill accessibility-compliance-adobe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/adobe/spectrum-web-components/tree/main/.ai/skills/accessibility-compliance
Command: npx skills add https://github.com/adobe/spectrum-web-components --skill accessibility-compliance-adobe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams building web UIs often struggle to meet WCAG 2.2 requirements across components, leading to inaccessible interfaces and missed compliance deadlines.

Core Features & Use Cases

  • WCAG 2.2 guidance coverage across POUR principles, including perceivable, operable, understandable, and robust interfaces.
  • ARIA patterns, roles, and properties to ensure accessible components and dynamic content.
  • Design-by-default patterns for keyboard navigation, focus management, and screen reader compatibility in both desktop and mobile contexts.

Quick Start

Audit a UI for WCAG 2.2 conformance and apply ARIA patterns to improve accessibility.

Frequently Asked Questions about accessibility-compliance

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

FAQPage Schema
How do I audit a web component for WCAG 2.2 compliance?

Evaluate WCAG 2.2 compliance by auditing web components against POUR principles, verifying keyboard navigation, testing screen reader compatibility, and validating ARIA roles, states, and properties for dynamic content.

What ARIA patterns should I use for accessible keyboard navigation?

Use ARIA roles, states, and properties to implement design-by-default patterns for keyboard navigation and focus management, ensuring dynamic content remains operable and robust for screen reader compatibility across desktop and mobile interfaces.

Does this WCAG compliance guidance cover mobile accessibility scenarios?

Yes, WCAG compliance guidance covers mobile accessibility scenarios by applying responsive interface checks, ensuring focus management, and testing screen reader support across both desktop and mobile contexts for robust user experiences.

Why does my dynamic UI fail screen reader compatibility checks?

Dynamic UIs fail screen reader compatibility checks when ARIA patterns, roles, and properties are missing or misapplied, preventing robust content delivery and disrupting proper focus management during interface updates.

When do I need to apply ARIA roles and properties for focus management?

Apply ARIA roles and properties for focus management whenever building dynamic web components, ensuring operable interfaces by guiding screen readers and keyboard interactions through perceivable state changes and updated content.

What is the best way to ensure robust accessibility checks for responsive interfaces?

The best way to ensure robust accessibility checks for responsive interfaces is to systematically apply WCAG 2.2 POUR principles, validate ARIA patterns, and test keyboard navigation across mobile and desktop breakpoints.