New May 5, 2026

A11y Advent Day 10: ARIA

More Front-end Bloggers All from Kitty Giraudel View A11y Advent Day 10: ARIA on kittygiraudel.com

Yesterday we discussed the usage of the aria-disabled and aria-describedby attributes so it’s a good time to talk more about ARIA as a whole. It stands for Accessible Rich Internet Applications. It’s a specification aiming at enhancing HTML in order to convey more meaning and semantics to assistive technologies, such as screen-readers.

The first advice when it comes to ARIA is to avoid using it when possible. It is a powerful tool that can completely change the way a page or widget gets interpreted by assistive technologies, for good or for bad, so it needs to be used carefully. Generally speaking, prefer using native HTML when possible, and only use ARIA when HTML is not enough (such as for tabs or carousels).

There are a lot of handy guides on the internet on building accessible widgets with the help of ARIA; Inclusive Components by Heydon Pickering has to be one of my favorite.

One thing I would like to bring your attention to is the concept of “live” regions. A live region is an area of a page that announces its content to screen-readers as it gets updated. Consider a container for notifications (or snackbars, croutons or whatever yummy thing they are called) or a chat feed.

<div role="log" aria-live="polite">
	<!-- Chat messages being inserted as they are sent -->
</div>

<div role="alert" aria-live="assertive"> <!-- Important notifications being inserted as they happen --> </div>

A few things to know about live regions:

Scroll to top