def-asterisk

This Field Is Really Really Required

I’m going to throw it out there – what is the point of non-required fields? Obviously the company that you’re submitting information to doesn’t really need whatever the field is asking for, so why ask for it?

The only time I can see it being necessary is for extra address information – you know, second floor, apartment number, etc. I can’t think of any other time an optional field would be useful (leave a comment if you have ideas).

So marking required fields should really not be necessary either. Best practices suggest that if most of your fields are required, you should instead mark the fields that are optional.

However, if you feel the need to mark your required fields, you really only need one asterisk. But that’s not good enough for H&M. On a contest they ran recently, they decided that you might not notice a field was required unless they used two asterisks:

H&M really really requires fields with two asterisks.

2 replies
  1. pik
    pik says:

    maybe for public, one-time-filled web forms there’s little sense in optional however for admin apps I find uses. I tend to have most fields optional in a form, so that one can insert a new entity in little time. The optional field values, when present, change the default behavior.

    Reply

Trackbacks & Pingbacks

  1. […] fields? Obviously the company that you’re submitting information to doesn’t really need Link – Trackbacks Posted in User experience (UX) | Permalink. ← Great #UX Requires Great […]

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

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

Please prove you are a human being *