Free book online: Search User Interfaces

July 2nd, 2009 by Michael Gaigg

Marti Hearst generously made his upcoming book “Search User Interfaces” available for reading online. He is definitely not a newcomer to the scene and the book for sure not a Best-Of compilation, moreover the book is written in an academic fashion that backs up its theses usability studies, log studies, or some other form of proof (like it!) - like Harry Brignull states: “Caution: actual thought may be required when reading this book.”

Contents: Search User Interfaces

The book has two main parts: search fundamentals (Chapters 1-7) and advanced topics (Chapters 8-12).

0: Preface
1: Design of Search User Interfaces
2: Evaluation of Search User Interfaces
3: Models of the Information Seeking Process
4: Query Specification
5: Presentation of Search Results
6: Query Reformulation
7: Supporting the Search Process
8: Integrating Navigation with Search
9: Personalization in Search
10: Information Visualization for Search Interfaces
11: Information Visualization for Text Analysis
12: Emerging Trends in Search Interfaces
References
Index


Suggested reading:


Search User Interfaces

Marti A. Hearst. Cambridge University Press 2009, Hardcover, 352 pages, $40.00

Good News , , , , , , , , , , , , , , , ,

Design Guidelines: Transactional Email

June 30th, 2009 by Michael Gaigg

Feedback request to change my address

Feedback request to change my address


I usually try to balance positive and negative critique, but sometimes - and especially when I see really bad things - I just cannot help but mention it here as well. Latest ‘incident’ was a harmless email to my local government body with the intent to change my address.

Optimize your webpage to avoid emails

The reason I sent the email in the first place was that I couldn’t find any form or document that would allow me to change my address online.

So, I tried to locate a tab or menu entry called ‘contact’ or similar (no luck), checked the footer (no luck) and eventually found the complete address with generic email (chief-on-duty@government) next to the logo - which showed me once more that users tend to look for certain elements in common places rather than even prominent locations.
Anyway, I figured this email address would do it and I shot my note to change my address. Here is the (automated) response:

Dear mail sender! The employee you have selected is out of office and can be reached again on June 29th, inquires will not be processed.

Wow, now what? Should I send my message again in two days (which I probably will)? Can I trust these guys to fix my address at all? Seems like there is no organization behind it. I have no chance to stop by because I’m out of the country but maybe I need to pick up the phone and call instead, how annoying. No big deal for a simple change of address but this slip can potentially damage your image and seriously reduce trust for other sorts of inquires, right?

Update: Today I received a very nice and personal response telling me that my address was updated. I will in return send a nice and personal note pointing out above issues. Let’s hope for the best.

But now, here are the

Design Guidelines for transactional email

  1. Avoid being mistaken for spam.
  2. Enhance company’s reputation and increase users’ confidence.
  3. Be precise and answer all relevant questions.
  4. Provide recognizable brand name in ‘From’ field.
  5. Add clearly distinguishable transaction to ‘From’ field.
  6. Keep ‘From’ field shorter than 20 characters.
  7. Explicitely relate ‘Subject’ field to a customer-initiated transaction.
  8. Avoid unnecessary message sequences (e.g. transaction confirmation + shipping confirmation; order summary not necessary anymore).
  9. Start the ‘Content’ with the information that matters most.

Solution to my inquiry above

First of all, unless the whole department was moved, closed or is on vacation I would not expect a vacation response mail for an email sent to a generic address. Secondly, automated responses are ok if they state that a human response will follow promptly, usually within 24 hours.

What would have been a better response? Maybe: “Thank you, your inquiry has been received and will be processed by our team within the next couple of days. You will be notified once your request is processed or if we have further questions.” And then some more specific information like contact names with alternative email and/or telephone numbers could follow. Maybe even some links that answer common questions or point the requester to common documents, be creative.

What are your experiences with transactional email?

How do you handle transactional email on your company webpage? What are your experiences? Any lessons learned (the hard way)?

References

Design Guidelines , , , , , , , , ,

The Three-?-stick

June 16th, 2009 by Michael Gaigg

The Three-?-stick is going around … and and so it came around. Björn from the Webzeugkoffer (excellent webdesign blog in German) picked up the stick by answering 3 questions that I will answer now too:

The three questions

Which Editor do you use for (X)HTML and CSS?

I’m using Macromedia Dreamweaver. I’m still stuck at MX 2004, but I really got used to the color coding and other superficial things - it’s like toothpaste, once you are hooked you’ll never change again (don’t ask for the trade pls).

…and notepad ;)

