Input Feedback Design pattern

Problem summary

The user has entered data into the system and expects to receive feedback on the result of that submission.


InputFeedback At LinkedIn, feedback is given both inline at the fields as well as at the top of the page upon erroneous data submission.


  • Use when you want to provide feedback to the user upon submitting content to your site.
  • Use when you want to notice your users about errors that happened during form submission.
  • Use when you want to let your users know that everything went as planned upon content submission.


When users submit content to your site via forms, errors in the data the user has provided is bound to happen from time to time. The goal of this pattern is to improve the user experience by minimizing input errors.

A paradigm suited for determining whether errors happened during form submission is whether the data validates. A common way to tell if data validates is to set up rules for each input field in the form that the entered data must pass to validate. Such validation rules can be:

  • Validate presence of content – at least some content must be entered
  • Validate exclusion of content – prohibited values – for instance inserting ‘admin’ as username
  • Validate inclusion of content – data must contain certain data or must be within a certain range
  • Validate acceptance (of for instance terms of service) – often with a checkbox
  • Validate confirmation – two input fields needs to match – seen with for instance passwords
  • Validate format – an email for instance needs an ‘@’ sign and a number of dots
    - for instance that the user must be above 18 year of age.
  • Validate length – A password must in many cases be at least 6 characters long.
  • Validate uniqueness – Many systems only allow one user with a given username

If the data submitted by the user validates, it is good practice to let the user know that everything went as planned. Even better, redirect the user to a page, where he or she can see the newly submitted content in a context.

However, if the data submitted by the user does not validate, an error message should be presented to the user explaining how to correct the data and request for a re-submit. Such an error message should explain that:

  • An error has occurred. Display box at the top of the page (so that the user does not need to scroll the page to find out that an error occured), preferably colored red to signal an error.
  • Where the error occurred. This can be done by listing the fields that caused the error in the error message, as well as highlighting the fields (by changing their colors) that caused the error.
  • How the error can be repaired. Provide information on what needs to be different in order for the field to validate. This can either be listed in the top error box or directly next to the field causing the error.

The visual representation of the input feedback should correspond with the message you want to give. If the submission went successfully, consider letting the user know in a green box. If the message is neutral, a color often used is yellow. If something went wrong, red is often used. But beware – red means danger – is the user experiencing a dangerous situation?


As the user fills out a form on a web page, he or she is conducting the process of converting mental data structured in one way to a written form structured in another way. As all humans do not think alike, we are bound to enter the data in different ways as we try to convert our individually structured data to a shared structure defined by the system.

Data entered in web forms is in this way prone to contain errors, which we must be prepared for in our design. The user must be made aware of the fact that the data entered did not match the structure that we designed for. Using visually distinct feedback notices, the user will be made aware of such errors and how to correct them.


It can be argued that you should focus more on preventing errors before the user submits his or her data than on providing a good error message after data has been submitted. Consider constraining input with select boxes.

Consider the language of your error messages, as these may have an emotional impact on your users. What tone of voice is appropriate for your users?

More example images of the 'Input Feedback' pattern

  • InputFeedback

    When you are not logged-in to basecamp and try to access a page within your project, you are redirected to a login screen with a positive feedback message telling you to log in first. If you enter a mismatching username

  • InputFeedback

    When signing up for a mail at Yahoo, the fields with errors are highlighted and complimenting messages lets you now how to repair the entered data.

  • InputFeedback

    Notice the wording of the amazon error messages: a "slight problem" does not mean "danger". Also notice how the problematic field has been highlighted and complimented with a message letting the user know how to repair the problem.

  • InputFeedback

    When you have confirmed the validity of your e-mail at by clicking a link in a received email, a message with positive feedback is shown. Notice how the check mark signals that the task of confirming your email is done and now out of the way.


Post a comment

Required. Real name or initials only.
Required. Will not be published.
Vote down Vote up
Out of 124 votes, 89.52% like this one.

Is also called...

Related links