Lars Damgaard
strategic user experience designer
December 15th 2014

Input validation is still an ambiguous design pattern

Recently I had to design something of a digital design classic: form input validation. In the early days of the web, notifying the user that the input he or she had typed was erroneous, was handled by a javascript alertbox. It would even make a nasty sound by default on windows computers as far as I remember. In terms of user experience, it was pretty bad. Luckily, a lot has happened since.

We now have validation that works via ajax and reacts upon user input as the user types and often also lets the user know that “things went well” and not only that there were a number of errors upon submitting the form.

Even though the design pattern of input validation has matured, I still see quite some ambivalence from a designer’s perspective:

Starting from scratch

Even though almost all sites use input validation at some point, it seems that this design pattern is re-interpreted over and over again – the only thing that we seem to agree on is that validation should happen before submitting the form (when that is plausible) and that it should respond quickly to user input as opposed to old-fashioned server side validation. Apart from that, each designer (myself included) has a tendency to start more or less from scratch every time.

Pattern recognition without recognition

Is this a problem? Well, it depends, but if you look at it from a pattern-recognition perspective, it surely is. Users see input forms that look alike on the web all the time, but they can never really know how they behave.

Do you agree or have you seen any good examples of input validation that deserves to define the future of the pattern? Let me know on twitter.

Related to what you were just reading
November 28th 2012

Jesse James Garret on the maturing of user experience design

In an interview with Brian SolisJesse James Garrett, the founder of Adaptive Path and author of The Elements of User Experience talks about user experience design and the way it has shifted from simple interface design towards a more…

Read more







December 2nd 2012

Merry uxmas

A few days ago, I stumbled upon UXMAS which is a user experience advent calendar.  So far, it has enlightened me with Jared M. Spools talk on how the kano model can inspire ux strategy and a rant about the stupid design of many…

Read more







December 26th 2012

Don’t use software for user experience design

When using a computer to build prototypes for user experience design, you are bound to loose yourself in a world of details. At least I often do.

Even though I use tools that are designed for rapid prototyping (whether it’s Axure,…

Read more







March 7th 2016

Working in teams with atomic design using a Sketch template file, symbolic links and Dropbox

I work in a department with two multidisciplinary scrum teams, each team with two designers. We’re currently working on a big project using atomic design. That’s all good.


Sketch is a good tool for atomic design, especially when using a…

Read more