Which little tool became a true time saver for you?

Can’t live without Firebug - seriously, can’t live without it. That’s not a little tool? Ok, what about ColorSet, love that also.

Flash - what do you think of that technology?

Call me a purist, but I’m really into DHTML. Unless somebody convinces me otherwise I can do what I need to do with HTML a JavaScript library like jQuery, Dojo, YUI or even the Facebook JavaScript Library.
I disliked flash when it got into ‘mode’ a century ago and still think that flash intros should die. Accessibility is still an issue also.

On the flipside our company created a really powerful ArcGIS API for Flex for building Rich Internet applications on top of ArcGIS Server, our internet mapping server. I might need to reconsider some of my previous believes.

I forward the three-?-stick to

Here and there , , , , , , , , , , , , , , , ,

ColoRotate - 3D color scheme generator with social component

June 15th, 2009 by Michael Gaigg

Following up my blog entry on How to Create a Color Palette for your Website I stumbled over a fascinating color scheme generator: ColoRotate.

Screenshot of ColoRotate

Screenshot of ColoRotate

What is ColoRotate

Set into motion by Michael Douma, the executive director of the Institute for Dynamic Educational Advancement, ColoRotate is a Flash-based application with a custom 3D display engine for visualization. When other palette generators are primarily focusing on the 2D color wheel, ColoRotate uses a prism to display color, luminescence, saturation, and brightness all in once. I found it very easy and intuitive to use and was able to produce a harmonious color palette within seconds (well, not that it was for any special purpose) and export the colors as CSS to my clipboard.

Community

Lazy registration

Lazy registration


Lazy registration with filled out information

Lazy registration with filled out information


Here comes the part that I love: Sign in using your google account to save and share schemes. Yes, that means one can in reverse search, get inspired and re-use existing user-generated schemes.

Loving it.

Note on the side: Loving even more the lazy registration process :)

Facit

Go, check it out. It’s not just another tool in your design toolbox. Look out for the Creative Suite 4 (CS4) plugin to come and start showcasing your palettes and discuss them with the community.

Good News , , , , , , , , , ,

Beware of the Frankenstein Design

May 22nd, 2009 by Michael Gaigg
Frankenstein Design

Frankenstein Design

“It was already one in the morning; the rain pattered dismally against the panes, and my candle was nearly burnt out, when, by the glimmer of the half-extinguished light, I saw the dull yellow eye of the creature open…” (Chapter 5). Sounds familiar to us geeky programmers out there? Yes, and the root of all evil are clients that design their webpage from a sushi menu, picking whatever they like.

Usually I encourage my clients to look around, get inspired and show me what they like. It gives me a sense of how they think and into which directions they want us to go. But never forget: Clients identify problems, designers provide solutions! Understand why the client shows you a specific page or design element and what exactly they like in it. Don’t feel pressured to include every detail in your final design otherwise you wake up at 1am facing a yellow-eyed creature and you’ll end up with a Frankenstein Design.

Warning Signals

What are warning signals that your project might face a Frankenstein Design?

  • Client mentions Stakeholders too often. Money makes the world go round, but will eventually ruin the user experience.
  • Client fell in love with a bad design. Try to build solid knowledge about good and bad design principles so you can explain the pro’s and con’s of a particular design.
  • Client needs to please too many interests. It’s understandable that every party involved wants to see their logo on the page, but honestly, one is enough ;)
  • Client decides on a color scheme. Besides corporate colors clients feel strongly about certain colors that either clash with your design, psychological theory or existing color schemes or are simply bad taste altogether.
  • Client has no idea at all. That means trouble! Not now, but once you are done. Guaranteed.
  • Got more?

What you can do

  • Listen. Hear what the client tells you and try to understand why they say it.
  • Feel. Sense what the underlying need is and translate it into design elements.
  • Talk. Speak up, don’t shut up, don’t wait until it’s too late.
  • Fight. Pick your battles, don’t let rules overrule what you think is right, at least voice it.
  • Reconsider. Don’t get hooked to an idea too strongly, be open to erase your white-board drawings and start over.
  • Document. Make notes, sketch ideas, capture screens, summarize. Send these notes out.
  • CYA. Cover your ass, seek consensus and approval, set it in stone through written acknowledgments (mockups help).

Send me your experiences? What is missing on this list?

Web Design , , , , , , , , , , , , ,

Best Practices for Accessible Stylesheets

May 1st, 2009 by Michael Gaigg

