ARIA Roles & Attributes Reference
100% LocalComprehensive guide for accessible web development.
A11y Pro Tip
"The best ARIA is no ARIA." Whenever possible, use native HTML elements (like <button> instead of role="button") for built-in accessibility.
A11y Standards
W3C WAI-ARIA 1.2 Compliance
WCAG 2.1 Level AA Reference
Semantic HTML Integration
Search by role name or filter by widget pattern. Each entry shows required attributes and keyboard behavior.
What is ARIA Roles & Attributes Reference?
Frequently Asked Questions
Technical Deep Dive
ARIA Roles & Attributes Reference
Improve your web accessibility with our curated ARIA reference. Look up roles, attributes, and best practices for creating inclusive digital experiences with real code implementation examples.
Pixel-Precise Output
Generates CSS, tokens, or assets that match what your design system expects.
Live Visual Preview
See changes the moment you make them, no copy-paste cycle between tool and IDE.
Copy-Paste Ready
Output is formatted for direct use in stylesheets, Tailwind configs, or Figma tokens.
01 ARIA Attribute Categories
| Category | Definition | Core Examples | Announcement Trigger |
|---|---|---|---|
| Roles | What an element IS | dialog, alert, tab | On Focus / Mount |
| Properties | What an element HAS | aria-label, aria-required | On Focus |
| States | Current interaction state | aria-expanded, aria-busy | On Value Change |
02 Accessible Component Pipeline
<button>, <nav>) before applying ARIA overrides.