In forms we often see the 'continue' button inactive until all the required fields are complete:


download bmml source – Wireframes created with Balsamiq Mockups

Is this actually a help to the user, or a hindrance?

I imagine the Pro for this is that it's a visual indicator to the user that they haven't finished filling in the form or dealing with errors (because even with inline validation a user won't be informed if they've never actually interacted with a field so won't show any errors for those at that point).

But then the main Con for this (which I've also seen borne out in usability testing) is that users will be confused why they can't click the button.

Is the pattern of disabling the Continue button until validation is complete actually providing a negative user experience?

  • 28
    Personal experience: In 90% of the pages the validation has some annoying bug, where I need to click in all fields again or reload the page just so the dumb button gets enabled! Examples: Login with autofill from browser (JS doesn't recognize autofill and button is disabled until I focus the PW field) Adress validation: Postal-Code is invalid for the current country, I change country, but the postal code field stays red until I click it again... You will probably never get it a 100% right, so don't annoy your users
    – Falco
    Commented Feb 18, 2015 at 10:32
  • 29
    @Falco: That doesn't mean the principle is wrong, only that the implementation often is.
    – André
    Commented Feb 18, 2015 at 14:17
  • 4
    The problem is that most, if not all, websites that I can think of that let you submit invalid information end up refilling only a subset of the information the user had previously entered, whether the entered information is valid or not. In particular, with regards to having to re-enter the password and the password confirmation fields. THAT IS WAY BEYOND ANNOYING and I believe death by firing squad is too good for the developer who decided that is how things should work. So if you are in that camp then lucky for you that I am not the king because your lifespan would be very short:)
    – Dunk
    Commented Feb 18, 2015 at 15:49
  • 2
    @Dunk I think clearing out the password field is a security feature and is built into the 'password' field type though. It's designed to be cleared out on reload. Not sure the full reasoning for that though, but it's not a conscious decision on the UX designer part for it to work like that, it's down to HTML standards.
    – JonW
    Commented Feb 18, 2015 at 15:54
  • 4
    I don't disagree that it shouldn't work that way from the security feature aspect after a submit. Thus, it gets back to the programmer not allowing the operator to submit unless the data is valid. I've had occasions where I submitted 4 or 5 times because the reason for the error wasn't clear enough, having to retype the password twice each time. Now, I don't like if it happens even once. Falco said "don't annoy your users" as a reason for not disabling. I say that enabling users to submit invalid data makes many users WAAAAAAY beyond annoyed. Firing squad becomes a viable option in the moment.
    – Dunk
    Commented Feb 18, 2015 at 18:33

12 Answers 12


Type of the information captured and number of fields required

It really depends on the type and scope of the information you are asking for and the number of fields that need to be filled:

I have tested and used this pattern successfully in login and and password creation. I think because the interface is so simple and the number of fields required limited there was no ambiguity with regard to the information needed to activate the continue button.

(In my opinion) users are generally task focused so getting-on with the task comes first before they get to finalising any task by committing to action.

As an example consider the case of a create password page with specific password requirements (the situation I have designed for). In this particular case I have disabled the continue button until all the rules for the password were fulfilled, the caveat being that the user needed to get visual feedback as they typed their new password and saw their input fulfil all password requirements.

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

source:10 Usability Heuristics for User Interface Design

Below is an excellent example of this approach which also incorporates gamification logic and you can test the real thing here alongside other variations:

enter image description here

Error prevention

As a general rule I try to avoid (where possible) error messages which add to user frustration and erodes their confidence. So instead of displaying an error message by keeping a continue button active I would attempt to actively convey hints and information about the required fields when and where possible.

Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

source:10 Usability Heuristics for User Interface Design

Inline validation: providing error messages in context

Below is another great example of a simple form with disabled button, Fields are validated inline and the disabled button "shakes" to indicate form incompleteness. Also, with regard to your point:

Even with inline validation a user won't be informed if they've never actually interacted with a field so won't show any errors for those at that point

Any interaction with the form translates to either progress (tick) or (inline error message). The only case where this will not work is when the user clicks on "sign up" without providing any information which is highly unlikely/irrational behaviour and you don't have to cater for it.

enter image description here

If you are dealing with longer and more complex forms, it's worth every effort to structure your form by chunking the information required in a meaningful manner and introducing a staged process/wizard or similar pattern if relevant. This will help optimise your design and to keep it focused on error prevention.

Content of error messages

The other area you may need to consider if "Submit" or "Continue button" are enabled is:

Match between system and the real world

This might be an edge case but its worth mentioning nonetheless ; consider a typical login form with login button enabled and the user clicks on login without providing any details, what would the error message tel the user without breaching system security: The simplest message I have seen, read the following: "Invalid username or password"

This is a clear mismatch between what the user has done and what the system feedback to him. So in this specific case I would opt for disabling login button until required fields are filled.

When could a disabled button be used?

The aim of a disabled button is to preempt and prevent error messages and they can achieve this in an optimal manner when:

  1. The form has limited number of fields and Users are able to see at glance which fields are missing.
  2. There is visual emphasis on required fields and clear feedback when each field is filled (Goals that need to be met to activate button)
  3. field labels are short and can be easily scanned, for example name, username, town/city etc which reinforces 1st point.
  4. All fields are mandatory as it offers a clear path for users to activate button and commit to action*.

    *It seems to me that when there are optional fields users might misinterpret what is actually needed to activate the button though I don’t have evidence to support this.

Is the disabled button a hindrance?

It is clearly not. Its a helping hand that embodies an old maxim "Prevention is Better Than Cure" but it does come with caveats and requires weighing some of the factors I have mentioned above and testing it with your target audience to make sure that it does what it is intended to do.

Designing For People not Machines

Error messages punish people for not behaving like machines. It is time we let people behave like people. When a problem arises, we should call it machine error, not human error: the machine was designed wrong, demanding that we conform to its peculiar requirements. It is time to design and build machines that conform to our requirements. Stop confronting us: Collaborate with us.

Source: Don Norman: Designing For People

I guess that the point I am trying to make is that “users” are people just like all of us and we should not underestimate their intelligence and treat them condescendingly:

  • They will Read & understand labels if these are clear, legible and concise
  • They will check for what is needed from them if the form is well structured and inline with what they want to achieve (task-focused)
  • 2
    The password example is good from a UI perspective, but it's important to note that, by that site's own acknowledgement, "these criteria, to reiterate, are suboptimal". For passwords specifically, arbitrary restrictions on what a password must contain are likely to backfire. (E.g. I can't use correcthorsebatterystaple with those requirements in place.)
    – Ajedi32
    Commented Feb 18, 2015 at 20:16
  • 2
    I had a scenario where users had to agree to the terms and conditions by checking a check box before continuing. The instruction text was there, but no one bothered to read it and they couldn't understand why the button was disabled. So I switched it to an enabled button with a Yes/No prompt and that was well received. I think the point is that you want to guide users through the process as much as possible.
    – John
    Commented Feb 20, 2015 at 19:49
  • 2
    I agree with most of this -- the important part is to make sure it's CLEAR to the user WHY The continue button is disabled if you're going to do it that way (which I feel is better than waiting until the user clicks it and then generating an error and making them go back).
    – Doktor J
    Commented Feb 21, 2015 at 20:08
  • 1
    The downside to disabling is accessibility -- if the user has javascript disabled, all your inline validation and more importantly the code that allows you to re-enable the button goes out the window and the form is left useless.
    – Doktor J
    Commented Feb 21, 2015 at 20:10
  • 1
    "Any interaction with the form traslates to either (tick) or (inline error message). The only case where this will not work is when the user clicks on "sign up" without providing any information which is highly unlikely/irrational behaviour and you dont have to cater for it." - Note that this falls foul of the point Falco made in a comment above: "Login with autofill from browser (JS doesn't recognize autofill and button is disabled until I focus the PW field)".
    – AlexC
    Commented Feb 25, 2015 at 13:40

I would have to say that this behavior hinders user experience.

If you've ever read Don't Make Me Think by Steve Krug then you will quickly realize that this pattern is breaking the rule stated in the title.

One might ask, Why is this disabled?

There is no benefit to make a user jump through this hoop.

Basically what I am implying is that the user is greeted with a form which is not action-able and through discovery, or worse yet reading, they will have to figure out how to properly use the form presented to them.

A workaround for this would be to immediately draw attention to required fields but that would send them into a panic as they wonder why they were greeted with a bunch of red errors even though they haven't even touched the form.

Don't stop the user from performing their intended task of hitting the Submit button, it feels good to know that the form let's you try with minimal repercussion. A gentle error message stating "Please review the form errors highlighted in red" will suffice.

Other thoughts:

I am not sure which websites or pages your are frequently seeing this on but a quick glance of the first 10 "Contact Us" website forms found on Google seems to argue against your observation.

My two cents:

If I had to guess then disabling the Submit button has become a default feature of a popular validation plugin and "developers" are simply leaving it as-is.

  • +1 Good answer. When it comes to scanning information is there any research in regards to forms? I've always seen them as more of a focused task with some level of commitment (depending on context of course). It's just all the usability observation and testing I've done I've personally found forms get completed from top to bottom step-by-step, and in most cases filling in optional information.
    – Wander
    Commented Feb 17, 2015 at 17:11
  • 1
    i hate to say but I downvoted this answer and I feel terribly guilty! If you can cite evidence of better quality than the link you provided then I'll reverse that. What would be good would be to see successful submission rates for type A and B forms where A has disabled button and type B has enabled button.
    – colmcq
    Commented Feb 17, 2015 at 17:15
  • to add: the state of the button is more a reflection of the validity of the user's inputted data. If the form validates inline then the argument for having it enabled or disabled becomes irrelevant
    – colmcq
    Commented Feb 17, 2015 at 17:17
  • @colmcq Part of the issue is that you can only validate a field inline that the user has set the focus state on. If there is a required field that the user hasn't even selected before trying to 'continue' then there will have been no inline validation occuring. So the user will not have any feedback as to why the button is disabled, save for the field instructional text against that field they missed.
    – JonW
    Commented Feb 17, 2015 at 17:20
  • 1
    @JonW I like to trigger validation upon hovering the mouse on a pixel located at x=12 and y=-38. I chose them because they are mobile screen friendly coordinates =)
    – MonkeyZeus
    Commented Feb 18, 2015 at 17:34

we often see the 'continue' button inactive

I think this may be false. Read on!

For what it's worth, I'm updating some old research on sign up forms for popular websites at the moment, and have found that quite a small percentage - around 5% or less - disable the Submit button (whether that's the final sign up or a continue type button) until the data is deemed 'valid'.

After studying so many forms, it becomes a noticeable behaviour rather than invisible behaviour, when the submit button is disabled. This is why I think you may feel like you see it more often than you actually do.

There is also the added problem with disabled buttons, that unless the form does a remarkable job of validating the data on-the-fly without distracting the user at the same time, then it prevents the user from being able to see what's wrong with the content.

One site that does this acceptably is for a BBC ID

enter image description here

However, they make it exceptionally clear on-the-fly what is valid and what is not.

enter image description here

Another notable example of a sign up form that disables the button is MailChimp, but they only disable it until the password is acceptable - not the whole form - so you could enter a password and get the button enabled - with no other valid data in the form.

They clearly see the password as something that absolutely has to be right before you can consider submitting the form. The rest of the data is allowed to be validated on submit. They do not disable the submit button for log-in.

The Mailchimp sign up form is, in my opinion, exceptionally good in many ways.

enter image description here

GoDaddy is a third example of a site that disables the submit button. However, here they don't disable the button until the data is all valid - the fields just have to be non-blank - so one letter in each field will do.

Here the disabled button is helping the user to spot missed fields rather than invalid fields.

enter image description here

So in summary:

If you really want to disable the button until all the data is actually valid then the form has to be very short and exceptionally well validated on the fly. A long form will be too unclear as to what is wrong, and the level of validation needed would be overly distracting for all fields.

Doing so would put you in a small minority, especially for full validation - whatever the feeling is that you 'often' see it :)


One should not disable the button

Consider the situation from the user's perspective. Divide users into two groups

  • Those that do not currently believe they can proceed, so are not looking for a way to continue
  • Those who believe they are ready to proceed, and are looking for a way to do so.

For the former group, disabling the "continue" button is merely a visual artifact seen in the corner of one's vision. It is helpful, but no more helpful than any other graphic depicting the state of the form. For these people, a graphic change (such as an arrow that points to the continue button, or a highlighted continue button) is just as meaningful as a button turning from grey to black.

For the latter group, they believe the form is completed. A disabled button lets them know that they're wrong, but does not assist them in identifying what went wrong. They must now scan the entire form which they think is filled out correctly for whatever notation they missed indicating an incomplete section. This misses out on an opportunity to interact with the user. That interaction can help them find the sections of the form that are not fully filled out. Missing out on this interaction turns the form into a puzzle: "the webadmins know you did something wrong, but you have to find it."

Given that there are other ways of handling the graphical hint that a form is complete (I like highlighted buttons myself), and the continue button provides a way for users to ask for assistance, I see no reason to ever disable the button.

  • That's some good logical thinking.
    – JonW
    Commented Feb 18, 2015 at 22:29
  • @JonW: It's just conjecture though. I don't see a single piece of evidence that this is indeed how you can divide up the user group, nor that this is how they really respond.
    – André
    Commented Feb 19, 2015 at 12:08
  • 1
    @André It may not be evidence-based, but as a method of deciding on a course of action to take, a logical approach isn't a bad one to take. Besides, UX is very subjective; being able to rationally take one side and being able to explain your reasoning for it is a good skill to have. As my question seems to be illustrating, people take a 50:50 view of whether disabling the button is a good idea or not. If I decide to go with one way or the other then I'll need some solid reasoning behind it, which I think this post has. Is it correct? I don't know, but it's certainly valid.
    – JonW
    Commented Feb 19, 2015 at 13:16
  • 1
    @André: The entire point of this approach is that I don't have to divide people up. I do make the assumption that you could divide them up into those two groups, so if there's a third possibility, I'm failing to account for that group. The point is that, once you divide them up this way, it suggests that it doesn't matter who is in what group, we support the user no matter what they're thinking. suggesting they feel that way. It's like "If you're happy if the coin comes up heads, and happy if it comes up tails, do you really care if the other guy cheated on the coin toss?
    – Cort Ammon
    Commented Feb 19, 2015 at 15:50
  • 1
    Really like the way you proceed to make a case, logical and methodical :) What you have demonstrated is a well formulated hypothesis that could be part of a usability test. My only issue with this approach is its built on mitigating issues that arise from bad form design ( too many input fields, lack of clarity, among others) The use of disabled button assumes that form design is optimal and is mostly geared towards error prevention. If a form is so long that it generates misunderstanding around what is required and what is not, than the disabled button is really the least of its problems :)
    – Okavango
    Commented Feb 19, 2015 at 20:12

