aria-patterns

Implement accessible ARIA roles, states, and properties for interactive web components.

38|3|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/dylantarre/design-system-skills --skill aria-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aria-patterns
Source: https://github.com/dylantarre/design-system-skills/tree/main/skills/accessibility/aria-patterns
Command: npx skills add https://github.com/dylantarre/design-system-skills --skill aria-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers build accessible interactive components by applying correct ARIA roles, states, and properties to ensure screen reader compatibility and keyboard operability.

Core Features & Use Cases

  • ARIA patterns for common widgets: Button, Toggle Button, Modal Dialog, Dropdown Menu, Tabs, Accordion, Tooltip, Combobox, and more.
  • Focus management & keyboard support: Guidance on focus traps, arrow navigation, and accessible names.
  • Testing & validation: Recommendations for manual and automated checks (keyboard-only navigation, screen readers, and a11y audits).

Quick Start

Implement a modal dialog with proper focus management and keyboard controls using standard ARIA roles and attributes.

Frequently Asked Questions about aria-patterns

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

FAQPage Schema
How do I implement ARIA patterns for custom interactive widgets?

Implement ARIA patterns by applying correct roles, states, and properties to custom interactive components to ensure screen reader compatibility and keyboard operability. This skill provides specific patterns for common widgets like modals, tabs, and dropdown menus.

What ARIA roles and properties are needed for a modal dialog with keyboard operability?

A modal dialog requires specific ARIA roles and properties combined with focus management and keyboard controls. This skill provides standard ARIA attributes and focus trap guidance to ensure the dialog is screen reader compatible and keyboard accessible.

How do I manage focus and keyboard navigation in accessible web apps?

Manage focus and keyboard navigation in accessible web apps by implementing focus traps, arrow navigation, and accessible names. This skill provides ARIA patterns detailing how to handle focus management across dynamic interactive widgets.

Can I get ARIA patterns for common widgets like accordions and comboboxes?

Yes, you can get ARIA patterns for common widgets including Button, Toggle Button, Modal Dialog, Dropdown Menu, Tabs, Accordion, Tooltip, and Combobox. Each pattern includes the necessary roles, states, properties, and keyboard interactions.

How do I test screen reader compatibility and keyboard navigation for dynamic content?

Test screen reader compatibility and keyboard navigation using a provided testing checklist. It recommends manual and automated checks, including keyboard-only navigation tests and a11y audits, to verify accessibility across dynamic content.

When should I apply ARIA states and properties to interactive components?

Apply ARIA states and properties to interactive components when building custom widgets that require screen reader compatibility and keyboard operability. This ensures dynamic content changes are accurately announced and controlled by users.