ARIA
The W3C standard of HTML attributes, such as role and aria-expanded, that tell assistive technology what a custom widget is and what state it is in.
In more detail
ARIA stands for Accessible Rich Internet Applications and is published by the W3C's Web Accessibility Initiative, hence WAI-ARIA. It only changes what assistive technology is told, never how the element behaves: adding role="button" to a div does not make it focusable or respond to Enter. That is why the First Rule of ARIA says to prefer native HTML.
Examples
In the browser: ARIA stands for Accessible Rich Internet Applications. It changes only the accessibility tree, not behaviour or appearance, so you still have to add keyboard handling yourself. The first rule of ARIA is to use a native HTML element instead whenever one exists.<div role="tablist"><button role="tab" aria-selected={true}>A</button></div>Related terms
- First Rule of ARIA — The guideline that you should not use ARIA if a native HTML element or attribute already gives the meaning and behaviour you need.
- ARIA role — The role attribute that tells assistive technology what kind of thing an element is, such as button, dialog, tab or switch.
- accessible name — The text assistive technology uses to identify a control, such as "Delete account" for a button.
- WAI — The Web Accessibility Initiative, the part of the W3C that produces accessibility standards such as WCAG and WAI-ARIA.
- screen reader — Software that reads the screen aloud or sends it to a braille display, used mainly by blind and low-vision people.
- ARIA states and properties — The aria-* attributes that describe an element's current condition or relationships, such as aria-expanded="true" or aria-controls="panel-1".
- live region — An area marked with aria-live whose content changes are announced by screen readers without the user moving focus there.
- accessibility tree — A simplified version of the DOM tree that the browser builds for assistive technology, listing each element's role, name and state.
- accessibility — Designing and building products so that people with disabilities, including those who use keyboards, screen readers or magnifiers, can use them fully.
- locator — An object in a test that describes how to find an element on the page, such as “the button named Submit”.
- W3C — The World Wide Web Consortium, a standards body that publishes web standards such as CSS, XML, WCAG and Trace Context.
- isPending — A true or false value from hooks such as useActionState and useTransition that is true while an action is still running.
- ARIA live region — An element whose text changes are announced by screen readers even though focus is elsewhere, set up with aria-live or roles such as status and alert.
- roving tabindex — A technique where only the active item in a group has tabindex="0" and the rest have tabindex="-1", so the group is one tab stop and arrow keys move between items.
Taught in
- Design Systems Architecture: Foundations, Layers & Taxonomy — Design Systems & Component Engineering
- Headless Architecture: State vs Presentation Separation — Design Systems & Component Engineering
- Actionable Form Primitives: Buttons, Switches & Inputs — Design Systems & Component Engineering
- Modal Dialogs & Alert Dialogs: Accessible Overlay Patterns — Design Systems & Component Engineering
- WAI-ARIA Semantics: Roles, States & Accessible Name Computation — Design Systems & Component Engineering
- Semantic HTML Elements: Landmarks And Structure — Frontend Architecture & Web Platform
- Accessibility Tree, ARIA Roles, States And Live Regions — Frontend Architecture & Web Platform
- MutationObserver: Reactive DOM Watching Without Polling — Frontend Architecture & Web Platform
- End-to-End Testing with Playwright: Multi-Tier Suites — Production Full-Stack Engineering
- Action State: useActionState & Optimistic Form UI — Next.js 15 & Modern App Router Architecture
- Slot Patterns And Headless UI Architecture in React — React 19 & Modern Component Architecture
- useId: Generating Stable Accessible Form Element Identifiers — React 19 & Modern Component Architecture
- Virtualization: Rendering Infinite Datasets Efficiently — React 19 & Modern Component Architecture
- Accessible Headless Primitives: ARIA, Focus, And Keyboard — React 19 & Modern Component Architecture