Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Make a declaration #29
created this issue from a note
in GOV.UK Design System Community Backlog
Jan 12, 2018
At HMRC we've come across the need for a submitter identity function within this pattern. That is, the need to know that the person submitting the information is the right person in the organisation. All the HMRC patterns we have currently assume that the person submitting has the right to declare. I wonder if this might be worth a variant?
Is there any specific guidance around not linking people off from the declaration page? On Blue Badges we have a bullet point that we want included saying "you have read and understand the rules for using a Blue Badge". The original request was to have part of this text linking off to a PDF of guidance... This doesn't feel like a great idea. Especially as it's the last page before submission and there is a timeout on the service.
Any advice would be great, thanks!
@charge-valtech I agree that it is an odd time to take people out of a service, especially if it would take more than 15 minutes to read the guidance.
This has been a requirement for some HMRC services. I think giving the link makes sure someone would not have to find the guidance before making their declaration. Here is an example from 'Manage your anti-money laundering supervision'.
The link is to a topic page with 17 links that would take longer than 15 minutes to read and understand. See https://www.gov.uk/topic/business-tax/money-laundering-regulations
Dropbox Paper audit
On 8th March 2019 the Design System team reviewed a Dropbox Paper document discussing the Declarations pattern.
The aim was to reduce the number of places containing guidance and code by:
Below is a record of the outcomes of that review.
If you need to, you can see the original Dropbox Paper content in the internet archive.
Updates to the Design System
The draft guidance on Declarations has now been included with this issue and the Dropbox Paper copy has been archived.
Help users understand that the information they provide must be true, and what the consequences of providing false information are.
When to use this pattern
Use a declaration if there are significant consequences to the user if they provide false information whilst using your service.
How it works
Make declarations concise and to the point
Users don’t read long pages of +terms and conditions. If the consequences of making a false declaration are genuinely important then this should be communicated clearly and concisely.
If there’s a specific part of the service that carries the severe penalty (especially if it’s not something the user would expect) then explain the penalty at that point in the service.
In most cases, you should set out the consequences of making a false declaration - eg "If you deliberately give us false information, you could be fined up to £5,000". If you don't want to state the penalty (eg because it's really trivial), say something like "It's against the law to deliberately provide false information".
Don't cite legislation (no-one will read it). For example: "Providing false information is an offence under section 2(a) of the Financial Services and Markets Act 2000" is less effective than "Providing false information is a criminal offence. You could be fined or go to prison.”
It’s not clear that clicking on a checkbox carries any more legal weight than just having the user click a button.
There's some evidence that people have become so used to this technique that it no longer carries any significance, but more research is required.
Declarations at the beginning of a transaction
There's some evidence that people are less likely to lie if they're reminded of the consequences before they start a transaction rather than at the end. You might want to consider this approach if the consequences are very severe. Keep it to a short simple statement though - don't link to or embed a long list of terms and conditions.
Declarations at the end of a transaction
If you add a declaration to the end of a transaction, you must give people a means to go back and change the information they've provided. For this reason, the bottom of a 'Check your answers' page can be a good place to have a declaration.
For very important transactions, consider a signing ceremony
If the consequences of making a false declaration are very severe, emphasising the declaration part of the transaction can reassure people that the service is taking them seriously. If your users are expressing reservations about completing a transaction because it doesn't feel 'important' enough, consider a signing ceremony.
Make it very clear which information is covered by the declaration. Signing ceremonies add extra work for people and may even put some user off the service. Only use them if you have evidence that they're helping. More about signing ceremonies.
Research about this pattern
Dan Ariely (author of 'Predictably Irrational') reports on various academic studies about honesty in his book "The Honest Truth about Dishonesty". It turns out that people are less likely to lie if they do the declaration at the beginning of the form, along the lines of "I promise that everything I write in this form will be accurate". He tried to persuade the IRS to put the declaration at the front, without success.
Should the full text of the declaration be visible, or is it acceptable for it to be available. Some services will have long +terms and conditions, and will typically include a line such as "you also agree to the terms and conditions", linking off to where they live.
Options for display of declaration text
Register to vote
The following appears at the bottom of the 'Check your answers' screen:
Your tax account
Online enforcement penalty payments