LAWS design guidelines

LAWS guidelines

Version

Final March 26th 2004


Abstract

This document contains a set of design guidelines
for local authority Web sites.

Prepared for the LAWS project
by the IBM Usability Competency Centre.


Table of contents


Introduction

About this document

Origin

This document contains design guidelines for local authority Web sites. It was sponsored by the LAWs project and developed by the IBM Usability Competency Centre.

Scope

The guidelines cover fields such as usability, accessibility, trust, e-government, legislation, and adoption. In most cases, the document gives guidelines at a summary level and refers you to authoritative sources for detailed advice. For example, while the guidelines do emphasize the important principles of coding accessible HTML, they do not give technical details for all aspects of tagging.

How this document is organised

Principles, guidelines, and sources

This guide is structured as a collection of guidelines organised within a set of principles. Guidelines are derived from range of referenced sources. Principles are marked by the symbol , guidelines are shown by the symbol , and sources are indicated by the symbol .

Where a principle describes a goal that a designer should aim for, the related guidelines offer specific advice on how to achieve that goal. Think of the principle as "why" and the guideline as "how". For example, to satisfy the principle Build on the citizen's prior knowledge, you would follow related guidelines such as Highlight new content and important news and Provide clear information that tells citizens how to contact the local authority.

Indexes and content

The front section of this document contains a set of indexes to help you find the guidelines you need. The main index Guidelines by LAWS goals and principles lists principles and their associated guidelines under the three LAWS goals, Useful, Usable, and Used. Three secondary indexes list guidelines by field of study, (for example Accessibility), by role and task, (for example Designer and Design content), and by validation method, (for example Expert review).

The body of the document contains details of all principles and guidelines. Like the main index, it is organised by guideline within principle within the three LAWS goals Useful, Usable, and Used. For each principle, it explains the meaning and underlying thinking. For each guideline, it provides additional information such as examples, rationale, the impact of not following the guideline, priority, validation method, and sources of further information.

The back of the document contains a glossary of technical terms and details of the sources referenced in the guidelines.

How to use these guidelines

To achieve a design that is useful, usable, and used:

  1. Follow the link in the table of contents to review the main index Guidelines by LAWS goals and principles
  2. Follow the links in the index to review individual principles and guidelines

To find guidelines related to a specific field of theory or practice such as Usability or Accessibility:

  1. Follow the link in the table of contents to review the index Guidelines by category - Field
  2. Follow the links in the index to review individual guidelines

To find guidelines related to a specific role and task such as Designer and Design content:

  1. Follow the link in the table of contents to review the index Guidelines by category - Role and task
  2. Follow the links in the index to review individual guidelines

To find guidelines for which compliance can be checked by a specific validation method such as Expert review:

  1. Follow the link in the table of contents to review the index Guidelines by validation method
  2. Follow the links in the index to review individual guidelines

To find out the meaning of specialist terminology:

  1. Hover over or click on terms highlighted in underlined italics

Disclaimer

This document is not intended to offer advice on legal or safety matters. If you need guidance on these matters, please contact an appropriate professional.


Guidelines by LAWS goal and principle

Useful

Principle Make all services available at all times

Principle Provide services and information that citizens want and need

Usable

Principle Allow citizens to customise

Principle Build on the citizen's prior knowledge

Principle Create a feeling of progress and achievement

Principle Design the site to support the citizen's preferred method of connection

Principle Do not compromise usability for function

Principle Keep the citizen out of trouble

Principle Provide proactive assistance

Principle Make actions predictable and reversible

Principle Use visual design to communicate the meaning and importance of elements of the site

Principle Write in a way that makes it easy for citizens to read on a computer screen

Used

Principle Avoid displaying or collecting information that could be misused

Principle Comply with all legislation and Government guidelines that affect Web site design and use

Principle Create a site that citizens trust

Principle Design the site to encourage adoption


Guidelines by category - Field

This index enables you to find guidelines related to a specific field of theory or practice, such as usability, accessibility, or trust.

Guidelines for Business

Business related fields study factors that are important to ensure success in a real-world business context.

Guidelines for Government

Guidelines for Law

Guidelines for Safety

Guidelines for Trust

