Posts Tagged ‘usability’

Google Wave

Friday, January 1st, 2010

Google Wave is a promising new form of online correspondence, part email, part IM conference. I recently redeemed my invite and started poking around. The product itself works fairly well and is definitely slick, but it has some usability issues that I’ll come back to later in another post.

The help and feedback areas however, are a nightmare. First, the feeback link doesn’t work. It goes to a survey which has closed, not to an area where you can provide feedback on the beta. The only other place I found to provide usability improvements is the seriously unusable “Product Ideas” area. The Ideas site itself is a good, well, idea, and one that more online providers might want to consider. But functionally, I’m wondering if THAT’s the product that’s actually a beta! 250 characters for usability feedback? Um, not likely in any detail that’s going to help. But even getting around that, it’s useless when those 250 characters generate parse errors when they’re submitted. No special characters. I even removed any ‘ or ” to make sure my entry was entirely alphanumeric. I got it to submit three times out of about ten usability issues I was trying to offer… isn’t getting that kind of feedback kind of the point of extending invitations to users, especially to users like me who work with interfaces and end-users constantly?

Concept to final product – system message icons

Thursday, June 18th, 2009

Two things that all transactional sites have: success messages and error messages. Ideally, these messages will be at the top of the page and be set off in some way through color or other visual cues. Using green and red respectively is the obvious choice, but this poses a problem: people who are color blind will not be able to tell the difference.

Icons are one solution to this problem. If you preface your system messages with distinctive icons, this can serve as a quick visual cue to experienced users as well as distinguishing between types of message for people who are color blind or who use screenreaders (the reader will read off the alt text of the icon, so you can use this to convey a message to screenreaders only).

Icons can be tricky. They have to be small enough not to get in the way but large enough to be recognizable. Making graphics at that size requires pixel perfection and any iconmaker’s path is littered with failed icons. My favorite, lost to the annals of server upgrades, was one particular trash can I was trying to make that when saved at the right side turned into… Cthulhu!

The demands of making your icons small but recognizable mean you have to go into them with a clear concept. I like to pull out my colored pens and brainstorm around the basic shapes that symbolize whatever you’re trying to make an icon for. Picking a symbol can be the most difficult part of the process. For an error, what do you use? The yellow “caution” triangle? An exclamation point? The red “prohibited” bar and circle?

For my current project, I chose a combination of the exclamation point and the caution triangle. A green checkmark was my immediate first choice for the success message. Out come the pens. It’s important not to censor what you’re drawing, just to let the shapes suggest themselves to you the way they want to be drawn. I usually have about five or six different iterations before I sit back and pick a style and form.

My final, chosen drawings ended up like this:

error_draw

success_draw

From here, I usually move into Photoshop. Some people use Illustrator, but I find Photoshop a lot more intuitive. The key to making your icon recognizable is starting big and going bold. Any line that you want to be visible in the smaller icon has to be several pixels thick in the large version, or it will scale to less than a pixel and disappear. You can get an immediate preview of your work by reducing the magnification until the icon is close to its final size. After a bit of consideration for how to get the borders on the triangle and circle, these were my “full size” icons:

error_03success

Note the thicker border on the symbols themselves. This will help them stand out from the background, especially after they’ve been shrunk to:

error35success35

Form Usability and Design

Tuesday, May 26th, 2009

Most of the work I do right now, I can’t post here because it’s proprietary and client-facing only. However, there’s one application, Mortgage Loan App, that’s fairly new and is what we call a “consumer facing” (meaning our clients’ customers) application that I would like to use as an example to discuss usability in forms and other aspects of form design. I’ll be referring back to it quite a bit in the next couple weeks. This copy is our production environment test copy; clients can customize the application with their own logo, colors and contact information.

A few forms topics (will link each when the post is finished, so feel free to bookmark this page to make it easy to find them in the blog):

  1. Label Placement
  2. Row Highlighting
  3. User Flow
    1. Tabbed Interfaces meet the Wizard
    2. Back/Next Navigation
    3. Button Placement
    4. buttons vs input=button vs input=submit
    5. Information breakdown, what’s on which page and why
  4. Why I use unordered lists in fieldsets for my forms
  5. Progressive Enhancement and Usability:
    1. dynamically hiding extra fields when they aren’t needed
    2. Making your form usable even when js and css are turned off by the user
  6. Making it Pretty
    1. CSS file design for multiple templates/themes
    2. Nifty 3d buttons without resorting to graphics
    3. Disabled Submit Buttons in IE and Firefox
    4. IE and empty divs

Must-read websites for UI Designers

Wednesday, May 20th, 2009

We may quibble over exact shades of blue users prefer or how important it is to break our code so we can still support IE6, but here are a few sites I think we can all agree are invaluable resources for both novice and advanced designers. I read these routinely and you should too.

1) Web Pages That Suck — learn good web design by looking at bad web design – Vincent Flanders and the people who submit sites to feature in “The Daily Sucker” deliver stellar advice to web designers through hilarious examples of what not to do.

2) useit.com: Jakob Nielsen on Usability and Web Design – This site is not about design. It’s about usability only and it excels at that. He’s the “Nielsen” part of “Nielsen Norman Group“, a leading usability company whose work you should be paying attention to if you do anything in web design or development.

3) UXmatters: Insights and Inspiration for the User Experience Community – This is a monthly ‘zine, rather than a frequent blog, with a number of contributors. Because of this, their articles often go into greater depth and have more solid references than your average design/UX blog. They also tend to cover more concise topics that may escape a generalist blog (for instance, this month one of their columns deals with using verbs as nouns in an interface).

4) Usability.gov – Yes, there is a government website focused on usability.

5) User Interface Engineering, a consulting firm – There’s a lot of really good information here.

6) No list of websites to read is complete without A List Apart. A List Apart: User Science is a direct link to their UX topics. Another ‘zine which goes in depth on topics you might not find on a more freqently updated blog.