Forms should have a natural flow and feel like a conversation between the site and the user.
A form consists of most of the following features. Using these features across all forms helps create a structure and language that users identify with.
Easy to understand title of the form.
Helps the user know they are in the right place. A brief description of what the purpose of the form is, with links to any guidance.
Helps the user know how much they have still to do and encourages them to finish. For long forms users should have the option to save at any stage and pick it up later. If steps within the form can be skipped then “steps # of #” should be changed to “part # of #”.
Indicate to the user which fields need to be filled in.
If there is an error, after a submission or on next step there should be a bulleted list of errors indicating the field(s) with the issue. The help on how to fix it should be in plain English and each list item (in the playback box) should link to the affected field. The field validation text should be displayed directly below the field as well as any extra error messages. https://www.nngroup.com/articles/error-message-guidelines/
The fields of the form should be ordered in a logical and structured manner making it easier for the user to fill out the form.
Forward and backward buttons/pagination
On multipage forms the user should always be able to navigate forward and back without losing their answers. The only thing that should stop a user progressing is an invalid input.
When entering personal details, it is important that users know what is going to happen with that data and that they are given the opportunity to consent to this use. Users will not be able to submit without consent. For long consent statements an accordion can be used to hide and show content.
There should be a button that finalises and submits the user input. When submitting, there should be a spinner to show that there is an action, followed by a success page, failure page or playback error message.