How do we alert users on updates, messages and tasks they need to be aware of

[Febakke]

Draft: We have many different ways of contacting our users. We should create a pattern that both talk about the content of the message. How do we write good alerts to our users. And on what medium. E-mail, phone or other.

[Camulos]

How do we ensure that users notice content that changes after a page has loaded?

Other patterns, such as System Notifications, already cover some of the techniques that can be used, but they have different goals and messaging. It may therefore be useful to create a dedicated pattern for this topic.

Possible names for the pattern:

• Dynamic updates
• Updated content
• Page changes
• Dynamic content

The pattern could cover concrete interaction examples such as a case status page, a search results list with filters, or a file upload with automatic validation. It could then provide guidance on topics such as:

• when a dynamic status change should be announced
• when role="status" is sufficient
• when role="alert" is appropriate
• how to avoid overwhelming screen reader users with frequent updates
• how to handle status badges, progress indicators, and real-time updates
• how to use operating system notifications (if the user has allowed them)

Asynchronous operations

Examples:

• Saving...
• Saved
• Publishing...
• Published

Real-time updates

Examples:

• A caseworker has taken ownership of the case
• Document received
• New comment available

Automatically updated lists

Examples:

• New messages
• New search results
• Activity log updated

Status changes

Examples:

• Processing
• Under review
• Approved

[Camulos]

https://aaardvarkaccessibility.com/wcag-plain-english/4-1-3-status-messages/