Loading State Announcements
You'll learn how to keep screen reader users informed when content is loading or updating dynamically on your page.
When sighted users see a spinner or "Loading..." text, they know to wait. But screen reader users navigating with a keyboard don't automatically get this feedback. Without announcements, they might interact with stale data, assume the page is broken, or simply feel confused about what's happening.
The Core Problem
Imagine clicking a "Load More" button. Visual users see the spinner appear and new content slide in. Screen reader users? Silence. They don't know if their action worked, if the page is processing, or when it's safe to continue.
The Solution Pattern
Use live regions (which you've already learned) to announce loading states at three key moments:
- Loading starts: "Loading more items..."
- Loading completes: "5 new items loaded"
- Loading fails (optional): "Failed to load items"
<div aria-live="polite" aria-atomic="true" class="sr-only">
<!-- JavaScript updates this text -->
</div>
<button id="loadMore">Load More</button>
The aria-live="polite" ensures announcements don't interrupt current reading, while aria-atomic="true" reads the entire update message.
Choosing Politeness Levels
- Use
politefor most loading states (search results, pagination) - Use
assertiveonly for critical errors that need immediate attention
Common Pattern
Start your message generic ("Loading..."), then update with the result ("20 products loaded"). Screen readers will announce the final state, letting users know it's complete.
Key Takeaway: Screen reader users deserve the same loading feedback as sighted users—use live regions to announce when content starts loading, finishes, or encounters errors.