3 ms·
Number 9, "Poor Validation," links to a discussion that encourages a fad that I can't get behind: namely, don't disable the submit button. As a long time Mac us
by mariodiana 5y ago
Number 9, "Poor Validation," links to a discussion that encourages a fad that I can't get behind: namely, don't disable the submit button. As a long time Mac user, my understanding has always been that you should not allow the user to do anything you're going to flag an error for.
In the discussion linked to, the example given falls apart in my mind because every one of the fields pictured omits placeholder text, and the placeholder text could easily say "Required." (That's just one solution.)
https://twitter.com/vponamariov/status/1400388907401977857 https://twitter.com/vponamariov/status/1400388907401977857
I could maybe see a counter-argument in the event of a long form. But I would say that long forms may, in most cases, be a bad idea in the first place.
- jakelazaroff 5y agoThe counter-argument is that it’s often unclear why a control is disabled, and an error message can help you figure that out. Even if you label a field “required”, what if the user accidentally skips it without noticing? Specifically highlighting the error might be more obvious than having the user scan the whole form for something that looks wrong.
- Arrath 5y agoIMO the best forms are the one where, if you hit the submit button with something incomplete, it auto-scrolls back to the problem field and highlights it for you.
- Zababa 5y agoIt's funny because the first advice is to not group all the problems together near the button, and then the second advice is to not disabling it because the user could have missed something higher up. It sounds like they're fixing a problem that they themselves created. The other advice seems solid though, I especially appreciate the part about adding an icon for colorblind people.