aria-live Attribute Values
What you'll learn: How the three values of aria-live control when and how aggressively screen readers announce dynamic content changes.
When you mark a region as a live region (as you learned in lesson 1111), you need to tell screen readers how urgently to announce changes. The aria-live attribute accepts three values that balance keeping users informed against interrupting their current activity.
The Three Values
aria-live="polite" waits for the user to finish their current task before announcing. Think of it like someone waiting for you to finish speaking before adding their thought. This is perfect for status messages, completion notifications, or non-urgent updates.
aria-live="assertive" interrupts immediately, like someone saying "Stop! This is important!" Use this sparingly for critical alerts that need instant attention—errors that prevent form submission, urgent security warnings, or time-sensitive notifications.
aria-live="off" (or removing the attribute) turns off announcements entirely. The content can still change visually, but screen readers won't announce it automatically. Use this when you want to disable a previously active live region.
Choosing the Right Value
Most live regions should be polite—shopping cart updates, search result counts, loading indicators. Only use assertive when user action is truly blocked or safety is at risk. Overusing assertive creates a frustrating experience, like having someone constantly interrupt your conversations.
The default value (when you don't specify) is off, meaning no announcements occur. You must explicitly set polite or assertive to activate live region behavior.
Key Takeaway: Use aria-live="polite" for most dynamic updates, reserve aria-live="assertive" for critical interruptions only, and use aria-live="off" to disable announcements—choosing the right value respects the user's attention and creates a better screen reader experience.