Practice 1
Status messages
Trigger a visual update and test whether it is announced without moving focus.
LESSON 16 OF 20
Modern interfaces change without a full page load. Users need to know what changed without having their current task repeatedly interrupted.
Choose suitable focus and announcement behavior for status, loading, notifications, timeouts, routes, and inserted results.
A new route or dialog may need deliberate focus movement. A background save or result count usually needs an announcement that preserves focus.
Loading indicators should expose that work started and, when useful, that it completed. Animation alone does not provide this information.
Toasts and timeout warnings need enough persistence, priority, and controls for users to understand and act on them.
When results or content are inserted, communicate the update while keeping navigation predictable. Do not force users to rediscover where they were.
Use focus for a genuine change of interaction context and announcements for relevant updates that should not take control away.
Answer every question, then use the forward lesson button to record this lesson as complete. The check is not scored and can be repeated.