This is a direct result of uneducated designers and a lack of
thorough testing.
All of these hurdles are quickly discovered with basic testing and a rudimentary QA
process. Drawn-out user testing and focus groups are rarely needed; simply sticking a few
strangers in front of a computer and asking them to fill out the form will catch 95 percent
of the problems right off the bat. Similarly, expensive code rewriting is often not necessary.
A few tweaks to the markup, the CSS, or the back-end code can remedy anything but
the most debilitating problems.
Common problems (and the errors that love them)
Even the most conscientious corporate entities cannot possibly predict user behavior,
especially the type of behavior that results in setting off a library of error warnings as soon
as the Submit button is clicked. When a user does trip a wire that they??™re not supposed to,
the host entity needs to be firm but kind in guiding them back onto the right path.
There has been a tremendous amount of research and study for errors in software programs,
but the rules are slightly different on the Web. For instance, Microsoft is notorious
for its incredibly poor error handling (???A Runtime Error has occurred.
Pages:
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503