Cascading Style Sheets (CSS), or short Stylesheets, is a language used to describe the presentation (that is, the look and formatting) of a document written in a markup language like HTML.

The stylesheet language as described in CSS level 2 revision 1 helps to separate presentation from structure and thus adds flexibility to the look and feel of a web page. Stylesheets are useful for the following reasons:

  • Can be re-used for many documents
  • Saves download times by caching by the browser
  • Presentational changes are fast and easy and only in one document
  • Development can be done independently from content and logic
  • Increases ability to program for device independence
  • Application of different styles for different output formats (e.g. print)

Basic Rules

  • Add Stylesheets whenever possible (minimize number of stylesheets)
  • Use them consistently across all pages
  • Use linked stylesheets rather than embedded styles; avoid inline stylesheets
  • Stylesheets do not substitute correct and meaningful structure

Best Practices

Level 1

Level 1 Checkpoints - Section 508 Compliancy Standards
Description W3C 508 Example
Organize documents so they may be read without style sheets 6.1 d Ensure that important content appears in the document object and is not generated by style sheets (i.e. through :before and :after pseudo-elements).

Level 2


Level 2 Checkpoints - Section 508 Compliancy Standards
Description W3C 508 Example
Use style sheets to control layout and presentation 3.3 n/a
<HEAD>
<TITLE>Drop caps</TITLE>
<EM class=”highlight” title=”provide STYLE element”>STYLE</EM> type=”text/css”>
.dropcap { font-size : 120%; font-family : Helvetica }
</EM class=”highlight” title=”provide STYLE element”>STYLE</EM>>
</HEAD>
<BODY>
<P><SPAN class=”dropcap”>O</SPAN>nce upon a time…
</BODY>

Level 3

Level 3 Checkpoints - Section 508 Compliancy Standards
Description W3C 508 Example
Create a style of presentation that is consistent across pages 14.3 n/a A consistent style of presentation on each page allows users to locate navigation mechanisms more easily but also to skip navigation mechanisms more easily to find important content.

Template

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<link rel="stylesheet" type="text/css" href="BaseStyleSheet.css" />
</head>
<body>
Hello World
</body>
</html>


/* Base CSS Document */
/**
Elements
*/
html, body, div, span, applet, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, acronym, address, big, cite, code,
del, dfn, em, font, img, ins, kbd, q, s, samp,
small, strike, strong, sub, sup, tt, var,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td {
margin: 0;
padding: 0;
border: 0;
outline: 0;
font-weight: inherit;
font-style: inherit;
font-size: 100%;
font-family: inherit;
vertical-align: baseline;
}
/* remember to define focus styles! */
:focus {
outline: 0;
}
body {
line-height: 1;
color: black;
background: white;
font-family: Arial, Helvetica, sans-serif;
}
ol, ul {
list-style: none;
}
/* tables still need 'cellspacing="0"' in the markup */
table {
border-collapse: separate;
border-spacing: 0;
}
caption, th, td {
text-align: left;
font-weight: normal;
}
blockquote:before, blockquote:after,
q:before, q:after {
content: "";
}
blockquote, q {
quotes: "" "";
}
/**
Classes
*/
/**
IDs
*/

References

Accessibility , , , , ,

Excellent read: Quality in Web Design

April 20th, 2009 by Michael Gaigg

Stumbled upon this blog entry by liam, loved it, shared it: How to Spot Quality within Web Design: Examples & Tips.

One can truly see the effort that went into all the visual examples (thanks, love that most) and compilation of useful tips!

Here the outline:

  1. Spacing
  2. Pixel Perfect Detail
  3. Well thought out Typography
  4. Organization of Elements
  5. Restraint & Subtlety
  6. Using Colour to it’s Full Potential
  7. Doing something Nobody else has done

Got an interesting article or blog entry?

I’d love to read and eventually share your content. Please feel free to add your links to the comments section so I can ’stumble upon’ them too :)

Web Design , , , , , , , , , , ,

Design Guidelines: Error Messages

April 10th, 2009 by Michael Gaigg

Just some weeks ago I wrote about Design Guidelines for 404 Pages. Closely related are Error Messages in general, and believe me, they will save your life. That’s why you need to get them right!

Why bad error message can hurt your company

Error messages are like saying “You are stupid”, or “Come on old fart, you still don’t get it?” - and that’s bad, it’s almost like constantly telling your kid “No, no, no”. Be preventive, defensive and avoid Design Bloopers like the the one at Cingular: Having tried to log into my account the following error message appears “My Account is Currently Closed”. Can you imagine the horror that bubbles up and the thoughts of who to call (but how?)? As it turns out Cingular was just maintaining their server and the only flawed thing was the error message. Is it possible to measure how much this little flaw will hurt the company?