Guidelines for Design

Design fields are concerned with the needs and motivation of individual users.

Guidelines for Accessibility

Guidelines for Adoption

Guidelines for Culture

Guidelines for Technology

Guidelines for Typography

Guidelines for Usability

Guidelines for Visual design

Guidelines for Writing


Guidelines by category - Role and task

This index enables you to find guidelines related to a specific role and the tasks typically carried out by that role.

Guidelines for Content creator

A content creator is responsible for developing material such as service definitions, location descriptions, and policy statements. Content creators typically have skills in writing and communicating together with subject matter expertise in aspects of local government.

Guidelines for Create content

Guidelines for Create help text

Guidelines for Designer

A designer is responsible for the user experience of a local authority site. Designers typically have skills related to interaction design, information design, or graphic design.

Guidelines for Design interaction

Guidelines for Design navigation

Guidelines for Design presentation

Guidelines for Developer

A developer is responsible for implementing a design as software on both client and server. Developers typically have skills such as implementation design, programming languages, networks, and server configuration.

Guidelines for Develop software

Guidelines for Implement servers and networks

Guidelines for Manager

A manager is responsible for ensuring that relevant legislation and government policy is implemented in the design of an authority site.

Guidelines for Manage implementation

Manage implementation

Guidelines for Marketer

A marketer is responsible for promoting the authority site and encouraging increased uptake by citizens.

Guidelines for Promote site

Market site


Guidelines by validation method

Guidelines for validation method - Code inspection

A code inspection is a review of the source code for the site to check for compliance with coding standards. A code inspection typically looks at both client-side code, such as HTML, and server side code such as PERL.

Guidelines for validation method - Expert review

An expert review is a inspection of some aspect of the design by a panel of specialists in a field such as accessibility, usability, or legislation.

Guidelines for validation method - Research (interview etc)

Research involves gathering opinions from citizens. Methods include interviews, focus groups, and surveys.

Guidelines for validation method - User test

A user test is a scientific study that observes and measures citizens using the site to carry out typical tasks.


Details of guidelines

Useful


Principle PRINCIPLE

Make all services available at all times

Users expect to be able to use Internet based services at any time they choose.

Citizens should be able to use all services in any sequence and at any time. They may wish to interrupt one task to perform another.

Give the citizen control over the system. Enable the citizen to apply self-defined procedures to accomplish tasks. Do not impose your own notion of the "correct" way of doing things, and limit the choices that should be available to the citizen.

Ensure that the system permits the citizen to establish and maintain a constant working context or a frame of reference. Make obvious the current state of the system and the actions for the citizen to perform. If the citizen leaves the system for a moment or longer, the state of the system should remain current or stable at the time of their return. This contextual framework contributes to their feeling of stability.

Avoid the use of modes. Modes restrict the user's ability to interact with the system. For example, allow the citizen to log on through more than one browser window at the same time so that they can refer to old information at the same time as supplying new information.


Guideline GUIDELINE

Make services available 24 hours a day, 7 days a week

Rationale

Users expect Web sites to be available all the time. If your site is down, or a service is unavailable, citizens' trust and perception of the usefulness of your site will be damaged.

Priority

3. Recommended

Validation method

Related principle

Sources


Guideline GUIDELINE

Allow citizens to use services in the sequence they choose For example, do not prevent them from using two different services at the same time.

Rationale

Citizens may wish to read information at the same time as completing a transaction in a different area. Whilst carrying out transactions, some citizens may see other information that they want to investigate. Allow citizens to explore other possibilities without abandoning work they have already done.

Priority

2. Strongly recommended

Validation method

Related principle

Sources


Guideline GUIDELINE

Use team or generic e-mail addresses rather than personal ones For example, use planning_department@camden.gov.uk instead of Richard_Smith@camden.gov.uk.

Rationale

Citizens should not have to adjust contact details they have saved as a result of personnel changes within the local authority. Using team or generic e-mail addresses provides a far more sustainable way to publish and handle e-mails.

Priority

3. Recommended

Validation method

Related principle

Sources


Principle PRINCIPLE

Provide services and information that citizens want and need