This is a meta answer drawing from the diverse opinions expressed.

If you want to disable the button, you should still check for clicks and give reason why it is disabled. This has two advantages: fewer errors are displayed, and if you for some reason did not previously communicate why the form can not be submitted, you can explicitly do so.

  • Was thinking exactly the same thing, and was just about to post it together with some other thoughts (to make it a full answer), so thanks for saving me the time xD Honestly, per Ammons logic I think disabling the button has no added value, but if you do this is really a good plan. Commented Feb 21, 2015 at 21:22
  • This is generally true IMO. There are technical obstacles. Disabled buttons don't fire click-events. So you have to design an active button as if it was disabled, which is a tedious task when the browser or the OS change the way they render disabled buttons.
    – hgoebl
    Commented Aug 31, 2021 at 11:46

Buttons are meant to be clicked. If user sees a button, he would want to click. Disabled button becoming active only when all the data is filled in that specific form is not a good experience. I would rather tell user ( which i do with the forms i design ) right at the beginning that all the fields are mandatory and you cannot sign up if any of these fields left empty. Your form is not a game where user has to finish the level he is playing to unlock another one. Just a thought :)

  • Your closing line is a very good point.
    – JonW
    Commented Feb 18, 2015 at 10:59
  • While I do agree that a form is not a game,I think your last point could have been more nuanced: Some forms do benefit from Gamification and that does not mean its a game! So this should not be a blanket rule: Gamification techniques such as Endowed Progress Effect has been used successfully in forms. For example,Progress bars in e-commerce which aims at optimising conversion rates.
    – Okavango
    Commented Feb 18, 2015 at 11:24
  • See the problem is very simple, if you are showing a button, then let user click it. Showing a disabled button will only make him thing that there is something wrong with the webpage or it is still loading. Imagine a 50 year old guy wants to sign up. Do you think he will understand why that button is not clickable? Start writing 'Why the Submit....' and check results for yourself :) Commented Feb 18, 2015 at 11:43

