Effective communication on the web is the product of good content and quality of presentation. Departments and agencies should develop websites that are rich in authoritative and up-to-date content that is well written, caters to the needs of a wide range of audiences and is easily accessible. Publication on the Internet should generally be simultaneous with publication in other media.
2.2.1 Introduction
This section states minimum requirements for the content of websites. It aims to establish what users should expect in homepages, and it sets out for the benefit of web teams a list of the minimum requirements with which they should comply. Together with material in section 2.4 it contributes to the establishment of an authoritative look and feel for government websites. Within these general parameters, it is for departments to determine how best to organise content with their own audiences in mind.
Go to section 2.4 Building in universal accessibility
Departments and agencies should be aware of who the core and non-core audiences are for their websites. It is very likely that the audiences for different parts of the website, or for different websites within a single department's estate, will vary considerably. It is very desirable that, in planning websites, departments should carry out market research or other consultation with core and non-core audiences and that this should be repeated subsequently. It is especially desirable that designers and website managers should view sites alongside members of their core audience and be responsive to their comments.
Departments should apply the same principles of plain language and inclusive language to their websites as they are expected to do to printed documents.
2.2.2 Minimum website requirements
Departments should, where appropriate, publish the following information and documents online:
2.2.3 Minimum homepage requirements
The following is a checklist of items that must be included on your web homepage:
It should also, where appropriate, contain links to the following:
2.2.4 Contact addresses
A full postal address must be provided as well as an email address.
Personal email addresses must not be used; for example, richard@hotmail.com should not be used instead of richard@e-envoy.gov.uk.
Alternatively, generic addresses can be used, depending on the strategy of your organisation, eg, webguidelines@e-envoy.gsi.gov.uk. This allows for portability of email addresses during personnel changes.
When email addresses are to be included within an HTML page they should be displayed using the universally understood email format.
The persons name alone is not sufficient because:
2.2.5 Department location
Although not essential for all, it is always a good idea to include maps and direction instructions to assist people visiting your department.
The map should be presented either as a web graphic such as, a JPG or GIF, or a downloadable PDF file. Whichever format is chosen there should also be a text version covering directions by rail, road, bus and underground.
2.2.6 Version control of website publications
Please refer to section 3.2.8.
Go to 3.2 Document structure