You are here:
- Manual
- Development
- Forms
- Usability of forms
Forms: Enhanced usability of forms
A number of suggestions to improve the usability of forms for visitors are described below. For guidelines and more information, see Useful forms.
Forms in general
Use CSS sparingly for input fields and form buttons.
Guideline R-pd.13.7
- Some browsers do not support CSS on input fields and buttons all that well. If the appearance of the field or the button is essential for the use of the form, visitors to these browsers may be confused. It is better to use HTML markup to indicate meaning. For example,
<strong></strong>around an input field or label that merits attention. - Furthermore visitors are used to the standard appearance of input fields and buttons. They tend to look the same on most of the websites visited, and usually these fields and buttons are similar to parts of the visitor’s operating system. Changing their appearance can be confusing. It is better to leave the appearance of input fields and buttons alone.
If a visitor has to provide personal data, let him know what will be done with this data, e.g. in the form of a privacy statement
Guideline R-pd.13.8
Visitors value respect for their privacy highly. Moreover this is required under the Personal Data Protection Act.
Do not ask a visitor to provide more information by means of a form than necessary for the purpose of the form. Keep forms as short as possible and limit the mandatory completion of form fields.
Guideline R-pd.13.9
Some principals want to know everything about their visitors. Visitors will rarely be willing to provide such personal information without a good reason.
Indicate which fields are mandatory and which are optional.
Guideline R-pd.13.10
Contact forms
Provide alternative contact options, such as address details, telephone numbers or e-mail addresses, if available.
Guideline R-pd.13.11
Visitors like to have a choice. Furthermore, a wide range of contact options benefits communication with the visitor.
Let the visitor know what will be done with the form when it is sent.
Guideline R-pd.13.12
For example, indicate when the visitor can expect a reply or which number the visitor can phone to make inquiries about the processing of his form.
Give the visitor the option of saving his reply.
Guideline R-pd.13.13
For example, display a summary of the reply sent, so that the visitor can print it. Or automatically send a copy of the reply to the e-mail address entered by the visitor.
Once the visitor has completed and submitted the form, send him confirmation that his message has been received (autoreply).
Guideline R-pd.13.14
Thanks to a confirmation, the visitor knows that submitting the form was succesful and that his or her reply is being processed. (The technique for this concerns configuration of the recipient’s email server, not the functionality of the form.)
Large, complex forms
Before displaying complex forms, give the visitor an impression of the size of the form.
Guideline R-pd.13.15
Approximately how long will it take to complete the form?
List documents which the visitor might need while completing the form beforehand.
Guideline R-pd.13.16
For example, it is annoying for a visitor to have to look for tax details or proof of identity halfway through completing the form.
Provide forms with instructions for the visitor if necessary, particularly for the applicable input fields.
Guideline R-pd.13.17
Do not provide more information than necessary. Additional assistance can be offered through a link to more information.
Do not add any reset buttons to forms.
Guideline R-pd.13.18
Not all visitors understand the function of the reset button. Moreover, it hardly ever serves any purpose. Visitors may mistake a reset button for a submit button and consequently lose all the information they just entered on the form! Usually the best option is to leave out a reset button.
