Skip to content
By TumWebSME
112 views
13 min

How to Design Website Form Fields: Labels, Error Messages and Mobile Keyboards That Get Customers to Finish

An office worker leans against a light grey wall, looking at her phone with a hesitant expression while filling in a form. A card summarises 6 principles for form fields: put the label above the field, error messages should say how to fix it, and match the keyboard so the phone field shows a phone keypad.

Have you ever filled in a patient history form at a clinic? Some print each field name inside the box in faint grey letters: "Full name", "Phone", "Medical conditions". As soon as you start writing over them, the faint letters disappear under your handwriting. Halfway down the page you look up to answer the nurse, and when you look back you have to squint to work out what the half-finished box was asking for.

Plenty of website forms work exactly like that every day. The field name sits inside the box in grey. The moment a customer taps the field and starts typing, the name is gone. If they make a mistake, a red message says "Invalid input" without saying what is wrong. And when they tap the phone field, their phone pops up a letter keyboard instead of a number pad.

Each of these looks minor. But a customer who reaches your form has already decided to get in touch or to buy. If they drop out here, you lose the person who was closest to becoming a sale. This article walks through form design at the level of individual fields, principles that work for any form, whether it is a contact form, a quote request form or an order form.

Try filling in your own form on your phone for 3 minutes

Before reading on, pick up your phone and open a form on your own website. Don't use a computer, because most customers fill in forms on their phones.

Do these three things.

  1. Type half a word into the first field, then ask yourself whether you can still see what the field is for.

  2. Tap the phone number field and see whether your phone shows a number pad, or a letter keyboard you have to switch yourself.

  3. Make a mistake on purpose, such as entering only 5 digits for the phone number or leaving a required field empty, then press submit. Check whether the message that appears tells you what to fix.

If all three pass, your form is already better than most. But if any of them made you stop and think, even for a second, your customers stop there too, and customers are not as patient as the person who owns the website.

Why small fields make customers abandon forms

People often fill in forms while doing something else: waiting for a bus, on a lunch break, or in the middle of a chat in another window. Their attention is interrupted all the time. A good form has to let them come back and carry on without starting again.

The problem with poorly designed fields is that each one adds a little work for the customer. They have to remember what the field is, guess what format it wants, switch keyboards, and hunt for the mistake. Each step takes only a few seconds, but together they add up to a feeling of "this is a hassle", and that feeling is what makes people close the page and tell themselves they will come back later. Most of them don't.

Another thing website owners rarely realise is that customers who fail to get through a form usually don't tell you. They don't message you to say the form is hard to use. They just leave. In your reports you only see that lots of people opened the form page and few submitted it, with no idea which field they got stuck on.

6 principles for form fields that work on any form

1. Put the label above the field, and don't use a placeholder instead

A placeholder is the grey text inside an empty field that disappears when you start typing. A label is the field name outside the box that stays there the whole time.

The Nielsen Norman Group article Placeholders in Form Fields Are Harmful explains that using placeholders instead of labels makes people who get interrupted forget what a field needs, makes it hard to check what they have already entered, and means that when the form reports an error, they have to delete their text to see what the field was. The article also points out that light grey placeholder text often has too little contrast to read easily, and that some people mistake it for data that has already been filled in, so they skip the field.

The GOV.UK Design System, the design system behind UK government websites, gives the same advice: every field needs a visible label, placed above the field, short and direct, and placeholders should not be used in place of a label or a hint.

The fix is simple. Move the field name out above the box. If you want to show an example format, such as "081 234 5678", put it in small hint text under the label instead of squeezing it into the box.

2. Make it clear which fields are required

Customers should not find out which fields are required by pressing submit and being sent back. They should know before they start.

Many websites use a red asterisk to mark required fields, which works if the form explains at the top what the asterisk means. GOV.UK takes a different approach. Its guidance on question pages recommends adding "(optional)" to the labels of optional fields, and says plainly that asterisks should not be used to mark mandatory fields. The reasoning is that if a form only asks for what it really needs, most fields should be required anyway, so marking only the ones people can skip is clearer.

Either approach can work. What matters is using the same one across the whole website.

3. Error messages must say what is wrong and how to fix it

The web accessibility standard WCAG 2.2 has two criteria that cover this directly. 3.3.1 Error Identification, at level A, requires that when an input error is detected, the field in error is identified and the error is described in text. 3.3.3 Error Suggestion, at level AA, adds that if suggestions for correction are known, they should be given to the user.

GOV.UK's error message guidance puts it even more briefly: describe what has happened and tell users how to fix it. It gives unhelpful examples such as "An error occurred" and "This field is required", and recommends instructions for empty fields, such as "Enter your first name", and descriptions for fields filled in the wrong way, such as saying how many characters a name can be.

Three more points from the same guidance apply to any form. First, put the message right next to the field in error, not only in one place at the end of the form. Second, use the same words as the label: if the label says "Mobile number", the error should also say "mobile number", not "telephone". Third, never clear what the customer has typed, in either the correct fields or the wrong ones, so they only have to fix one thing.

4. Match the keyboard to the field

