Build good forms

Here you will find tips and UX examples for designing forms. Whether a form works well depends not only on its design but very much on the context it sits in. These notes are therefore general, and in a particular case it can make sense to depart from them.

Here you will find tips and UX examples for designing forms. Whether a form works well depends not only on its design but very much on the context it sits in. These notes are therefore general, and in a particular case it can make sense to depart from them.

I. General

1. Multi-level forms instead of one-page forms

Split your form into two or three steps. This almost always makes it easier to fill in, and there are three reasons why multi-step forms work so well:

  • At first glance, a multi-step form is less intimidating than a long form with many fields.
  • You can save sensitive details such as email or phone for the last step. Users are then more likely to fill in these fields, because they don’t want to lose the progress they made in the earlier steps. This cognitive bias is known as the “sunk cost fallacy”.
  • A progress bar motivates users to complete the form. Here, too, a known cognitive bias is at work: people like to finish what is half done.

2. Remove fields that are not required.

Every additional field in your form costs you enquiries. So ask yourself, for each question, whether it is worth that loss.

3. Use conditional logic to shorten.

With conditional logic, sometimes called branching logic, a question only appears if a previous question was answered in a certain way. Questions that don’t matter to some users never appear for them. Your form becomes shorter on average, and fewer people abandon it.

4. Top left aligned field names are most readable.

UX researchers found that people complete a form faster when the labels sit left-aligned above the fields. The eye then needs fewer “visual fixations”, fewer points at which it stops. I describe an acceptable alternative to labels above the field in point 16.

5. Avoid asking questions side by side.

Eye-tracking studies have shown that simple single-column layouts work better than multi-column layouts with questions side by side. This also applies to dates and times: a single field with a clearly stated format works better than day, month and year side by side (see no. 12).

6. Give people a reason to use your form.

Imagine a form that takes an hour to fill in. Nobody would complete it, unless you gave everyone who did a trip to the Bahamas. That promise would be reason enough to push through, despite the long and tiresome experience. The example is exaggerated, but it shows how much motivation matters in a form.

7. Group related fields into sections or steps.

If your form has more than six fields, group the questions into logical sections or steps.

II. Questions & field types

8. Select field types that reduce the number of clicks required to complete.

Every extra click takes effort, and at every one someone may give up. So choose field types that need as few clicks as possible.

9. Use smart presets.

If you ask for a “phone number” or a “country”, suggest a dialling code or a country based on the user’s IP address.

10. Use radio buttons, checkboxes and dropdown lists instead of free text fields.

11. Radio buttons should be arranged vertically.

Radio buttons and checkboxes arranged vertically are quicker to take in than a horizontal layout.

12. Do not use split fields when requesting phone numbers or birth dates.

Split fields force users to make extra clicks to get to the next field. A single field is better, with the format clearly shown in the placeholder. Even if the cursor jumps to the next field automatically, one drawback remains: split fields need stricter validation, and that can backfire.

13. Confidential information

People are increasingly concerned about how their data is protected. If you need to ask for confidential information, explain clearly why you need it, ideally in a help text directly below the field.

14. When querying addresses, use a postcode search to reduce field entry.

If users need to give their address, it is best to ask only for the house number and postcode. A service can then suggest the full address.

15. Use placeholders correctly

A placeholder is the light text that appears in an empty form field. It should help users when it is unclear what belongs in the field. So a field like “First name” probably doesn’t need one.

16. Always display a field identifier

A field identifier is the question text above the field. It should always be visible and never be replaced by a placeholder, because the placeholder disappears as soon as someone starts typing. Users then have to remember what was asked. The only acceptable way to do without a label above the field is an inline label. This hybrid always stays in view but takes up less height than a label above the field.

17. Use predictive search for fields with many predefined options.

If users need to select their country, profession or anything else from a long list of predefined options, it is best to offer a predictive search. This saves typing and reduces the cognitive load.

III. Individual fields

18. Optional questions

If you have to ask an optional question, mark it clearly as optional. My recommendation, though, is to remove optional questions or to ask them only after users have submitted their data. If you are still required to ask them first, use the placeholder to make clear that they are optional.

19. Pictures

Selectable images are among the most engaging question types.

20. Phone number

Think carefully before you ask for a phone number. People are less and less willing to share their number, and if you ask for it anyway, the drop-out rate will very likely rise significantly.