A Form's 'Continue' button should be disabled until all required fields have been filled out and have passed validation.

Why? Well it's common sense, really:

Imagine you are a Bank. And you have a simple form setup which allows the transfer of monies from one party to another. You have a 'From which account would you like to transfer money?' field, a 'Recipient' field and an 'Amount to send' field.

If any one of those fields is not filled in, the transfer cannot take place. Therefor, all three fields are mandatory. Without the information from all required fields, there is no way this transfer can take place.

Now, what happens if we make all three fields mandatory, and indicate this to the user, and the user does indeed enter information in all required fields, but they make a mistake in the 'Amount to send' field?

Let's just say that the user entered 0.00.

Well, we can't send $0.00. If the backend is not setup properly to handle cases such as sending zero dollars, what could happen? When the user clicks 'Continue', not only does this cause yourself to lose bandwidth and time, but it also causes your user to lose bandwidth and time. And in Business, time equals money, and if many people are constantly making mistakes, or not entering in details when they should be, you'll effectively be creating way too much overhead for yourself (allowing too many resources to be used) and I bet that this will eventually cause mismatched data at some point.

Also, as a user, not validating a form and allowing me to continue without telling me that something is wrong is very annoying. Especially when the page refreshes and forces me to fill out everything a second time.

  • 4
    Most of these reasons are really technical / business issues rather than user ones though. The user doesn't care if it takes more bandwidth to fill in a form incorrectly than not. And also you can still do client-side validation on initial selection of Continue before any request gets to the server. While I do agree that business requirements and technical restictions need to be considered when making UX decisions, I feel that those restrictions can be worked around in this instance.
    – JonW
    Commented Feb 18, 2015 at 11:03
  • 1
    Fair point, but if you're going to disable the continue button until all fields are complete then how do you inform the user that there is a field they haven't interacted with at all? There'll be no error message and no way to trigger that error. The user would have to re-read the whole form and each field instruction to find that out.
    – JonW
    Commented Feb 18, 2015 at 13:50
  • So if there is a solution to that issue then you may be right and disabling the continue may be a useful option.
    – JonW
    Commented Feb 18, 2015 at 13:52
  • 1
    @Jonw that the main reason why shorter forms could make use of the disabled button (I would say up to 3 fields) and not longer ones as users will be able to view all required information at a glance.The error message is basically the form itself. If you are dealing with much longer forms than a disabled button is most probably not the right solution and you will need to rely heavily on the form narrative and structure to avoid error messages.
    – Okavango
    Commented Feb 18, 2015 at 18:10

