Accessible Rich Internet Applications (ARIA)
ARIA is a suite of web standards that adds roles, states, properties, and relationships so custom interfaces can expose meaning to assistive technologies.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/aria/
01What it means
Accessible Rich Internet Applications (WAI-ARIA or ARIA) defines semantics that browsers map into accessibility APIs. It can describe custom widgets, live regions, landmarks, and dynamic states when native HTML is insufficient. ARIA changes accessibility-tree information; it does not automatically add keyboard behavior, focus handling, styling, or functionality.[1][2][3]
- 01Interaction purposeWhat the component must mean and do
- 02Native HTML firstUse built-in semantics and behavior
- 03Identify semantic gapChoose an established ARIA pattern
- 04Implement whole patternRole, name, state, focus, keyboard
- 05Synchronize + testVisible state, accessibility tree, real AT
ARIA changes accessibility-tree information; it does not automatically add keyboard behavior, focus handling, styling, or functionality.
02Why it matters
Modern interfaces often introduce behavior beyond basic documents. Correct ARIA can make those interactions perceivable to assistive technology, while incorrect roles or states can override accurate native semantics and create a confident but false representation.
03When to use it
Use semantic HTML first. Add ARIA only when required semantics or relationships are absent, following an established authoring pattern and tested behavior. Avoid recreating a native control merely for visual customization.
04How it works
- Choose the native HTML element whose built-in semantics and behavior most closely match the interaction.
- Identify the remaining semantic gap and select an established ARIA pattern rather than isolated attributes.
- Implement the required role, name, states, properties, relationships, focus, and keyboard interaction together.
- Update programmatic states whenever visible or behavioral state changes.
- Inspect the accessibility tree and test with browsers, keyboards, and representative assistive technologies.
05A practical example
A design system uses native button and disclosure elements wherever possible. For a custom tree view with no equivalent native element, the team follows the ARIA pattern, implements arrow-key navigation and selection, exposes expansion state, and tests combinations of browsers and screen readers.
06Where it breaks
ARIA support varies across browser and assistive-technology combinations, and conformance to a pattern does not guarantee usability. Semantics can become stale when application state changes, while overuse often makes native controls less reliable.
Common mistakes
- Adding a role without implementing its required keyboard behavior.
- Using aria-label to replace useful visible labels.
- Applying ARIA where a native element already provides semantics and behavior.
- Failing to update aria-expanded, aria-selected, or other states when the UI changes.