21. Input fields should be dimensioned according to the expected input.

The size of a field should reflect how much text users are likely to enter. Fields for a postcode or house number should therefore be shorter than the field for the street name.

IV. User friendliness

22. Captchas

Avoid captchas. They push the work of fighting spam onto your users, interrupt the flow and in the end put people off. Better alternatives are an automated spam filter such as Akismet, a very simple sum (such as 1 plus 3) or a “honeypot” with hidden fields. A captcha should be the very last resort.

23. Colours

Don’t rely on colour alone to communicate. According to Colour Blind Awareness, about one in 12 men and one in 200 women have some degree of colour blindness. So when you show a validation error or a success message, don’t mark the field only in red or green. Wherever you use colour, add text or icons so that the message reaches every user.

24. Make sure that your entire form is navigable with the tab key.

Many users move through forms with the tab key. This matters most for people with disabilities who rely on software that uses the tab function to move from one question to the next.

25. Difficult questions

If you ask a question that users may not understand, explain it clearly and guide them to the right answer. One way is a hint that appears when you hover over a question mark.

26. Does your form work on all popular browsers and devices?

It may sound like common sense, but it is worth checking that your forms work, and are easy to use, in all popular browsers and on all popular devices. When in doubt, a service like BrowserStack will help.

27. Is your form easy to use in bright or low light conditions?

If people are likely to use your forms outdoors on their phones, your fields need to stand out clearly from the background. Otherwise users may not see where to type.

28. Make sure that nothing flashes more than three times per second.

If you plan to use blinking cursors, animated progress bars, GIFs or anything else that blinks, make sure none of it blinks more than three times per second, as WCAG success criterion 2.3.1 requires. Faster blinking can trigger seizures in some people.

29. Enable browser auto-fill.

Browsers such as Google Chrome and Firefox can fill in forms automatically, so users can complete standard fields with one click. To know what a field expects, the browser looks at its name, label and placeholder. So label your fields with terms a browser will recognise, such as “email”, “first name” or “city”.

30. Use step-by-step forms

How do you keep a form short enough not to scare anyone away, and still collect more information from people who are happy to give it? Step-by-step forms are one option. Users can submit them once they reach a certain step, and anyone who wants to can add more information afterwards.

31. Optimise the speed of your forms.

Users expect websites and forms to load quickly. If you want to increase your conversions, make your form as fast as possible.

32. Automatic “next”

Avoid automatic advancing, where the form jumps to the next question by itself. Hardly anyone expects it, and it confuses people.

33. Use visual cues and icons to make form fields more intuitive.

Our brains process images much faster than text. Visual cues are therefore a good way to show how a field should be filled in.

V. Input validation & error handling

34. Do not validate too strictly

Strict validation makes programming easy and life hard for users. If there are many ways to fill in a field, such as a phone number written as +12345678912, +44 12345678912 or 012345678912, your developers should write a rule that converts all of them to one consistent format. A placeholder that clearly shows the expected format helps as well.

35. Avoid double confirmation.

Ask for an email address and a password only once. To let people check what they typed, an icon or a checkbox that shows the password when clicked works better.

36. Validate correctly.

Check entries right at the field, to the right of it, and report errors early, not only when users click “Send”. This inline validation should not run in real time, though, or it will report errors before the field has been filled in. Ideally, the message appears about 500 ms after users have finished typing.

VI. Trust

37. Attractive design

It has been shown that people trust “beautifully” designed forms and websites more than less attractive ones.

38. Fix possible problems near your form.

There are probably a number of reasons why people might feel uneasy about your form. Typical questions are “How long will it take to fill in?”, “Will I have to enter my credit card details?” or “Will I get annoying calls from a salesperson?” If you answer such questions in advance, users will trust you more.

39. Show a strong trust note in close proximity to your form.

Statements such as “used by 100,000 people” and testimonials from people in a similar situation are strong cues. They make users more likely to trust you and fill in your form.

40. Be careful with seals, unless you require payment.

People associate privacy and security seals with payment. Adding a seal can therefore even lower your conversion rate, because visitors think they are about to pay for something.

41. Display live chat or contact information in the view of your form.

For more complex forms, where users may have questions about the form itself, this works very well. It lets prospective customers clear up anything that still keeps them from filling in your form.

VII. Multi-level forms & progress bars

42. When using multi-level forms, you should always display a progress bar.

