It’s pretty standard UX that you shouldn’t give users feedback on field validity until after they have finished typing…
If they re-enter an invalid field to fix if, then the error UI should remove as soon as the input becomes valid.
The current behaviour where an input shows red straight away is a bit offputting
how nice to see creators caring about ux!
you can simply make a field red only when it is invalid AND isn’t focused.
That being said, error prevention is also an important heuristic in UX design. Therefore having a field appear in invalid state as long as it is invalid keeps user attention on the input until they fix it. It helps to have assisting text beneath it to ease the anxiety the red border may cause.
Thanks @hanan1 - this is much better than the default behaviour and easily implementable by applying to the element style.
I also like the suggestion of specific errors to reduce anxiety, so will look to implement and create reusable elements for all my input types.
These are some of the better articles I’ve read on the topic, which i’m trying to consider in my implementation A Complete Guide To Live Validation UX — Smashing Magazine & Inline validation in forms — designing the experience | by Mihael Konjević | WDstack | Medium
Some good conclusions:
Show Errors Immediately If Issues Are Severe
Late Validation Is Almost Always Better
Validate Empty Fields Only On Submit
Reward Early, Punish Late (this is one of my faves, and something I want to try and do… that’s having behaviour around editing erroneous fields)
That’s awesome, thank you for sharing that
This topic was automatically closed after 70 days. New replies are no longer allowed.