WAI-ARIA

WAI-ARIA, short for Accessible Rich Internet Applications, is a W3C specification that provides a set of attributes to make web content and applications more accessible to assistive technologies. It exists to close a gap: HTML on its own cannot always express the semantics of modern, dynamic interfaces such as custom dropdowns, tab panels, sliders, and live-updating regions. ARIA supplies a vocabulary of roles, states, and properties that describe what those custom components are and how they are behaving.

ARIA works by annotation rather than by changing behavior. A role attribute tells assistive technology what an element is, for example role="tablist" or role="dialog". States and properties, such as aria-expanded, aria-checked, or aria-label, communicate an element's current condition or supply an accessible name. Crucially, ARIA changes only how an element is exposed to the accessibility tree; it does not add keyboard behavior, focus management, or any actual functionality. The developer must still build the interaction.

Because of that, ARIA is easy to misuse, and incorrect ARIA is often worse than none at all, actively misleading screen-reader users. The guiding principle, stated as the first rule of ARIA, is that if a native HTML element or attribute already provides the semantics and behavior you need, you should use it instead of recreating it with ARIA. A native button is more robust than a div with role="button" and hand-written key handling.

For teams building complex widgets, the W3C's ARIA Authoring Practices Guide (APG) is the reference for how to combine roles, states, properties, and keyboard interaction into patterns that actually work. Getting ARIA right is a Robust-principle concern in WCAG terms, and success criteria such as 4.1.2 Name, Role, Value depend directly on correct name, role, and value information being exposed.