Lee Crossleywe’ve seen auto tabbing bomb in testing. It confused everybody, including highly skilled users. They’d be keyboard tabbing through form fields and not looking at the screen. There is an argument however that it could be useful for internal data entry interfaces.
I am in the process of creating the journey for saving and retrieving a session. I am going to test having both a 'Save and continue' button or a separate "Save" button. With a separate "Save" button we are going to have a small notification/modal box which notify's the user that the form has been saved, we do not think this would be appropriate if a "Save and continue" button is used as it will become very repetitive. Does anyone know if there are any guidelines around how this feature should be implemented? can anyone give me some visual examples to take inspiration from/use as a reference in justifying the design?
This pattern carries no more legal weight than just having them click a submit button. There's also evidence that people have become so used to this technique that it no longer carries any significance.
I disagree with this guidance. This question has come up several times, and I don't think we have consensus here. The UI is not just about having legal weight. We've seen users who will blindly click on the green button without reading. Whilst they may click on an 'I agree' checkbox without reading, at least they've made conscious decision ('informed consent') to do that. They're aware that they've agreed to do something. With the button alone there will be users who don't even realise they've made an agreement at all.
For this sort of thing, the declaration and warning is more of a courtesy (from the user's point of view), and a nudge to get people to give accurate and complete information (from government's point of view). So in most cases, it should be enough to say something like 'By submitting your claim, you confirm that ...' - and leave out the checkbox. The GOV.UK 'exclamation' icon is useful here because it helps the warning to stand out.
If we expect users to have a need to change their answer, after seeing a declaration—then that’s an argument to place declarations at the beginning. Otherwise, users are supplying information, without fully understanding what they’re doing. Users can be reminded of the declaration (if need be), or any legal consequences, when submitting/checking their answers.
We‘ve been usability testing the large radio buttons recently. They work really well for less technically literate users. We’re only showing them in our simplest application and it’ll be interesting to see how they fare in more complex designs.