You are here:
- The Manual
- Development
- Contingency design
- Guidelines
Contingency design: Contingency design guidelines
The following is a collection of guidelines for web developers which will help to resolve site-related problems for visitors.
Use language that the visitor understands: limit the use of jargon, difficult terms and abbreviations.
Guideline R-pd.22.1
Give visitors an ‘escape route’: possibilities to continue if they get stuck. Escape routes include useful links, being able to use the back button, a search function, and being able to correct input errors immediately.
Guidelines R-pd.22.2
Don't make visitors guess: provide information on how they can correct errors they have made. Take into account the most common errors.
Guidelines R-pd.22.3
In the event that a visitor to the site has forgotten to fill in a required field, indicate the field in question.
Make modified error pages for errors such as dead links (404 Not Found) where the visitor is given options for continuing within the site.
Guidelines R-pd.22.4
The most frequent mistakes occur when site visitors fill in search terms.
In the event of an error message as a result of sending a form, give the visitor the option of correcting the error in the form immediately and don't make him be dependent on the use of the back button.
Guidelines R-pd.22.5
When implementing a search engine on the website: use ‘smart’ search technology that takes into account spelling errors, similar search terms, terms in singular or plural form, etc.
Guidelines R-pd.22.6
Provide a well-organised list of the most relevant search results. If too many search results are provided, it takes visitors too long to find the desired information. Give visitors the option of entering search criteria, or sorting the search results.
Guidelines R-pd.22.7
Visitor feedback (regarding broken links or malfunctioning forms, for example) can help to increase the overall quality of the website. Make it easy for visitors to give feedback regarding the site.
Guidelines R-pd.22.8
Give visitors the option of reporting errors on the site.
Use colours, icons and textual explanations to draw the visitor's attention to an error message and explain the problem.
Guidelines R-pd.22.9
Give visitors the option of finding information in alternative ways. For example, by providing a sitemap, search functions, or by means of a request by e-mail, letter or telephone.
Guidelines R-pd.22.10
