aria-live region

Detailed explanation

WCAG 2.1 SC 4.1.3 (Status Messages) requires covered status messages to be programmatically determinable without receiving focus. Live-region attributes and roles are common implementations, but the correct behavior depends on the message and interface.

aria-live="polite" queues the announcement until the user is idle (preferred for non-urgent updates). aria-live="assertive" interrupts whatever the screen reader was saying (reserved for time-critical errors). Two related convenience roles wrap common patterns: role="status" (implicit polite) and role="alert" (implicit assertive).

How this applies to Shopify stores

Cart updates, search-result counts, loading states, and validation messages are candidates for status-message review. AccessComply can surface selected patterns and, where a change is safely source-mapped, present a merchant-approved candidate; choosing status, alert, focus movement, or no announcement requires interaction context and manual testing.

What merchants should check next

Treat this term as a practical audit prompt, not just a definition. Check the storefront pages where the concept shows up in real customer journeys: product discovery, add-to-cart, cart drawer, checkout handoff, account login, and support contact flows. If the issue affects code, verify the rendered HTML and computed browser output after the theme change. If it affects copy or media, keep the merchant-facing wording accurate and easy to maintain.

Primary source: w3.org