How Should Government Web Sites Be Designed?

Wally Hartshorn asks: "Do Slashdot's readers have some examples of government Web sites that they particularly like or dislike? I'm the Web coordinator for the Web site of a state government agency, and I am looking for some ideas to improve our site's usefulness and design. I've read numerous articles about Web design, but they virtually all focus on commercial sites, where the information to be provided tends to be short and voluntary. There are many good ideas to take from these articles. However, I'm reasonably certain that there are some very different issues to consider when designing a site that is trying to present regulatory requirements (to an audience that would really rather be doing something else) rather than a site focused on selling or providing news. Any suggested good/bad examples to visit?" I think the key word for government sites is 'accessibility'. Do you all agree or disagree?

Comments

Make them printer-friendly

[Thaddeus]

As someone who has designed a few government web-sites in the past, probably the number one demanded feature is printer-friendliness. Usually the pages are full of detailed info of which many visitors will want a hard copy. If you have too many images (especially large ones), outlandish formatting, or even a black background, it won't come out right for a lot of people. If you absolutely need to put that kind of thing in there, consider making a second, plainer version with a 'Printer Friendly' link to it.

Got it in One

[StormyMonday]

I think the key word for government sites is 'accessibility'.

Bullseye.

The rules for content are simple:

• The users have to be able to find it.
• The users have to be able to read it.

The first item means that you have to be really careful how you lay out your site navigation. Other posters have some good suggestions here. In particular, consider how your users will try to find things. Hint -- it aint by regulation number.

It is also important to provide your data in a usable form. Thomas is a particularly bad example here. This site lists bills before the US Congress. Unfortunately, the "real" text of the bills is almost invariably in the form of a diff to a current law; it's impossible to tell what's going on without reference to the original, and even then, it's not easy.

In terms of fancy layout, etc:

• Take the graphic designers out and shoot them.
• Delete all the fancy "web design" tools. Anybody who uses a tool more sophisticated than Homesite will be designated a "graphic designer" and shot. Anybody can learn enough HTML to format a basic page in about 10 minutes.
• All testers must connect to your pages at no more than 14400 bits/sec. Broadband connections and local Ethernets are specifically forbidden.

In particular:

• Don't make assumptions about your users' hardware or software. In particular, don't assume any particular screen size or browser.
• No animation, Shockwave, graphics maps, Java, Javascript, background music, etc. Duh!
• User defaults are your friend; style sheets are your enemy. In particular, don't mess with fonts. Every commercial site out there tries to force me to read a tiny, san-serif font. Every usability study I've ever seen shows that serif fonts (Times Roman, for example) are more readable.
• Don't use tables for layout. They don't improve readability and they slow things down. Use tables for tables, and don't make assumptions about your users' screen size or resolution.
• Use graphics only when necessary and keep them small. Use the minimum color and resolution that you can get away with. Don't forget the ALT tags.
• Validate your HTML. There are a number of HTML validatiors out there; find one you like and use it. Amazing how often this gets forgotten ....

Above all, look at it! Look at it with every browser you can find. Don't forget the old versions. (And don't forget Lynx.) Get some blind (excuse me, Visually Impared) testers if at all possible to "look" at it with screen magnifiers and screen readers. Look at it over slow lines.

Note that, depending on the laws in your area, you may have specific requirements that won't fit these (or probably, any) guidelines (line numbering, fonts, etc). In this case, you may be limited to letting folks download a PDF file. Even in this case you should be able to post your HTML regs "for information only" and tell people to refer to the PDF for the "real" regs.

Anyway, good luck! One advantage of the current crowd of crap Webpages is that it's easy to look good.
--