The document discusses ways to improve online forms by making them more minimal, flexible, and user-centered. It recommends organizing forms into logical sections, placing optional fields after required ones, using minimalist and task-focused design, testing different designs, and considering usability and accessibility best practices. The key message is that there is always room for improvement and new testing provides opportunities to create better forms and user experiences.
Frontend Designer & Developer
Work to simplify user interaction through IA, Design, etc
Slideshow up on Slideshare and my site later today
At this point of our progression with developing and using the Web, it's nearly impossible to imagine where we'd be if we didn't have a method of getting information directly from web site visitors and into usable formats.
Forms were originally included in the first versions of HTML in 1990 by Sir Tim Berners-Lee.
Since then, the specifications for them have barely changed. Today, we use them for almost everything. From searching to social networking like Facebook and Twitter to doing our taxes to searching for new web sites.
Since then, the specifications for them have barely changed. Today, we use them for almost everything. From searching to social networking like Facebook and Twitter to doing our taxes to searching for new web sites.
Except for some dramatic (and awesome) additions in HTML5, that is. But today we’ll concentrate on the design of forms, not how awesome the specs are for them.
But in all the years that we've had forms and we've tried getting information from our visitors, have we really progressed far enough in our design and use of them? Yes, but no. Because you're still doing it wrong.
Goal for Presentation: Make you realize that you're doing something wrong and motivate you to do it better. I say better, because there often is no absolute "right way" to do something on the web, but there is almost always a "better way".
Too Long; Didn’t Read
Steve Krug’s “Don’t Make Me Think!”: We don’t read pages; we scan them. We’re in a hurry, we know we don’t need to read everything, we’re good at it.
Please precede your number with a "+" and your country code (leaving off the leading 0 of your number if applicable). Examples: +447781488126 or +12125551212. Need help?
Please precede your number with a "+" and your country code (leaving off the leading 0 of your number if applicable). Examples: +447781488126 or +12125551212. Need help?
Please precede your number with a "+" and your country code (leaving off the leading 0 of your number if applicable). Examples: +447781488126 or +12125551212. Need help?
*Logical* Sections
Getting information is like having a conversation with your site visitor. Imagine having a conversation with someone you just met: the first thing you find out is their name, maybe some general information about where they’re from. Then you get the details. Lastly, you find out how you can contact them later if there’s ever a problem.
Forms should be structured the same way.
Getting information is like having a conversation with your site visitor. Imagine having a conversation with someone you just met: the first thing you find out is their name, maybe some general information about where they’re from. Then you get the details. Lastly, you find out how you can contact them later if there’s ever a problem.
Forms should be structured the same way.
Getting information is like having a conversation with your site visitor. Imagine having a conversation with someone you just met: the first thing you find out is their name, maybe some general information about where they’re from. Then you get the details. Lastly, you find out how you can contact them later if there’s ever a problem.
Forms should be structured the same way.
UCD: Give the interface extensive attention at each step of the process
TF: Focus on a single task at a time
Using a single Call-To-Action minimizes lost conversions
Remove all unnecessary surrounding content
UCD: Give the interface extensive attention at each step of the process
TF: Focus on a single task at a time
Using a single Call-To-Action minimizes lost conversions
Remove all unnecessary surrounding content
UCD: Give the interface extensive attention at each step of the process
TF: Focus on a single task at a time
Using a single Call-To-Action minimizes lost conversions
Remove all unnecessary surrounding content
UCD: Give the interface extensive attention at each step of the process
TF: Focus on a single task at a time
Using a single Call-To-Action minimizes lost conversions
Remove all unnecessary surrounding content
“Numbers only–no dashes or spaces”
Offenders include:
Constant Contact, Best Buy, Costco,
AT&T, California DMV, Consumer Reports, Geico…
Your service just didn’t account for how they normally would right it.
Seriously... it’s pretty easy...
“I would like to use Huffduffer. I want my username to be ___________ and I want my password to be ___________. My email address is ___________.
By the way, my name is ___________ and my website is ___________.”
“Hello, my name is ___________ ___________ and I’m writing you today to learn more about […] I live at ___________ in the 94114 area and I would like o hear back from you soon and learn more about this vehicle. Please call me at ___________ at your earliest convenience.
Confirmed by Vast.com and Kelly Blue Book.
But will it work for everyone?
“I want to make bingo cards! Save them for me under my __________ and I’d like to use this word ___________ as my password.
Doing it wrong. Found a 22% decrease in conversions.
But, they did one thing right: tested it.
Has a lot of visual interaction. Is quite time consuming to comprehend and interact with.
Has a lot of visual interaction. Is quite time consuming to comprehend and interact with.
Has a lot of visual interaction. Is quite time consuming to comprehend and interact with.
Less visual interaction than left aligned with a more clear association of label to input, but this can still be further optimized.
Less visual interaction than left aligned with a more clear association of label to input, but this can still be further optimized.
Less visual interaction than left aligned with a more clear association of label to input, but this can still be further optimized.
Very clear label to input association with a single visual path flowing down the fields. Fastest completion and comprehension times of all previous formatting choices.
To find out more, visit http://uxmatters.com/mt/archives/2006/07/label-placement-in-forms.php
Your CSS must lay your label over your input.
Your CSS must lay your label over your input.
Your CSS must lay your label over your input.
Your CSS must lay your label over your input.
Your CSS must lay your label over your input.
Your CSS must lay your label over your input.
Your CSS must lay your label over your input.
Your CSS must lay your label over your input.
Your CSS must lay your label over your input.
Label context disappears on input focus. How am I supposed to know what I was going to type in here?
Label context disappears on input focus. How am I supposed to know what I was going to type in here?
Label context disappears on input focus. How am I supposed to know what I was going to type in here?
Label context disappears on input focus. How am I supposed to know what I was going to type in here?
Label context disappears on input focus. How am I supposed to know what I was going to type in here?
Label context disappears on input focus. How am I supposed to know what I was going to type in here?
Label context disappears on input focus. How am I supposed to know what I was going to type in here?
Label context disappears on input focus. How am I supposed to know what I was going to type in here?
Label context disappears on input focus. How am I supposed to know what I was going to type in here?
Label context disappears on input focus. How am I supposed to know what I was going to type in here?