I believe there is a middle-ground. A visually disabled button doesn't have to mean that clicking it does "nothing" as suggested. It will logically prevent the user from advancing in the absence of whatever is required to enable that primary action, but there is no reason that clicking it could not present an alert message to the user explaining why it is disabled and how to enable it.

  • 3
    Interesting idea, but what happens if the user sees the 'inactive' button and doesn't even try to click it because it doesn't look clickable?
    – JonW
    Commented Feb 20, 2015 at 8:40

I will keep this short and to the point as most answers are already covering a lot of valid and good areas.

Does it add value?

I am not able to think of a case where the user will/should look at the continue button to know whether he has finished filling in a form. Whenever a user wishes to click the button he believes he has finished the form and directing him to any required actions is necessary at this point. In principle this should already be clear in a well designed form, but the fact that the user believed he was finished proves that this wasn't the case, thus focusing, temporary blinking or in some other way directing the user is a good plan of action.

What about validation that is not synchronous?

One thing that hasn't been covered yet is that a lot of forms are web forms or otherwise internet dependent and not all validation can be instantaneous. To give a typical example a registration form with a username: the username needs to be looked up in the database and if the username is already used the field will require a different username to be inputted. Normally this is an extremely quick look up, but what if the user is for example using mobile internet and just lost his connection or has an incredibly slow connection? With a disabled continue button the user will end up with a filled out form and no button to click on which is comparatively more confusing than clicking a button and waiting for the next page to load which such a user on a poor internet connection will be used to taking a bit longer.

