Agent WranglersFeedback and dialogs
Confirm finished work in a status message and keep errors where they need fixing. Place focus with care, and let people undo what they delete.
- Required 4
- Recommended 2
Required
Use toasts only to confirm finished work
RequiredUse a toast only to confirm that something worked, such as "Invoice sent". Announce it through a live region, keep it for at least 6 seconds, and pause it while hovered or focused.
Keep errors that need action on screen
RequiredShow an error that people must act on next to its cause, and keep it until it is fixed. Never put it only in a toast that disappears.
Put focus somewhere sensible after every change
RequiredAfter a client-side page change, move focus to the new page's heading and update the title. When the focused element disappears, move focus to the next item, the previous item or the control that opened it.
Let people undo or confirm destructive actions
RequiredFor deletes and other changes that lose data, offer undo when the change can be reversed, and ask for confirmation when it can't. Name the object and the count in both.
Recommended
Keep dialogs for short tasks
RecommendedUse a modal dialog only for a short task that must finish before anything else, such as a confirmation. Give longer tasks their own page with its own address.
Show progress for long actions
RecommendedWhen an action takes longer than 10 seconds, run it in the background, show its progress, and let people leave the screen. Tell them when it is done.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers app interface playbook: https://agentwranglers.se/playbook/app-ui/feedback-and-dialogs.