Government Web sites need to be user focused. Provide the information and services that citizens want, and continually evolve them to meet user demand. Web sites that do not meet user needs cannot be effective.

Local authorities will often need to provide electronic information, and in some cases transactions, for over 700 different services. Give priority to services that are most beneficial to the local community. This will help ensure that the site is useful to its target audience.


Guideline GUIDELINE

When planning which services should be hosted online first, consider those which are most in demand by citizens and those which will bring the greatest cost savings to your authority

Rationale

Government policy is to make all government services electronically available by 2005. As Web usage increases, citizens' expectations will increase in relation to the online information and services provided by government.

Priority

2. Strongly recommended

Validation method

Related principle

Sources


Guideline GUIDELINE

Present content that is applicable to citizens

Rationale

Many government documents are not aimed at the general public, or are of any interest to them. Make a distinction between information that is aimed at different audiences. Ensure the main navigation and search functions used by citizens leads them first to information that is useful to them.

Priority

2. Strongly recommended

Validation method

Related principle

Sources


Guideline GUIDELINE

Support two-way communication between local authorities and citizens For example, provide contact information on the home page to reassure citizens that they can speak to someone either on the phone or face-to-face.

Rationale

Citizens will expect to be able to contact government officials, express their views, make enquiries, or ask for help. If your site does not provide an adequate level of support, some citizens will be unable to complete tasks effectively. Encourage citizens to adopt your site by supporting feedback and queries, and by reassuring them that help is available should they encounter any difficulties.

Priority

3. Recommended

Validation method

Related principle

Sources


Guideline GUIDELINE

Provide clear information that tells citizens how to contact the local authority

Rationale

Web users expect to be able to contact real human beings if they need to. Providing contact details will help build trust amongst citizens and give them easier access to the local authority. Display clear contact information on the home page. Include a full postal address, a telephone number, and a contact e-mail address.

Priority

2. Strongly recommended

Validation method

Related principle

Sources


Guideline GUIDELINE

Provide clear directions on how to find local authority buildings

Rationale

Some citizens may need to visit council officers, and they will expect the Web site to provide clear directions on how to find the local authority buildings. Provide textual directions on rail, road, bus and underground travel. If you provide a map, present it either as a graphic (GIF or JPG) or a dowloadable PDF file.

Priority

3. Recommended

Validation method

Related principle

Sources


Guideline GUIDELINE

Highlight new content and important local news

Rationale

Highlighting new content helps citizens find new information and helps them to appreciate the active nature of the site. Review highlighting regularly so that it is not devalued by over use.

Priority

3. Recommended

Validation method

Related principle

Sources


Guideline GUIDELINE

Offer services that help to create and support local online communities For example, adopt the LAWS Community Engagement Modules that provide facilties to help local comunities set up their own web site and publish local events.

Rationale

Providing services that are useful to local communities will encourage more citizens to use and value the local authority site.

Priority

3. Recommended

Validation method

Related principle

Sources


Guideline GUIDELINE

Offer services that support local businesses For example, adopt the Community Engagement Modules to enable businesses to advertise available jobs.

Rationale

Provinding services that are useful to local communities will encourage more citizens to use and value the local authority site.

Priority

3. Recommended

Validation method

Related principle

Sources

Usable


Principle PRINCIPLE

Allow citizens to customise

The interface should be tailorable to an individual citizen's needs and desires. No two citizens are exactly alike. Citizens have varying backgrounds, interests, motivations, levels of experience, and physical abilities. Customisation can help make an interface feel comfortable and familiar.

Personalising a computer interface can also lead to higher productivity and user satisfaction. For example, allow citizens to change their own home page to give priority to elements that they use most frequently.


Guideline GUIDELINE

Store each citizen's personal information

Rationale

Citizens will not continue to use a site that makes them supply the same information more than twice. Allow citizens to choose how much of their personal information is stored.

Priority

3. Recommended

Validation method

Related principle

Sources


Guideline GUIDELINE

Allow citizens to tailor services to their needs For example, if citizens log on, allow them to remove rarely used functions from their view of the site.

Rationale

If citizens are presented with few choices, they will be able to find areas they need more quickly.

Priority

3. Recommended

Validation method