Kirabug at 00:12, 10 June 2021

2021-06-10T00:12:11Z

← Older revision		Revision as of 17:12, 9 June 2021
Line 4:		Line 4:
	==TL;DR==		==TL;DR==
	Error messages can occur at four levels of the application:		Error messages can occur at four levels of the application:
	* Field-level~~, in a form~~		* [[Field-level validation and error messaging]]
	* Page level, when validating a form		* Page level, when validating a form
	* Submit / system processing level, when validating a form		* Submit / system processing level, when validating a form

Kirabug: Created page with "Error messaging patterns are the patterns we use to tell a user that they can’t move forward in their current task because of the state of the system. The goal of error me..."

2021-06-09T22:35:07Z

Created page with "Error messaging patterns are the patterns we use to tell a user that they can’t move forward in their current task because of the state of the system. The goal of error me..."

New page

Error messaging patterns are the patterns we use to tell a user that they can’t move forward in their current task because of the state of the system.

The goal of error messaging patterns is not to ensure that we prevent errors, (that’s a different set of patterns) but that when errors occur, the user can recover as quickly as possible to move forward.
==TL;DR==
Error messages can occur at four levels of the application:
* Field-level, in a form
* Page level, when validating a form
* Submit / system processing level, when validating a form
* System flat out quit, no user action caused the problem
Each of these scenarios requires a different form of treatment due to the causes and contexts of the errors.
==Pattern description==
This is a parent page for multiple error messaging patterns.
===Why this is important===
By providing consistent error messaging we:
* Increase the user’s confidence in our applications
* Increase the user’s confidence in their ability to use our applications
* Ensure higher efficiency of using the system (because the user isn’t slowed down by poor messaging or confusion)
* Build trust in users that we know what we’re doing and are transparent about it
===Use when…===
* Error messages are only used for “hard stop” scenarios.
===Do not use when…===
* If the user can proceed but possibly shouldn’t, use a warning.
* If the user can proceed and you have additional information for them, use an info message.
==Additional Resources==
[[Accessible Error Handling]]

[[Category:Design]]

Error Messages - Revision history

Kirabug at 00:12, 10 June 2021

Kirabug: Created page with "Error messaging patterns are the patterns we use to tell a user that they can’t move forward in their current task because of the state of the system. The goal of error me..."