An ARIA live region is a section of a web page that, when updated dynamically via JavaScript, automatically announces its content changes to screen readers. This allows assistive technology users to be aware of content updates without having to navigate to the updated area. Live regions are created using the aria-live attribute on HTML elements.

Polite (aria-live="polite"): The screen reader waits until it finishes its current announcement before reading the update. This is ideal for non-urgent updates like new chat messages, search results, or status changes.

Assertive (aria-live="assertive"): The screen reader immediately interrupts its current speech to announce the update. Use this sparingly for urgent or critical alerts like error messages, session expiration warnings, or critical system notifications.

aria-atomic="true" tells the screen reader to announce the entire content of the live region when any part of it changes. When set to false (the default), only the specific changed portion is announced. For example, if a live region contains "Page 1 of 10" and only the "1" changes to "2", with aria-atomic="true" the user hears "Page 2 of 10"; with false they might only hear "2".

aria-relevant controls which types of DOM changes trigger announcements. It accepts a space-separated list of tokens:
• additions — New nodes added to the live region
• removals — Nodes removed from the live region
• text — Text content changes
• all — All of the above (equivalent to "additions removals text")
The default value is "additions text". Only change this if you have specific requirements.

role="alert" is essentially equivalent to aria-live="assertive" aria-atomic="true". It's a shorthand for creating an assertive live region. Similarly, role="status" is equivalent to aria-live="polite" aria-atomic="true". Using these roles can make your markup more semantic and readable.

Common use cases include: chat message notifications, form validation errors, search result counts, shopping cart updates, stock tickers, sports scores, loading status indicators, session timeout warnings, and any content that updates asynchronously without a page reload. For non-urgent updates, use polite; for critical alerts requiring immediate attention, use assertive.

Test with real screen readers like NVDA (Windows, free), VoiceOver (macOS/iOS, built-in), or JAWS (Windows, paid). Use this tool to understand the visual behavior and timing differences between polite and assertive regions. Always verify that your live regions: (1) exist in the DOM before updates, (2) have appropriate aria-live values, (3) use aria-atomic correctly, and (4) don't overwhelm users with excessive announcements.

Yes, you can have multiple live regions on a single page. Each operates independently. However, be careful not to create too many assertive live regions, as they can compete with each other and create a confusing experience for screen reader users. Generally, limit assertive regions to truly critical alerts, and use polite regions for most dynamic content updates.