Too many error messages will confuse the user. Is there any simple method to overcome validation?
closed as too broad by Bart Gijssens, Andrew Leach, Mervin Johnsingh, Charles Wesley, Code Maverick Mar 4 '14 at 15:32
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Instead of dumping a long list of errors on the user, you should attach each error to it's corresponding field - write the error next to the field or color the field in red and show the error in the hover text or whatever way you like to make the error visually attached to the field.
That way, instead of having to deal with a long list of errors and matching it to a long list of fields, the user can easily treat each field with error separately without being confused.
If you mean how to avoid as much as possible some errors message due to errors of the user, you could use a placeholder to give the user the example.
There's no simple method to overcome validation, but validation can be designed in good or bad ways. If you search this forum you'll find a lot of questions regarding that!
This is one flow I've seen before:
- Form loads with light coloured pre-fill to describe the syntax that should be used to set expectation. This disappears on focus.
- User enters in information.
- Next page contains a message requesting the user to double check their form entry and ONLY shows the fields that were in error.
- Error messages appear on each field on hover.
User cycles through step 3 and 4 until the form is filled correctly.
Apologies, as I can't seem to find the link to this sample but I think that's one approach you could try.