Of course the above can be somewhat prevented if fields that are awaiting validation very clearly show this, but it's not typically done and if all fields are checked live on server side as is increasingly common then this might be just confusing the user: "Why is there a thingy spinning next to my full name?". So, if you wish to do this the only solution I was able to think of was putting a spinner in the disabled submit button whilst validation is running. The only danger of that is that the user might think he submitted the form already by mistake as a disabled button often is associated with a clicked/pushed state.


While designing some webpages, I came to this site to see what others had to say to make some decisions. I've concluded that the best answer is "it depends."

I thought about my own experiences with enabled buttons that do nothing but tell me what I did wrong and, sometimes on a poorly designed webpage, clear everything! I especially find myself annoyed when I'm on a long form and the error is at the top of the page...which I don't see until clicking on the Submit button several times and then scrolling up to the top to see the problem. Plus, not every website makes it clear what's required until the Submit button is clicked. Don't catch me on a bad day with a website that tells me after the fact that I have to enter something!

I think Webpages should be absolutely clear what is required on a form BEFORE I hit a button so that, if I hit the Submit button before entering a required field, I am thinking, duh, I can't believe I missed that, I knew it was required! On the other hand, I have to agree with Jase that I certainly don't want a Submit button enabled on my bank's website until I've entered all the required fields! I use my bank's website more than any other site and the disabled button has never caused me any confusion.