Misleading and almost terrifying error message at Cingular

Misleading and almost terrifying error message at Cingular

Defensive Web Design

Prevent error messages whenever possible; e.g. "did you mean" at google.com

The beauty of usability design is to think of ways to prevent showing error messages at the first place. The most prominent example is probably Google. Have you ever seen an error message on Google? How great is the “Did you mean:” function… I even use it day by day as a spell checker, like I use google images to visualize words I didn’t know (do you know what a vicuna is?).

Design Guidelines: Error Messages

  1. Avoid error messages if possible.
  2. Explicit indication that something has gone wrong
  3. Human-readable language
  4. Polite phrasing without blaming the user or imply that user is stupid or is doing something wrong
  5. Precise descriptions of exact problems
  6. Constructive advice on how to fix the problem
  7. Visible and highly noticeable, both in terms of message itself and how it indicates which dialogue element users must repair
  8. Preserve as much of the user’s work as possible
  9. Reduce the work of correcting the error (e.g. list of possibilities)
  10. Hypertext links may be used to connect a concise error message to a page with additional background information or explanation of the problem.

Did you ever encounter a ’special’ error message?

Send me a screenshot and/or tell me the story behind it.


Suggested reading:


Defensive Design for the Web

37signals. New Riders Press 2004, Paperback, 264 pages, $9.00


GUI Bloopers

Jeff Johnson. Morgan Kaufmann 2000, Paperback, 584 pages, $12.95

Design Guidelines , , , , , , , , ,

Steps to improve User Experience for Government

March 31st, 2009 by Michael Gaigg

In my daily work I’m constantly confronted with developments for government sites. Often I hear confusion in what needs to be achieved, who needs to be served and especially why it should matter.

