Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

This question already has an answer here:

I'm designing a signup form and got stuck in a ux discussion on how to handle user input error handling. Which would you prefer of the following two scenarios? Or is there a third, better option?

Method 1: The submit button is always enabled. When clicking the submit button the form is either posted (if all fields are correct) or the wrong fields are marked for the user to correct.

Method 2: The submit button is disabled from start. When the user interacts with one of the form fields the rest of the fields are marked (with an error or are just highlighted) in order to emphasize that those fields also have to be filled out. When all fields are filled out correctly the submit button is enabled.

share|improve this question

marked as duplicate by Charles Wesley, JohnGB, rk., Matt Obee, Marjan Venema Jul 19 '13 at 8:50

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

    
Thanks for the link I should have done a search. –  Simon N Jul 19 '13 at 16:40

3 Answers 3

up vote 0 down vote accepted

The sooner you let someone know they have an error, the better. Why wait for submit? If the user types an email address that isn't properly structured, mark it invalid as soon as they leave the field. If they activate a required field and then leave it blank, show the "required field" message next to it.

You can get even more active if you chose. If usernames must be unique, check the availability of a typed username after the user finishes typing. It's much quicker feedback than letting them submit only to tell them the name is taken.

I wouldn't disable the submit button because that can make the form look broken, or at least slow down how soon the users gets feedback. Let them click it and you can deliver the feedback messages that much faster.

share|improve this answer

The best design solution would depend on the typical user behaviour for your target group, but here are some things to think about:

Method 1: enabling a action when you know that there are things preventing it from being executed successfully is not good for meeting user expectations. However, generally most sign up forms have the submit button enabled because it needs to be inviting for people to want to sign up.

Method 2: disabling the submit means that the user has to figure out exactly what the problem is in order to enable the action, which can be frustrating.

Without any idea of the information required for sign up, I would suggest that if you made the form very short and simple, then either method is actually fine as long as you address the potential problems.

share|improve this answer

enter image description here

May I suggest this.

First: allow the user to be prompted immediately if they have a wrong format input.

Second: Provide suggestion in cases like username rather than a failure message.

Third: Break the form up into multiple steps (this will enable the user to have a sense of completion and the user will not need to worry if there's input have mistakes once they past this step.)

Forth: Enabled the next button only if the form are completed and error free.

Simon

share|improve this answer
    
Thanks, valid points. I agree with the first three points, on the fourth I'm still leaning towards enabling the submit from start. –  Simon N Jul 19 '13 at 16:45

Not the answer you're looking for? Browse other questions tagged or ask your own question.