Bad UX: “Confirm” fields

It’s been a rough few weeks, and I’ve been incredibly uninspired to do anything as of late – but let’s get this bugbear out of the way first.

If you’ve used the Internet for any length of time recently, you’ve probably come across a form where you have to enter – and then confirm entry of – a new password.


In most cases that’s good practice: since you can’t see the contents of a password field (because all the characters are replaced with either asterisks or bullets), the confirm password field is a method of making sure the password you want to use is the right one.

However, some places on the Net take this concept way too far.

Most commonly you’re also asked to “confirm” your email address in this fashion as well, even though the email address you’ve typed is in plain view.


Honestly, I don’t see the point of having two fields in a form to confirm one’s email address, especially when it isn’t hidden like a password field is; it smacks of pretentiousness, as Gordon Ramsay would say. Even if it was a case where sensitive information would be sent to the email address, I would employ another technique – such as a confirmation email, or a CAPTCHA system (which ironically would probably be in the form anyway).

However, this morning I came across an even more pretentious implementation:

Again, I really don’t see the point of having a confirm field for one of the numbers, let alone all three. I think I would be competent enough to enter my number correctly the first time – who in their right mind thought this was a good idea?!

One comment in response...

  1. Lertdarapong don says:

    I’m need same my old one. Thanks.lert

Leave a Reply

Your email address will not be published. Required fields are marked *

15 + eighteen =