Make a declaration
A declaration allows users to confirm that they have understood or agreed to something before they submit an online form.
The following examples show how declarations are used in Home Office services. Use these examples as a guide only and adapt them for your service.
You must ask a legal representative to sign off your declaration content.
When to use this pattern
Use this pattern when there are significant consequences if false information is given and the user needs to confirm that:
- the information they've given is correct
- they understand the consequences of not telling the truth
- they understand the information they have been given
- they need to agree to something
Writing for this pattern
The declaration should be tailored to the service and include information about what will happen if the user makes a false declaration.
- make consequences clear using simple language
- refer to the user as 'you' in the text, but 'I' in the action button
- use 'I confirm that' or 'I understand that'
- add a checkbox and ask the user to confirm that they understand and agree
- get the content signed off by legal or policy
- duplicate terms and conditions or privacy policies
- use the word 'prosecute' unless you are sure this is the case
- use complex legal or policy terms if they can be explained simply
- publish a declaration content that has not been sign off by legal or policy
When not to use this pattern
Do not use this pattern to give users complex or complicated information about policy or legislation.
If a bullet list is not needed, instead consider using 'Accept and continue' or 'Agree and continue' buttons along with a statement. For example:
By submitting this application, you are agreeing that the information you have provided is correct.
If your service uses this pattern, add the error messages that you have used.
Services using this pattern
This pattern has been used in the following services:
- Electronic Visa Waiver
- Register to Apply for US Global Entry
- Registered Traveller
More research is needed. If your service uses this pattern, get in touch to share your user research findings.
All transactions should be reversible, or confirmation must be required before submission. See the error prevention requirement in the Home Office Accessibility Standard for more information.
Consider alternative ways a user can submit a declaration offline.
If your service uses this pattern, let us know of any insights you have on accessibility considerations.