live regions

The output HTML element is an ARIA live region by default.

Many web pages today have their content dynamically changed using Javascript. An example of this is the search page on this blog. When the page is initially loaded, the only content in the section of the page is a search form. But, when you type in a

If you have an interface where content is dynamically updated, and when the content is updated it does not receive focus, then you likely are going to need a...

Recently I wrote a bit on how I’d define a toast component, outlining UX concerns that should be considered if deciding to implement such a messaging mechanism.

Yesterday, we talked about screen readers (and why you should use one). What happens if you have a piece of content that changes dynamically on your page? How do screen readers let the user know that content has changed? For example, imagine you had an input for users to type their name. Below it, you have an element that displays “Hello {user’s name}!” in real time as they type. How does a screen reader user know about the message in the #app element?

Der direkter Draht zum Screenreader: Wie dynamische Änderungen im HTML-DOM live an assistive Technologien kommunizieren werden können

Rough notes on Sara Soueidan's free chapter "Accessible notifications with ARIA Live Regions".