Course contentsShow
← Web Development
Lesson 1115 of 2,98220. Screen Readers and Assistive TechnologyFree lesson

Status Role for Passive Updates

Using role='status' for non-urgent status messages that don't interrupt the user's workflow.

What You'll Learn

You'll learn how to use role="status" to announce non-urgent information updates that don't require immediate user attention or interrupt their current task.

Understanding Status Messages

When content on your page changes—like a success confirmation, item count update, or progress indicator—you want screen reader users to know about it, but you don't want to rudely interrupt what they're doing. That's where role="status" comes in.

Think of it like a notification light on your phone versus an alarm. An alarm demands immediate attention (that's role="alert"), but a notification light just lets you know something happened when you're ready to check it—that's role="status".

How role="status" Works

The status role is a special type of live region with polite announcement behavior built in. It tells screen readers: "Hey, this content changed, but announce it only when the user pauses or finishes their current activity."

This role has implicit ARIA properties:

  • aria-live="polite" — waits for a natural pause
  • aria-atomic="true" — announces the entire region, not just what changed

When to Use Status

Perfect for:

  • "5 items in cart"
  • "Changes saved"
  • "Loading complete"
  • "3 new messages"
  • Progress updates that aren't critical

Not for urgent errors or warnings—those need role="alert".

Example Structure

<div role="status">
  Your changes have been saved.
</div>

<div role="status">
  Shopping cart: 3 items
</div>

The container should exist in the DOM when the page loads (even if empty), then update its content when needed. The screen reader will politely announce the new content without interrupting the user's current focus or action.

Key Takeaway: Use role="status" for informational, non-urgent updates that should be announced politely without disrupting the user's workflow—it's the considerate way to keep users informed.