So, my conclusion? If you have an extensive form with multiple fields, some are required, some are optional, clearly mark all the required fields, enable the Submit button and, when the form is submitted with invalid or missing required data, highlight the problem fields and list messages with the errors. If you have a form where all the fields appear on the same page...along with the Submit button, disable the button and clearly indicate what the user needs to do to enable the button. The Submit button can also be enabled; however, either way should work just fine and provide a good user experience....herein lies the beauty of web design...it's up to you! Finally, know which way is more difficult to code as this may also help you make a decision one way or the other when either seems fine...keeping the costs down for the client should always be a consideration.

Oh...and how often does the typical user "disable" their HTML? I'm thinking that is not common and the average user (non-IT) does not even know how to do it so I don't think that is a good enough reason to take it into consideration when designing a user friendly website. If the user is smart enough to disable their HTML, then they should know they have to enable it for the website to be fully functional!! Happy designing! :)


Yes the "Continue" button should be disabled until all required fields are filled out with at least some text (this assumes that the required fields are designated as such to the user in some way). The affordance here is that the system cannot even attempt to continue until it has the required input from the user.

Once the required fields have been filled out, the "Continue" button should immediately be enabled indicating the system has what it needs to attempt to continue.

From there, clicking on the "Continue" button will run the full validation and may return validation messages to the user.

  • You don't really say why it should be disabled though. Can you elaborate?
    – JonW
    Commented Feb 17, 2015 at 20:30
  • Thanks @JonW, I've elaborated a bit. The idea is that the disabling of the continue button is a subtle validation in itself, and can quickly let the user know whether or not they have filled out the minimum required fields to be able to attempt to continue.
    – landonz
    Commented Feb 17, 2015 at 20:50
  • This works for short forms where there's only 1-3 fields, but it disabling the submit button in a long form with multiple fields will be an issue. The user would have to try to figure out which fields are required to enable the button.
    – M Bo
    Commented Jul 9, 2021 at 17:57

I think it's bad to disable it when it comes to native HTML form constraint validation. It takes away all usability out of form validation leaving you with just the validation.

Taken this simple form for example, when you fill something in to field a and press enter, nothing happens. You don't get any visible feedback. You don't know what is required by just looking at the visual UI.

  <input type="text" name="a" required>
  <input type="text" name="b" required>
  <input type="submit" disabled>

Where as if you would have the button enabled

  <input type="text" name="a" required value="sometext">
  <input type="text" name="b" required>
  <input type="submit">

Now if you where to press enter after having entered something on field a you get a popup and the input field also gets focused

enter image description here

Having a perfectly structured form validation without disabling the continue button

  • You wouldn't need any javascript
  • The page would not reload (thus saving bandwidth)
  • You get good detailed feedback in your own language for what is wrong (talking numbers with step, min max added to it - you get something like: "enter a valid number, the two closest, valid numbers are x, y")
  • The erroneously filled field also gets focused
  • Doesn't make a user confused as to why they can't click it, in fact it's the opposite you now know what is wrong with the form

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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