This is something customers feel immediately on their phones, but website owners who test on a computer often never see it.

In a form's code, each field can set which keyboard a phone shows. MDN's inputmode documentation explains that tel shows a telephone keypad with the digits 0 to 9 plus * and #, numeric shows digits only, email shows a keyboard with an easy-to-reach @ key, and decimal shows a number pad with a decimal point.

There is one trap worth knowing. GOV.UK recommends avoiding type="number" unless user research shows a clear need, because users can accidentally change the value by scrolling. For fields such as postcodes or account numbers, use a plain text field with inputmode="numeric" instead. For phone numbers, type="tel" is fine.

You don't need to write the code yourself. Just tell your web team: "phone field gets the phone keypad, email field gets the keyboard with @, postcode field gets the number pad". A team that knows what it is doing will understand straight away.

5. Let phones fill in name, phone and address

Phones and browsers today remember their owner's name, phone number, email and address. If a form tells the browser what each field is, a customer can fill in several fields with a single tap.

What makes that work is the autocomplete value on each field. MDN's autocomplete documentation lists the standard values, such as name for a full name, email for email, tel for a phone number, street-address for an address and postal-code for a postcode.

This is about more than convenience. WCAG 2.2 criterion 1.3.5 Identify Input Purpose, at level AA, requires that fields asking for information about the user can be programmatically identified by purpose. The explanation page for this criterion says autofill helps people with memory difficulties, people with dyslexia, and people with motor impairments, which in practice also means every customer filling in a form with one thumb.

6. Only ask for what you actually use

The last principle needs no code at all. Go through your form field by field and ask: "If the customer leaves this blank, can our team still do its job?" If the answer is yes, the field should be optional, or removed altogether.

Fields that are often asked for unnecessarily on small business contact forms include a full address when nothing is being shipped yet, a company name for customers who are individuals, and a "How did you hear about us?" field that nobody ever reads. Every field you remove gives time back to the customer, and it also means you collect less personal data, which fits the PDPA points I covered in PDPA and your business website's contact form.

Error messages before and after

Here are some messages you often see on forms, compared with messages that tell the customer what to do next.

Field

Common message

Message that says how to fix it

Mobile number

Invalid input

Enter a 10-digit mobile number, for example 0812345678

Email

Invalid email

Enter an email address with an @, for example name@example.com

Full name

Please complete all fields

Enter your full name

Project details

An error occurred

Describe your project in 500 characters or less

Notice that the messages on the right use the same words as the field name, start with what the customer needs to do, and avoid words like "invalid" that sound like a telling-off. The customer hasn't done anything wrong. They just don't know yet what format the system wants.

"Placeholders make the form look cleaner and save space"

That's true, and I'm not arguing with it. A form without labels above the fields looks lighter and shorter, and on a small phone screen every line you save counts. Many designers choose this style for good reasons.

But that cleanness only lasts while the form is empty. Once a customer has filled in three fields, the form shows only what they typed, with no field names. If they want to check before pressing submit, they have to guess from the content which field is which. The compromise NN/g mentions is the floating label, which starts inside the field and moves above it when the user starts typing. That is better than a placeholder alone, but if there is room, a label that stays outside the field is still the clearest option.

"Our form only has 3 fields, so there's not much to think about"

Short forms really do have an advantage, and if yours only asks for a name, a phone number and a message, you have already done a good job of cutting unnecessary fields.

But those three fields are usually the three most important ones. If the phone field shows a letter keyboard, the customer has to switch it themselves. If they miss one digit and the form only says "Invalid input", they may not see what is wrong. And if the form accepts a wrong number, your sales team can't call them back. The shorter the form, the harder each field has to work, because there is no other field to help you reach that customer.

Why fixing this now is better than waiting for a new website

Many people plan to fix their forms when the whole website is redesigned. But all 6 principles in this article are fixes at the field level. They don't change how the website looks or the back-office system, and a web team can make them quickly.

While you wait for a redesign, every day the form is hard to use is a day some customers quietly close the page. And when the new website does happen, you will have before-and-after numbers to compare, so you know what worked instead of starting from guesswork.

The minimum your web team can fix in a day

If time is short, start with these four.

  • Move every field name out above its box.

  • Set the phone field to show the phone keypad and the email field to show the keyboard with @.

  • Rewrite the error message for each field so it says how to fix the problem, using the same words as the field name.

  • Add autocomplete values to the name, phone, email and address fields.

None of these changes how the website looks, but customers filling in the form will feel straight away that it is easier.

If your shop still collects information through Google Forms, you can only change a few of these, because the form's look and code belong to Google. I covered when it is worth moving to a form on your own website in Google Forms vs a Website Form.

Real examples you can open and look at

If you want to see forms that follow every one of these principles, open the GOV.UK Design System. Its text input and error message pages have live examples you can try, showing labels above fields, hint text under labels, and red error messages right next to the field. The system is designed for an entire country to use, from teenagers to older people, which makes it a good example of forms that have to work for everyone.

Another free source is W3C's explanation pages for the WCAG 2.2 criteria. W3C is the body that maintains web standards, and each page includes examples of techniques that pass and examples that fail, which are useful to share with your web team when you discuss what to fix.

