UX: How not to design a form

Here’s an interesting example of form design for the web. It’s interesting because it’s the wrong way to do it.

Screenshot of form asking for confirmation of email address, but not password

UX Doesn’t Have To Be Difficult

Most of the time UX is just common sense. The designer here has asked for confirmation of an email address. Email addresses are collected in plain-text. The user can see what they typed and, if they typed it wrong, they can go back and correct the issue. So why ask for confirmation? There’s simply no need.

Worse still they haven’t asked for confirmation on the password. The password is obscured while it is typed. The user cannot see what they are typing and, if they make a mistake, will have no way of knowing unless forced to confirm the password.

Please, people of the world, if you’re designing a form for the web employ common sense!

About Matt Lowe

Matt Lowe is a WordPress web designer / developer based in Newbury, Berkshire. After 8 years of doing the nine-to-five for other companies and watching them make the same mistakes over and over he set out in business on his own, forming Squelch Design to help businesses get online and make money.

Sorry, comments are currently closed, pending a redesign of the website.