Imagine how annoyed you'd be if your car's steering wheel randomly moved to different parts of the car, none of the knobs indicated what, if anything, they did, and the gas and brake pedals switched positions every few days.

You'd probably buy a horse and buggy and wholeheartedly embrace the Amish lifestyle. I know I would. At least I could count on getting homemade fudge now and then.

A drastic example, but it illustrates exactly what happens when someone tries to traverse the numbingly confusing terrain of the modern e-government Web site. It doesn't matter how dazzling an online service is if people can't find what they're looking for.

When citizens come looking for information, they want to find it as quickly as possible, and that's where usability and standards come into play.

As I write this, a handful of states are taking baby steps in the right direction.

The commonwealth of Virginia is in the process of promulgating new policies that cover Web templates, accessibility and usability so government can present a unified and coherent front to the public. Utah is working on something similar. Kansas requires that sites be accessible to the disabled. Indiana created a header that acts as consistent navigation for government sites, so visitors can always tell how to get back to the state's home page. And California is working to get its consistent navigation header accepted on all government sites in the state.

But the journey will be a long one.

Why Set Standards?

A recent study showed one of every three Web site visitors couldn't get what they needed due to poor usability. How can a government agency rationalize not reaching nearly 35 percent of its audience simply due to bad organization and presentation?

Sure, some sites have done a great job. But many more have done a horrible job. Some sites are totally useless to anyone but the designer, and nothing's worse than a site designed by someone under the delusion they're being clever. As the joke goes, "It just annoys those of us who are."

People don't understand when they click on a link on a government portal, they're going to an altogether different agency that often has different standards and goals. They think their government is whole and organized and seamless. And that's exactly the way it should be.

The alarming truth is that the public's approach to government Web sites is in line with a current restaurant slogan -- get in, get out, get on with your life. Visitors don't care what your internal hierarchal structure is, what your director thinks about the future, or that you have menus one can use properly. Your designer may have a wonderful new Flash animation that impresses everyone at the office, but when you pay attention to your audience's needs, that Flash site must go elsewhere.

The public wants to get to what they need. They don't want to relearn navigation with each link they click on, and they don't want to read some programmer's mind to find information about marriage licenses. Usability is like housework; you only notice when it's done badly. With the exception of a few contests and awards, few people will visit a well designed government site and say, "You know, that was the most usable navigation I've ever seen."

Instead, they will acknowledge your hard work by returning again and again. Only when something breaks will you hear from them, which is how it should be. Yet every day someone is designing a site without glancing toward usability or information architecture, making the Web the chaotic mess it is.


In my experience, there are two main roadblocks to getting government standards in place.

Christopher O'Kennon  |  Contributing Writer