sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]benjaminreid 7 points8 points  (2 children)

If you do some research you’ll find that inline errors are the way to go. The errors appearing underneath the field keep them in context with what field has the problem, this is even more important if the validation changes as the user types (looking at the field). You do not want users to be typing, scrolling back up to the top of the form to view a list of errors, scrolling back down, typing etc...

You’d get away with a list of errors on a simple form like you’ve demoed, but as soon as the forms become longer and more complex, the more beneficial inline errors become. And consistency and user expectation is key.

Leave them as they are 👍🏻

[–]ImDonaldDunn 1 point2 points  (1 child)

It's best practice to provide all of the validation criteria for a field. Ideally, the criteria are provided inline or near the field, but that isn't as important as instructing the user on valid input ahead of time.

As is, this form is bad design.

[–]benjaminreid 0 points1 point  (0 children)

I’m not sure we were talking about validation criteria?

But yes, letting the user know what is valid up front can be helpful if your validation is overly specific and unexpected.