Become creative to engage citizens in governmental issues (using the citizen’s language), e.g. upload a photo of the damaged street (http://www.fixmystreet.com/)

Become creative to engage citizens in governmental issues (using the citizen’s language), e.g. upload a photo of the damaged street (http://www.fixmystreet.com/)

Listening into a Webcast by Human Factors International (download white paper on Designing the e-government experience through citizen-centered usability, March 2008) gave me additional insights that I want to summarize and present here:

Goals of eGovernment

The web offers governmental sites the potential for increased operational efficiency and cost reductions while improving access to information and services for their citizens.

Levels of interaction between these two actors (government & citizens) include:

  • Connect citizens with legislative offices
  • Communicate faster and more targeted
  • Leverage access to public services (enhanced productivity with reduced effort)

Steps to improve eGovernment

Traditionally the government has three main functions:

  1. Report
  2. Transact
  3. Interact

What can be done to improve these functions/processes?

Get it out there

  • What information is interesting?
  • What is already available?

Make it useful & usable

  • Pre-digest the information (e.g. into charts, comparisons, …)
  • Understand the citizen’s needs (e.g. Spanish language, search, text size, …)
  • Assist citizen’s in finding the information (sometimes they don’t know it exists)
  • Avoid: limited business focus, internal focus, lack of shared resource

Provide self-service

  • Assist citizens to walk through business logic (avoid unnecessary pages, forms, fields, …)

Track improvement

  • Establish a baseline (best practices review, scorecard, usability testing success rates, web analytics, call center volume, server logs, …)
  • Validate improvements (success rate, task time) & seek for support within your organization for doing this
  • Continuously track usage
  • Why? Avoid falling back in national ranking, reduce costs for service calls, …

Make it engaging

  • “Will? Can?” Will citizens use the service? Can they find it?
  • Make it exciting
  • Use experiences or technologies that are current and up to date (videos, gadgets, …)

Embrace the future

  • Become creative to engage citizens in governmental issues (using the citizen’s language), e.g. upload a photo of the damaged street (http://www.fixmystreet.com/)
  • Encourage citizens to interact through social tools

Erase boundaries

  • Integration of “Report”, “Transact” and “Interact” means to remove the disparity between organizational structures of governments and the mental models of the citizens
  • Understand and channel the motivation of citizens to use online services
  • Integrate offers from multiple agencies into one comprehensible user experience

Start a movement

  • Create a community by involving State & Agency Leadership, Agency CIO’s and Webmasters
  • Recognition and adoption are key aspects
  • Embrace the chaos
  • Provide useful & usable tools
  • Reward contributions & demonstrate progress
  • View webmasters as a partner, not as recipient

Transparency

  • The user’s perspective of the organization and the actual organizational structures are mostly very different. Citizens should not need to know how an agency is organized or be familiar with its terminology.
  • Focus on the citizen means to understand how they look for information!
  • Integrate internal processes into one intelligent solution (iGov = integrated Government)
  • Understanding the level of literacy is key to success. Easy language assists citizens in filling out bureaucratic forms.

Government must view itself as a business

  • Attract and satisfy citizens. Beware of competition and consider concepts like ‘brand loyalty’. Effective interaction adds benefits to citizens.
  • Convert visitors into customers meaning that citizens become active online users of the services.
  • Broaden the focus onto international audience which is important to attract entrepreneurship and investment capital and is a good indicator of a strong technology market and research and development environment.

Assistance through technology, tools and continuous improvement

  • Support CIO’s and webmasters through tools like design templates, standards, guidelines and an effective means of governance.
  • Adjust technology to changing market conditions, population demographics and the user’s level of expectations.
  • Create a culture and long-term commitment (=institutionalization) of usability within the agency!
  • Establish a baseline of improvement and continuously validate and improve through benchmarks.

Your thoughts?

I’d like to hear your feedback and if you have applied one or many of above techniques in your agency and what your experiences were.

References

  • Straub, K., Gerrol, S.; Designing the e-government experience through citizen-centered usability; Human Factors International, Inc.; White paper; March 6, 2008

Usability & UCD , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Question: How can Internet Mapping Applications be made accessible?

March 25th, 2009 by Michael Gaigg

Following I will identify areas that make web-based maps inaccessible as per WCAG 1.0 (please see section: ‘Questions and Possible Research Areas’).

Shout for Help

Question: How can Internet Mapping Applications be made accessible for users with disabilities?

If you are currently working on resolving any (or all) of these issues, know of somebody that is working on them or even know existing solutions, I would greatly appreciate if you pointed them out to me.

It is absolutely impossible to continue with our current approach to seek exceptions as a ‘work-around’!

Background

It is important to note that I’m not talking about simple Google maps like driving directions or locate services that could be described through alternative, textual output.
Many times a map is the means to select, query, mix and eventually analyze data across multiple layers from multiple services. The input requires good vision and motor skills (mouse) and same applies to the output that is highly visual as well.
A simple example that illustrates this fact pretty well is shown in Figure 1, Drive Times from a specific location based on traffic grid.

ESRI Map, Drive Times

Figure 1: ESRI Map: Drive Times; produced using ArcGIS JavaScript API, http://mapapps.esri.com/serverdemos/siteselection/index.html

The Law

Section 508 as explained by Authority 29 U.S.C. 794d: “Section 508 requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who are not individuals with disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.”
This law is extended and applicable to companies that develop applications for the agency, i.e. ESRI has to adhere to the Section 508 Standards.
The Section 508 Checkpoints were translated into Web Content Accessibility Guidelines which cover most of Section 508 and describe its implementation in terms of HTML & CSS.

Current ‘Solution’

So far, exceptions to this law have been granted for the specific case of online maps. It is believed to impose an ‘undue burden’ to the agency/contractor to make maps accessible. In many cases a 1-800 number was provided that would help the user to get the same information.

Questions and Possible Research Areas

Currently the following WCAG checkpoints are Level 1 (A) show-stoppers and need to be solved/researched/implemented:

Checkpoint 1: Provide equivalent alternatives to auditory and visual content

How to read a map when blind? E.g. redundant text for active regions/content.

Checkpoint 2: Don’t rely on color alone

Map application could provide different color schemes/black&white/shades of gray?!

Checkpoint 6: Ensure that pages featuring new technologies transform gracefully

How to provide a map (or alternative) that can be used when scripts are turned off?

Checkpoint 8: Ensure direct accessibility of embedded user interfaces

Do not write event-handlers that rely on mouse-coordinates (device-independence; see also Checkpoint 9)

Checkpoint 9: Design for device-independence

How to navigate a map without a mouse?

Checkpoint 12: Provide context and orientation information

How to describe the content of a map (especially after a change, e.g. query)?

You know of a solution?

Please get in touch with me if you know of solutions to these problems!

I hope that solutions for these problems can be found and maps become available to everyone. As always, not only users with disabilities will benefit from these efforts but also the applications themselves, e.g. better SEO (search engine optimization), alternative support for mobile user agents, assistance for elderly people, etc.

Accessibility , , , , , , , ,