A case from our own work: Matang Cosmetic

In TumWebSME's own work, the most relevant case is the website for Matang Cosmetic, a cosmetics manufacturer. Our portfolio page states that the site has a consultation and quotation request form designed to turn visitors into business partners.

A form like this is where all 6 principles matter most, because the people filling it in are serious about becoming partners, and the details they enter are what the sales team uses to reply. If a phone number is off by one digit because the keyboard was awkward, or someone gives up halfway because they can't tell which fields are required, the business loses a partner without anyone noticing.

A five-step plan for this week

  1. Do the 3-minute test above on every form on your website: contact forms, quote request forms and order forms.

  2. Note which forms use placeholders instead of labels, which fields show the wrong keyboard, and which error messages don't say how to fix the problem.

  3. Go through every field with the question "If the customer leaves this blank, can our team still do its job?", and remove it or make it optional.

  4. Rewrite the error message for each field, then send the whole list to your web team to fix in one round.

  5. Once it is fixed, ask someone who has never seen your website to fill in the form on their own phone, and watch where they get stuck.

Step 5 doesn't require hiring anyone. A family member or friend is fine. I described this kind of test in detail in Hand Your Website to Your Parents for 5 Minutes.

How to tell whether the fixes worked

The first measure is the completion rate: the number of successful form submissions divided by the number of people who opened the form page, comparing the same length of time before and after the fix. If your website already runs Google Analytics 4, your web team can set it up to count successful submissions.

The second measure is the quality of the data you receive. Count how many submissions each month have a phone number that doesn't work or an email address that bounces. This number should drop after you fix the keyboards and error messages.

The third measure is behaviour on the form page. If you want to see which field customers get stuck on, a free tool such as Microsoft Clarity can show where people click repeatedly or stop. I covered how to set it up, and which data to mask before you start recording, in Microsoft Clarity for Small Business.

Back to the patient history form

Clinics that care about their patients usually fix their forms in simple ways: they print field names clearly outside the boxes, add an example under the fields people often get wrong, and have a nurse point out which fields can be skipped. Patients don't feel the form looks any nicer, but they finish faster without having to ask anyone.

Website forms are the same. Customers don't come to admire your form. They come to get in touch with you. Labels that stay put, messages that explain how to fix things, and the right keyboard for each field let them reach the submit button without stopping to think, and then you get to talk to the people who really meant to contact you.

Want us to take a look at your website's forms?

Send us your website link. We'll tell you which field your contact or order form is losing people on, and what to fix first. The first consultation is free.

See all our services and packages on the TumWebSME packages page.


Follow TumWebSME

Follow more articles on website building and online marketing at:

Contact us for work inquiries

  • 088-983-9386 (Ploy)

  • 099-856-3198 (Sannan)

Keywords:

web form design
online form
contact form

FAQ: Frequently Asked Questions about This Article

A collection of questions and answers to help you better understand the content of this article.

A label is the field name outside the box that stays visible, while a placeholder is grey text inside the box that disappears when you start typing. Both Nielsen Norman Group and GOV.UK recommend giving every field a visible label and not using a placeholder instead of one. If you want to show an example format, put it in small hint text under the label, so it stays readable after the customer starts typing.

Say which field is wrong and how to fix it, which matches WCAG 2.2 criteria 3.3.1 and 3.3.3. For example, instead of Invalid input, write Enter a 10-digit mobile number, for example 0812345678. Put the message next to the field in error, use the same words as the field label, and never clear what the customer has already typed.

Use tel. MDN says this makes phones show a telephone keypad with digits plus the * and # keys. GOV.UK recommends avoiding type number unless user research shows a clear need, because users can accidentally change the value by scrolling. For other numeric fields such as postcodes, use a plain text field with inputmode set to numeric.

You can, as long as the form explains what the asterisk means. GOV.UK takes another approach: it adds optional to the labels of fields that are not required and does not use asterisks for required fields at all, because a form that only asks for what it needs will have mostly required fields anyway. Whichever you choose, use it consistently across the whole website.

Not for fields like name, phone, email and address. WCAG 2.2 criterion 1.3.5 requires fields asking for the user's own information to identify their purpose so browsers can fill them in, which helps people with memory difficulties or who find typing hard. For password fields, MDN notes that browsers may ignore autocomplete off on login pages anyway, to support password managers.

Some of it. You can write clearer questions, remove ones you don't use, and choose which questions are required. But the look of the fields, the keyboard a phone shows, autocomplete values and most error messages are controlled by Google. If that form is the main way new customers contact you or order from you, a form on your own website gives you control over all of these details.

Free Consultation

We are happy to provide consultation on website and system services to be a tool for growing your business.

Address : 89 Ramkhamhaeng 82 Alley, Ramkhamhaeng Road, Huamark Subdistrict, Bang Kapi District, Bangkok 10240, Thailand.

Business Hours : 09:00 - 21:00 (Open Daily)

Or follow us

FacebookInstagram
TikTok

Let us contact you

Fill in your name, email and phone, tick the consent box, and wait for the bot check before sending.