UX Foundations · Step 5 · 7 min read
Forms
Forms are where people sign up, pay and apply, and where many give up. How to ask fewer questions, label every field, start with one thing per page, and show errors next to the field with a way to fix them, based on GOV.UK Design System guidance, NN/g research and Luke Wroblewski's Web Form Design.
A form is a conversation in which only one side can talk. You ask the questions in writing, and people can't ask you what you meant. So every word, every label and every error message has to do the job a patient person would do face to face. Forms are also where the money is: sign-up, checkout, applications. A small improvement here helps more people than almost anything else you'll design.
What you'll be able to do after reading:
- Cut a form down to the questions you really need
- Write clear labels and hints, and avoid placeholder text as labels
- Decide when to split a form into one question per page
- Write error messages that appear in the right place and say how to fix the problem
1. Why forms deserve care
Know why you need every question.
Cut what you can't justifyA visible label above each field.
Not a placeholderStart with one question per page.
Merge only if research says soNext to the field, saying how to fix it.
After the person finishes typingSmall details in forms change results. A study by Seckler and colleagues (CHI 2014), summarised by NN/g, found that people filling in forms that followed basic guidelines were "almost twice as likely to submit the form with no errors from the first try": 78% against 42% (NN/g, Whitenton, Website Forms Usability: Top 10 Recommendations, 2016).
Luke Wroblewski's Web Form Design: Filling in the Blanks (Rosenfeld Media, 2008) is still the classic book on the subject, and many of today's guidelines trace back to it.
2. Ask less
Every question costs people time and trust. The GOV.UK Service Manual tells teams to "know why you're asking every question" (GOV.UK, Structuring forms). NN/g's first recommendation is the same: "Keep it short".
For each field, ask your team:
- Do we need it? Who uses this answer, and for what?
- Do we need it now? Could we ask later, when it's needed?
- Do we already know it? Could we look it up or reuse it?
3. Label every field
- Visible labels, above the field. GOV.UK: "All text inputs must have labels, and in most cases the label should be visible. You should align labels above the text input they refer to" (GOV.UK Design System, Text input).
- No placeholder as label. Grey text inside the field disappears as soon as people type. NN/g: placeholder text "makes it difficult for people to remember what information belongs in a field, and to check for and fix errors" (NN/g, Sherwin, Placeholders in Form Fields Are Harmful, 2014).
- Hints for format. If you need a format, say it before people type: "For example, 27 3 2007".
- Mark required fields. NN/g recommends an asterisk for required fields, and warns that "only marking optional fields makes it difficult for people to fill out the form" (NN/g, Budiu, Marking Required Fields in Forms, 2019).
- One column. NN/g also recommends a single-column layout and fields sized to the expected answer.
4. One thing per page
GOV.UK's advice for long services is to "start by splitting the form across multiple pages with each page containing just one thing", for example one question or one decision. It adds: "User research will tell you when you can merge pages together" (GOV.UK, Structuring forms). Each page then has one clear question as its heading (GOV.UK Design System, Question pages).
This isn't a rule for every form. A login with two fields is fine on one page. But for applications, claims and checkouts, one question at a time makes each step easy, works well on phones, and lets you skip questions that don't apply.
5. Errors next to the field
When something is wrong, show it where it happened, say what is wrong and how to fix it.
- GOV.UK: "Show an error message next to the field and in the Error summary component when there is a validation error" (GOV.UK Design System, Error message). The summary goes at the top of the page and links to each field.
- NN/g's guidelines for errors in forms include "Aim for Inline Validation Whenever Possible", "Keep Error Messages Next to Fields" and "Don't Validate Fields Before Input is Complete" (NN/g, Krause, 10 Design Guidelines for Reporting Errors in Forms, 2019).
- In Wroblewski's test of inline validation, the best version showed "a 22% increase in success rates" and "a 42% decrease in completion times" against a form that checked only on submit (Wroblewski, Inline Validation in Web Forms, A List Apart, 2009). It was a single study of one sign-up form, so treat the numbers as a direction, not a promise.
A worked example: rewriting errors
| Before | After | Why |
|---|---|---|
| "Invalid input" | "Enter your date of birth" (the format example stays in the hint) | Says which field; GOV.UK says not to repeat an example that is already on the screen |
| "Error: field required" | "Enter your first name" | GOV.UK's style: a plain instruction |
| "Password does not meet requirements" | "Password must have at least 8 characters" | Says the exact rule |
| A red banner at the top only | The same message next to the field, plus a summary that links to it | People see where to fix it |
GOV.UK also asks you to avoid words like "please", "sorry", "valid" and "invalid", "forbidden" and "you forgot", jokes like "oops", and technical jargon such as "error 0x0000000643".
6. Common mistakes
- Asking for data "just in case" (phone number, gender, company size) with no use for it.
- Placeholder text as the only label.
- Showing errors while people are still typing, or only after the whole form is sent.
- Vague errors ("Something went wrong") with no way to fix them.
- Clearing everything people typed when one field is wrong.
- Two or three columns of fields, so people miss some.
7. Vocabulary
| Term | Meaning |
|---|---|
| Label | The visible name of a field, telling people what to enter |
| Hint text | Short help under the label, such as the expected format |
| Placeholder | Grey text inside an empty field; disappears when typing starts |
| Inline validation | Checking a field as soon as people finish it |
| Error summary | A list of all errors at the top of the page, linking to each field |
| Question page | A page that asks one question, used as its heading |
8. Try it (no tools needed)
- Find a paper or online form you filled in recently (a gym sign-up, a delivery form, a doctor's registration).
- For every field, write: "Do they need it? Now? Do they already know it?" Cross out what fails.
- Pick one error message from any form you use and rewrite it so it says what's wrong and how to fix it.
Then do the full Redesign a form lab.
Reflection questions: Which form made you give up, and at which question? What would have kept you going?
9. If you already practise
- Write a "question protocol": a table of every field, who uses the answer and why. GOV.UK recommends this approach, and it ends many debates.
- Test forms with real data, not "John Smith": long names, two surnames, foreign addresses, no postcode.
- Review error messages with a content designer as part of the design, not after development.
Checklist
Learn more
- GOV.UK: Structuring forms (2016, updated 2018) · Design System: Question pages · Text input · Error message · Error summary
- NN/g: Website Forms Usability: Top 10 Recommendations (2016) · Placeholders in Form Fields Are Harmful (2014) · Marking Required Fields in Forms (2019) · 10 Design Guidelines for Reporting Errors in Forms (2019)
- Luke Wroblewski: Inline Validation in Web Forms (A List Apart, 2009)
Books, courses and videos to go deeper
- Web Form Design: Filling in the BlanksLuke WroblewskiBook · Rosenfeld Media, 2008 (external site)
- Forms that Work: Designing Web Forms for UsabilityCaroline Jarrett and Gerry GaffneyBook · Morgan Kaufmann, 2008 (Amazon)
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
Redesign a form · Affordances, signifiers and feedback · Interface states: empty, loading, error, success · Content first · Users, tasks and context