Remove the reset button. Almost no form needs one, and it sits beside Send looking identical. Give the form one clearly labelled send button, alone below the last field, and keep answers when an error occurs.

Every field went blank

A homeowner spends twenty minutes on an architect's quote request: the lot, the budget, the rooms, the timeline, and a long paragraph about how the family uses the house.

At the bottom are two grey buttons of the same size, side by side. She presses the left one, and every field empties at once. It was labelled Reset.

There is no undo. She closes the tab, and the architect never learns the enquiry existed.

Nothing about the form was broken. It worked exactly as designed, which is the problem.

Where the reset button came from

Early web forms often came with two buttons, one to submit and one to clear the form back to its starting values. The second made some sense when forms were new and people were unsure how to start over.

The button still exists in HTML, and it survives in old templates, copied examples and some form tools that place it beside the send button by default.

It solves a problem visitors rarely have. People who want to change an answer edit that field, and people who want to abandon a form simply leave.

Who presses it by mistake

The cost of this slip is unusual too. Most mistakes on a website can be undone with the back button; this one usually cannot.

Two buttons that look the same

The reset and send buttons are usually styled alike, with the same colour, size and shape, so the only difference is a word. Under pressure, people read shapes and positions before words.

Position adds to the confusion. Some forms put Reset on the left and Send on the right, others the reverse, and visitors bring habits from every other site they use.

A keyboard user tabbing from the last field lands on whichever button comes first in the page's code. If that is Reset, one press of Enter clears everything typed.

Nothing brings the answers back

A reset empties the form in the browser instantly, without asking. There is no confirmation, no message, and nothing the visitor can do to recover what was typed.

On a short form the loss is a minute. On a long quote request, an application or a detailed booking, it can be twenty minutes of thought, and few people type it all again.

The web's accessibility guidelines, WCAG 2.0, include helping people avoid and correct mistakes. A control that wipes out a long entry with one press works directly against that.

A worked example

A boat builder on the coast builds custom workboats and small cruisers, and most new work begins with a long enquiry form on its website.

Customers give the length, hull, engine, layout, intended use and timeline, then describe the boat they have in mind. Most spend a long time on that last box.

At the bottom sat Reset and Send, identical grey buttons, with Reset on the left. The builder heard about it twice in one spring, from customers who phoned after losing a long description.

The developer removed the reset button entirely. The send button now reads Send my enquiry, is wider and coloured like the site's links, and sits alone below the last field, aligned with it.

The form also keeps every answer if a required field is missed, and the description box saves a draft in the browser as the visitor types, so a closed tab is not the end of it.

Making the one button obvious

A form should have one main action, and its button should say what it does: Send my quote request, Book this date, Join the list. Submit tells the visitor nothing.

Place it directly below the last field, aligned with the fields, so the eye travels down and lands on it. Make it large enough to tap comfortably and give it a colour that stands out.

Give it a visible outline when it has keyboard focus, so a keyboard user can see where they are before pressing Enter.

Keeping what the visitor typed

The reset button is not the only way forms lose people's work. A form that reloads empty after an error, because one field was missed, does the same damage more often.

When something is missing, the form should come back with everything else intact, the problem field explained in words, and the cursor placed there.

Very long forms can be split into steps, each saved as the visitor goes, so nothing is lost to a dropped connection or a closed tab.

Cancel and Clear do the same damage

Some forms use Cancel or Clear instead of Reset. The wording differs, but the effect is the same: one press beside the send button discards the visitor's work.

A Cancel button that returns to the previous page is rarely needed either. The back button and the site's menu already offer every way out.

The counter-case

A few forms genuinely benefit from starting over: a calculator with many inputs, or a form used at a shared counter by one customer after another.

A very short form, such as a newsletter signup with one field, loses little if it is cleared by mistake, and its reset button matters less than a vague label on its send button.

Where clearing is needed, make it a small text link well away from the main button, labelled Clear all answers, and ask for confirmation first. The send button still deserves its place alone.

One clear button under each form

  1. List every form on the site.
  2. Remove reset, clear and cancel buttons from each.
  3. Label the send button with what it does.
  4. Place it alone below the last field.
  5. Show a clear focus outline for keyboard users.
  6. Keep every answer when a field is missed.
  7. Test each form with the keyboard alone.

Step two takes minutes and removes the worst outcome entirely. The other steps make a form better; this one stops it from destroying a visitor's work.

The same loss on a larger scale, returning customers whose passwords and order history vanished with a change of shop software, is traced in customer accounts lost when the shop moved platforms.

Frequently asked questions

Why do forms have reset buttons at all?

Early web forms often paired a submit button with one that cleared the form. Old templates, copied examples and some form tools still include it by habit, not need.

Can a visitor undo a reset?

No. The browser clears every field at once, with no confirmation and no way to recover what was typed. On a long form that can be twenty minutes of work.

Who is most likely to press it by mistake?

Keyboard users, screen magnifier users, people with limited hand control, phone users, visitors reading in a second language and anyone in a hurry, especially when both buttons look identical.

What should the send button say?

What it does, such as Send my quote request or Book this date. A label like Submit tells the visitor nothing about what happens next.

Does any form need a way to clear it?

A few do, such as calculators or forms used at a shared counter. Use a small text link away from the send button, and ask for confirmation first.

What else makes forms lose answers?

Forms that reload empty after an error. When a field is missing, the form should come back with everything else intact and the problem explained in words.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Two identical buttons under your forms?

Tell us which of your forms is longest, and we will test its buttons, labels and error handling with a keyboard.

Start a Conversation