Start with the task, not the fields
An online form may be short and still be difficult to use. A person might not know why a detail is needed, which format to enter, or whether they can fix a mistake later. Before choosing fields, define what the form must accomplish and remove questions that do not serve that purpose. Fewer questions mean fewer opportunities for confusion and error.
Put questions in an order that follows the user’s task. Group related fields under clear headings, and explain any information people may need before they begin. If a form requires an account number or a document, say so near the start rather than revealing it halfway through. For a longer process, show the main stages and whether answers can be saved. A predictable path helps people plan their time and reduces the pressure to rush.
Make every question understandable
Give each input a visible, specific label. “Phone number” is more useful than “Contact,” and “Email address for updates” explains what will happen next. Keep labels visible when someone starts typing; placeholder text inside an empty field should not be the only label. Brief instructions belong beside the relevant question, where people can use them.
Mark required fields consistently, and do not rely on color alone to distinguish them. When an answer needs a particular format, provide a simple example, such as a date written as “day month year.” Avoid demanding one exact format when the form can reasonably interpret several. For choices, use familiar controls and describe the difference between options in plain language. If a question is optional or sensitive, make that clear and explain its purpose without making people guess.
Support different ways of navigating
People may fill out a form with a keyboard, touchscreen, screen reader, voice input or a combination of tools. A form should work without a mouse: users need to be able to reach every field and button, see which control has focus, and move through controls in a sensible order. Visible labels should be associated with their inputs so assistive technology can identify each question.
Layout matters too. Keep text readable when a page is enlarged, avoid fields that become clipped on a small screen, and leave enough space to select checkboxes and buttons accurately. Do not make essential instructions depend on hovering over an icon. If the form has a time limit, explain it and, where possible, offer a way to extend the session or save progress. A person may need to pause to find a document, ask for help or simply take a break.
Treat errors as part of the journey
Error messages should tell people what went wrong and how to fix it. “Enter a date in day month year format” is more useful than “Invalid input.” Place the message close to the relevant field, identify the field in words, and make the message available to assistive technology. At the top of a long form, an error summary can help people find every issue without searching the whole page.
Keep answers in place when validation fails. Asking someone to re-enter an entire form because one field is wrong turns a small correction into a large task. Check entries at a useful point, such as when a person leaves a field or tries to continue, rather than interrupting every keystroke. Before final submission, offer a review step for details that are difficult to change later. If someone does make a mistake after submitting, explain what options, if any, are available to correct it.
Test the complete experience
Consider a hypothetical community workshop registration form. A participant enters their name and contact details, chooses a session and submits. A useful test would go beyond asking whether the submit button works: Can they tell which session they chose? Can they use the form without a mouse? If they mistype their email address, does the message explain the problem without clearing their other answers? Does the confirmation say what happens next?
Test ordinary and difficult paths, including missing answers, unexpected formats, small screens and keyboard-only navigation. Watching people attempt realistic tasks can reveal confusing wording that a technical check alone may miss. After making changes, repeat the tests: a clearer error message is valuable only if people can find it and act on it. The goal is not a form that never receives an incorrect answer. It is a form that makes the next step clear, including when something needs to be corrected.
