There are two places for communicating problems: right above the
form (required) and in line with the specific field in question (optional, but sure nice for
the user).
The error message must appear right above the form. Not only is it contextual to the
actual fields, but it will appear above the fold so that users will see it immediately when
the page loads. Inline errors should appear next to the offending field in addition to the
primary error. These do not have to be too obnoxious??”simple icons or bolding of the label
of the field is sufficient. See Figure 11-7 for a straightforward example of both of these.
Figure 11-7. This fictional example uses several contingency
design techniques to bring attention to the fact that the user
forgot the final m in his e-mail address.
Graphic design. As these messages need to visually pop from the screen, the design is very
important. They have to catch the eye, but not clash with the rest of the site; in other
words, the error message should look designed, as if it were part of an effort to streamline
the experience (which it is).
CONTINGENCY PLANNING
259
11
Chapter 3 stressed the importance of not using color alone to convey important information.
Pages:
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505