5 Common Form Error Design Mistakes to Avoid

Showing an error before the user finishes typing

If someone has only started entering their answer, showing a format error immediately can be too early.

For example, a user may type the first letter of an email address and already see an error saying the format is invalid. Give people enough time to finish their answer before showing a format error.

Showing the error somewhere else

An error message can be easy to miss when it appears far away from the field that caused it.

If the message is above the form while the relevant input is several screen lengths further down, the user has to find the problem themselves. Place the explanation beside the affected input or link the message to it.

Making the message too vague

An error message should tell the user what they need to correct.

Vague language leaves people guessing. Instead of only indicating that something is wrong, explain the specific correction that is needed.

For example, if an email address is missing an @ symbol, the message can tell the user that the email address must contain one.

Keeping the error after it has been corrected

Once the user changes the input, the form should check the affected rule again.

If the corrected value now passes, remove the error message. Leaving the same error visible after the problem has already been fixed can make it unclear whether the correction worked.

Clearing the whole form because of one error

When one field contains an error, keep the answers the user has already entered, including the rejected value.

This gives them the opportunity to update the affected field instead of having to enter everything again.

Remember that the server can still say no

A form can pass its checks, and the process can still fail. Account creation, for example, may fail because the service is temporarily unavailable.

In that situation, keep the user's input and allow them to try submitting the form again.