A confusing form can prevent a customer from asking a question, booking a service or completing a purchase. Clear labels, understandable errors and keyboard access make those tasks easier for more people.
Forms are where advertising and customer service meet. A visitor may find the right business, understand its offer and still abandon the process because a field is unclear or an error message does not explain how to continue.
Accessible design addresses barriers for people with disabilities, including people who use screen readers, keyboards or magnification. Clearer forms can help others too, including someone using a phone in bright light or completing an application under time pressure.
Tell people what each field requires
A visible label should identify each input. “Email address” tells a customer what to enter; a box with only a disappearing example can leave the person guessing after they start typing.
The World Wide Web Consortium’s form guidance recommends associating labels with their controls, providing instructions and helping users recover from errors. An accessible name used by assistive technology is necessary, but it does not replace clear instructions visible to everyone.
Show required fields and any constraints before submission. If a business needs a particular date format or a file of a certain size, explain that beside the field. Avoid asking for information the company has no clear reason to collect.
Make errors specific and recoverable
“Something went wrong” tells the customer little. “Enter an email address in the format name@example.com” identifies the field and suggests a correction. Where a form has several errors, a summary at the top can guide people to the affected fields, with the relevant message repeated beside each one.
Preserve information already entered where possible. A customer who corrects a phone number should not have to rewrite a long inquiry. Do not rely on red color alone to indicate an error, because some users will not perceive the color difference.
The UK Home Office’s error-message guidance recommends clear instructions and an error summary for submitted forms. Its patterns are a starting point for testing, not a substitute for checking how a particular form behaves.
Test the entire journey
Use only a keyboard to move through the form. Can you see which control has focus, reach every field and button, select options and submit? Then check the form with a screen reader and at enlarged text sizes. Test on mobile as well as desktop.
These checks should include what happens after submission. A confirmation page should say whether the request was received and what happens next. If the company sends an email, make sure the address or delivery process does not prevent a customer from knowing whether the request arrived.
Automated accessibility tools can catch some technical defects, but they cannot establish that instructions make sense to real customers. Observing people, including disabled users, complete realistic tasks can reveal barriers that a checklist misses. Obtain appropriate consent and avoid collecting unnecessary personal information during testing.
Use the numbers carefully
A business might track how many people start a form, encounter an error and submit it. Define each event before comparing results, and check that analytics reflect the permissions users have given. A lower completion rate can have several causes, including changes in traffic or the offer itself.
Removing a necessary field may raise submissions while making it harder to deliver the service. Judge form changes against completed customer outcomes and the quality of requests, not just the number of clicks. Our explainer on marketing tools covers other ways businesses collect and use customer information.
