web-a11y-dynamic-ui

Use ARIA live regions for status updates that should not move focus, such as loading, error, and success messages. Move focus only when it improves task flow, and communicate result counts, sort state, and current page semantically and visually.

Use live regions for status updates that users need to hear but that should not interrupt their current position, like filter result counts or background loading states. Move focus only when the update changes the user's task context, such as after pagination or form submission.

Use real table semantics with captions or labels and proper header cells, and expose the sort state on the active header using aria-sort. Tables should represent tabular relationships only, never layout, and interactive controls inside must preserve context.

Pagination must expose the current page and the available movement options, such as next, previous, and page numbers. After navigation, communicate the new page position and updated result range both semantically and visually.

It targets interfaces that update client-side without a full page load. Traditional server-rendered pages with full reloads rely on standard document semantics and page titles instead of live regions and focus management strategies.