A progress bar encourages people to finish. It eases your users’ uncertainty, because it shows clearly how far they still have to go. If the bar starts with part of the way already marked as done, even more people will complete the form.

43. Pay attention to your transition speeds.

If the transition between two steps is too fast, users may not notice that the content has changed. They click “Next”, seem to see the same thing and give up. A slightly slower transition makes the new step visible. We are often told that faster is better, but not when it comes to transitions.

44. Use clear signage

A progress bar alone is not enough. Also show the total number of steps and the step the user is currently on, so that nothing is left unclear.

VIII. Buttons & Call-to-Action

45. Calls to action should end the sentence “I want …”

Many forms use dull buttons such as “Submit” or “Send”. Replace them with a call to action that says what users want to achieve with your form. A good rule of thumb: from the user’s point of view, the label completes the sentence “I want …”. For a form requesting a free consultation, for example, the button could read “Request my free consultation”.

46. Make sure that the call-to-action contrasts strongly.

You may have heard of those infamous studies in which changing the colour of a button increased conversions. Taken literally, such studies are misleading, because what usually matters is not the colour but the contrast.

47. The call-to-action should have the same width as the fields.

A large, full-width call to action that contrasts sharply with the background is easy to find. If the button is as wide as the fields, nobody has to wonder where it is.

48. Avoid using the “Clear” or “Reset” keys.

Some forms offer a button next to “Continue” or “Submit” that clears all fields. The risk of accidentally deleting everything you entered outweighs the small convenience of being able to start over. Most users know anyway that they can reload the page or overwrite their entries to start again. So leave out cancel and reset buttons.

49. Arrange your questions logically.

When you ask for credit card details, for example, ask for them in the order in which they appear on the card: card number, expiry date, security code.

50. Do not place too complicated legal messages near your keys.

If your users have to agree to a lot of complex disclaimers, bundle them in as few places as possible. Keep legal notices as concise as you can.

51. No automatic inclusion in mailing list

Ask before you add anyone to your mailing list. Adding people automatically deceives them and looks manipulative, and most of them then need an extra click to unsubscribe. It also violates the GDPR.

52. Clearly explain what happens next when you click on the “Send” button.

Someone filling in your form may wonder how long they will have to wait, whether they need to prepare anything, or what happens now. Ideally, your form then takes them to a page that says clearly what will happen next and what they can expect.

53. Send button

Deactivate the “Send” button once it has been clicked. This prevents duplicate submissions and at the same time shows users that sending worked.

54. Make it clear what users can expect next.

Your call to action, and your landing page as a whole, should say clearly what users can expect once they have filled in your form.

55. Use native functions

Use the native features of the mobile device (camera, geolocation, date selection) to simplify tasks.

56. Question fields and buttons should be at least 48 pixels high.

An adult’s fingertip is about 10 mm wide on average. On the web, that is about 48 pixels. So if your forms will be used on mobile devices, make your fields at least 48 pixels high.

57. All form labels and placeholders should be at least 16px.

Smaller text is hard to read on a phone, and all the more so if you are designing forms for older users.

58. HTML input types

Have you ever noticed that a phone shows a different keyboard depending on the question, sometimes with a “.com” key, sometimes with a date picker? That is the work of HTML input types. Choose the right type for each field, and the right keyboard appears. This is a great help in mobile form design. Eight input types are relevant for forms:

  • input type="text" shows the normal keyboard of the mobile device.
  • input type="email" shows the normal keyboard plus “@” and “.com”.
  • input type="tel" shows the numeric keypad with 0 to 9.
  • input type="number" shows a keyboard with numbers and symbols.
  • input type="password" hides the characters as they are typed.
  • input type="date" shows the phone’s date picker.
  • input type="datetime-local" shows the phone’s date and time picker.
  • input type="month" shows the phone’s month and year picker.

More tips, tricks & kits

100 tips for a better user experience

User experience design aims to leave users satisfied. It does so by making websites easier to use, more accessible and more efficient […]

Web Design | Tools & Resources

Here you will find tools for developing websites, such as tutorials on Codrops and Codepen. For HTML there is a validator, a cheat sheet and a reference of elements and their properties […]

Want to apply some of this in a project?

Let us talk about your project.

Call +49 228 629 380 60 I can be reached on working days. If I cannot pick up, I will call you back. Book appointment Take a free slot in the calendar A short conversation clears up a lot.