Alert dialog box
The typical alert dialog provides information in a separate box to the user, after which the user can only respond in one way: by closing it. Closing an alert dialog will provide access to the original window, which is not available while the alert dialog is presented.
Alert dialogs that block the application are regarded as a bad design solution by usability practitioners, since they are prone to produce mode errors. Also when used as error dialogs, they have been shown to be ineffective in their goals to inform users about an error condition or protect from a destructive operation.
Alerts have several typical uses:
- Error: informs the user than an operation could not continue or complete due to some insurmountable error.
- Warning: alerts that the current course of action could be in some way dangerous or detrimental, often offering the option of not proceeding.
- Info: presents a general notification about a recent event.
- Question: elicits some kind of response from the user, required to complete the current process.
Warning and question alerts typically offer two opposite options to close the dialog ("Allow/Deny", "OK/Cancel", "Yes/No") with the implicit assumption that one will proceed with the paused process that triggered the dialog, and the other one will interrupt the process without action. A good practice in interface design, often included in human interface guidelines, is to label each option with the precise effect that it will have on the process (for example, "Save/Don't save" in a dialog triggered while editing a document with unsaved changes).
The primary reason for using an alert dialogue instead of communicating via the main program window is modality. A typical online form is non-modal. They present to a user many actions that can be performed in any sequence. By contrast an alert dialogue creates a modal state that isolates a particular element of the form and requires a user to address it before proceeding to the next step.
The utility of the alert dialogue is increasing with mobile device penetration, because:
- modal alerts are part of the native functionality of a mobile device, so can be deployed consistently across the device ecosystem as opposed to visual styling techniques that are prone to cross-platform inconsistency
- smaller viewports (screens) make it more difficult to review the main program window looking for errors/information
- smaller viewports have acclimatized users to interacting with a sequence of small screens each with a define action, rather than viewing all contextual info at once on a big screen
A dialog created this way will contain a yellow triangle warning symbol (similar to those found on electrical devices), the text of the warning message, and a single button saying "OK" which will close the window.
Such a dialog also assumes control over the user interface, preventing the user from proceeding with any other task in the application until the dialog window is closed.
Modal alert dialogs are prone to produce mode errors due to their unrequested nature. A study to appear at the Proceedings of the Human Factors and Ergonomics Society showed that when a user dialog appears, the primary goal of users is typically to get rid of them as soon as possible even without any analysis of the causes for the dialog appearance. When asked, users dismissed any dialog box as a distraction from their assigned task.
This is explained by a common complaint about the wording of the message in the alert box, which is often incomprehensible to the user. In applications without proper user-centered design, the developers decide the text of the message, including terms and concepts from the mental model of the programmer, not of the user's view of the world. Since the dialog doesn't work to accomplish the user needs, the common reaction will be to dismiss the alert without further consideration.
Dangerous actions should be undoable wherever possible; a modal dialog that appears unexpectedly or which is dismissed by habituation will not protect from the dangerous action. This problem can be avoided by providing an undo action instead of a warning, or showing the warning in an infobar instead of a dialog.
Another recognized problem is that, as a modal window, the dialog blocks all workflow in the program until it is closed. Users may not recognize that the dialog requires their attention, leading to confusion about the main window being non-responsive, or causing loss of the user's data input. This often happens in data entry forms after an error alert produced by invalid data. The preferred design include changing a visual aspect of the input element to reflect an invalid entry (such as applying a red border), or adding a character such as an asterisk next to the input element that needs to be corrected.
- Java Look and Feel Design Guidelines, second edition.
- Fake popup study sadly confirms most users are idiots Ars Technica, 23 September 2008
- Raymond Chen, The Old New Thing: The default answer to every dialog box is "Cancel"
- Raskin, Jef (2000). The Humane Interface. Addison Wesley. ISBN 0-201-37937-6.
- Aza Raskin, A List Apart: Never Use a Warning When you Mean Undo
- Cooper, Alan (17 March 2003). About Face 2.0: The Essentials of Interaction Design. Wiley. ISBN 0-7645-2641-3.
- Designing Around Dialogs, a presentation about the usage problems of alert dialogs.