Usability - Misleading Web Forms
Posted on June 6, 2007 under Usability.
How do we determine the usability of a form? Do we design web forms with the user in mind or for the form's sake? Both these questions popped into my head while I was dealing with web forms extensively the last couple of weeks.
I have noticed a rather worrisome trend in the web industry lately, and that is hiding secondary form fields "until they are needed." I do acknowledge the value of such an approach in creating "pretty" form fields. But that's not really coding forms with the user in mind, now is it? Forms should not be coded to look pretty by themselves, forms should be coded with the user in mind.
So what exactly is the value of hiding form fields from the user? We live in a busy world, most of our lives revolve around one thing: <b>time</b>, or the lack thereof, so it is normal for us to allot units of time to our activities. Such as filling in an application form. If it's a paper form you might glance at it and be able to tell how long it may take to fill it in... and plan your time accordingly.
The same should be the case with web forms. But how can that be possible if the form is split on multiple pages or form fields are hidden?
From a usability perspective the form should be an aid for the user. If the form is quite lengthy and there's really no way to reduce the number of fields then show them all. Empower the user and help him better estimate how long it'll take to fill it out by showing all the fields on one screen. Concerned about abandonment? Ask yourself which is better for your brand: abandonment before users start filling in the form or midstream because they are out of time or frustrated with it?
I have noticed a rather worrisome trend in the web industry lately, and that is hiding secondary form fields "until they are needed." I do acknowledge the value of such an approach in creating "pretty" form fields. But that's not really coding forms with the user in mind, now is it? Forms should not be coded to look pretty by themselves, forms should be coded with the user in mind.
So what exactly is the value of hiding form fields from the user? We live in a busy world, most of our lives revolve around one thing: <b>time</b>, or the lack thereof, so it is normal for us to allot units of time to our activities. Such as filling in an application form. If it's a paper form you might glance at it and be able to tell how long it may take to fill it in... and plan your time accordingly.
The same should be the case with web forms. But how can that be possible if the form is split on multiple pages or form fields are hidden?
From a usability perspective the form should be an aid for the user. If the form is quite lengthy and there's really no way to reduce the number of fields then show them all. Empower the user and help him better estimate how long it'll take to fill it out by showing all the fields on one screen. Concerned about abandonment? Ask yourself which is better for your brand: abandonment before users start filling in the form or midstream because they are out of time or frustrated with it?