But! If there’s a button with a form over it, and the button said “login”, wouldn’t that imply that the form would need to be filled, given the user’s past experience with login pages? I mean we could use the little red stars next to the fields to say they’re obligatory, but would that need to be necessary? I’d love your take on it.

Plus, there’s a hidden benefit for rule number 3 — say you had a long register page with a lot of drop downs, form fields and radio buttons. If you happen to miss a field and you didn’t realize it, you’d wonder why the button is still disabled.

But! If it was working like described in rule 3, you’d click on the button, have the page scroll you back up and you’d see you missed something. It provides extra information and feedback for something you missed. Most forms work this way I believe.

I think the frustration would happen in both scenarios, but at least in the second one you’d have the information to quickly continue on the customer journey. 🙂