Good content is sometimes not enough, the users must reach it so they can see it's good!
Posted: October 19th, 2009 | Author: Adrian | Filed under: Patterns, Usability fail | Tags: buttons, call to action, forms | 1 Comment »
I have update the “All in one seo pack” for wordpress and it insisted that i update the configuration page. I went and checked the page an this is what i have found:
It amazes me how awful is this form made, I think it’s deliberately made so you fuck up. Let’s see why:
1. the “Reset” option in on the right. (I’m not saying the submit must be on the right, but it’s the most common that way)
2. the “Reset” button is bigger and has the same design as the “Update” button. That and 1. makes it most likely to be pressed first
3. both buttons have the same design, hence they are equally important? i don’t think so, the call to action button must be the “update” button. Keep in mind that “Reset” is a destructive action.
4. what’s with the “>>” ? the arrows on the first button point to the second, which kindda’ makes the second the call to action, but the arrows on the second? there’s no extra step, there’s only a form.
Posted: October 19th, 2009 | Author: Adrian | Filed under: Good practices, Patterns, Usability fail | Tags: buttons, labels, search | 6 Comments »
A basic usability test (very cheap also) is logging remote on another person’s computer and watching him/her use the app/website/tool. It’s eye opening.
So I have seen my mother (who is not a computer savy person) hovering the page in search of buttons. When she searches things she doesn’t use the keyboard, she presses the “Search” button, and when that’s not available she gets confused. If the search field has an arrow image background on the right side, she tries to click that arrow and gets puzzled when nothing happens.
So, please use search buttons.
Oh, and please don’t name them “Go” or “>>” or stuff like that, name them “search”, and even put a magnifying glass on them.
Posted: October 19th, 2009 | Author: Adrian | Filed under: Patterns, Usability fail | Tags: forms, inputs, labels | 8 Comments »
DON’T put your form labels inside the inputs.
If i start writing into the input and i forget if i had to insert the username or the email address i have to delete everything, pray to god that the programmer made so the label appears again in the field once I click away, and after that complete the field again. It’s not nice.
Posted: October 7th, 2009 | Author: Adrian | Filed under: Good practices, Patterns | Tags: account, call to action, google, login | No Comments »
A login account sounds simple but it’s not. I’ve been watching Google Account login form for a while and saw the changes they made over time. A login form has to accomplish several things:
– get the registered clients into the system fast
– make unregistered users to register
– convert a visitor into a user
– provide a way to recover an account
In time, the priority of those things changes, ie: at the beginning of a startup you want more new users, the register process must be the first thing a visitor sees in the page, after a while and a solid client base you want those clients to login fast and without issues.
Let’s see some of Google’s login forms now:
Size of the font and spacing changed for better focus on the link.
Here come the blue buttons. Call to action all the way. Unfortunately, I personally had problems logging in, I pressed the “new account” button instead of “login” multiple times. Wasn’t very happy with those. The naming on the button changed a lot, “get started”, “pick a name” or simply “new account”
The next one is the one i can see today on my browser, it really doesn’t have a actual call-to-action button, just a size priority. It’s better.
Note: I’m more than sure it depends on the OS/BROWSER/GOOGLE SERVICE etc.