Confirming what happened.
WHAT EVERY ACTION NEEDS
Confirmation that it occurred, or explanation that it did not.
WHAT FORMS FEEDBACK TAKES
Inline messages, beside what changed Temporary messages, for transient confirmation Dialogs, for anything requiring a decision Status regions, announced to assistive technology
WHAT TO USE FOR SUCCESS
Something brief and unobtrusive, close to the action.
WHAT TO USE FOR ERRORS
Something persistent, near the cause, explaining what to do.
WHY PERSISTENT
An error that disappears before it is read is useless.
WHAT TO ANNOUNCE
Anything appearing without a page load.
HOW
A region marked as live, so assistive technology reads it.
WHAT TO BE CAREFUL WITH
Announcing too much, which becomes noise Messages that disappear too quickly to read Messages placed away from what they refer to
WHAT TO NEVER USE ALONE
Colour, to indicate success or failure.
WHAT TO PAIR IT WITH
Text and an icon.
WHAT TO TEST
Whether a non-visual user knows the action succeeded.
