Button and form text should explain actions and their results
Button and form guidance should explain the action and what happens next. The short text used in buttons, field instructions, error messages, and confirmations is called microcopy.
A button that sends an inquiry can say Send inquiry; a button that retrieves a document can say Download service guide. Claims such as Free, No registration required, and Reply within one business day need to match the service. Measure the effect of wording changes after publishing.
Explain the operation and what happens after submission
Review guidance before an action, during entry, and after submission as one process. Buttons, fields, errors, and confirmation messages each need wording that matches what happens at that stage.
Name the button's action and content
A button label should describe the operation it starts. Keep the surrounding promise consistent with that operation.
| Vague label | More specific label | Use it when |
|---|
| Submit | Send inquiry | The form sends a request |
| Learn more | View pricing | The link opens pricing details |
| Download | Download service guide | The button retrieves that document |
| Register | Create account | The action creates a user account |
Evaluate meaning as well as length. W3C's guidance on headings and labels emphasizes descriptions that identify their content. (W3C headings and labels)
Book a free consultation fits a process that books a consultation without a charge. A form that only submits a booking request needs wording that reflects that request.
Label fields with the information requested, such as Name, Email address, and Project details. Supporting text can explain required fields, expected formats, and details needed to discuss the request.
For a project field, an instruction might ask for the work required and the preferred timeline. Use restrictions that reflect the information the business actually needs.
Keep labels and essential instructions visible during entry. W3C describes ways to associate instructions with fields. (W3C form instructions)
Identify the field and the correction in an error message
An error message should name the rejected input and explain how to correct it. W3C requires known correction suggestions for detected input errors, with exceptions where they would compromise security or the purpose of the content. (W3C error suggestion)
| Vague message | A specific correction |
|---|
| Invalid input | Include an @ symbol in the email address |
| Required field | Enter your project details |
| Invalid date | Enter the preferred date as YYYY-MM-DD, for example 2026-10-12 |
The date example applies to a form that accepts that format. Use the actual accepted format in your instructions.
A connection failure needs a different explanation from an invalid field. Before recommending another submission, the system should establish whether the request was already received, so the wording helps avoid duplicate requests.
Confirm what succeeded and what follows
A confirmation should state the result: an inquiry was received, a document is available, or an appointment was booked. An inquiry received and an appointment confirmed describe different outcomes.
Any reply estimate should match operating hours and business-day rules. W3C's form-notification guidance describes informing users about success and errors. (W3C form notifications)
The message can also explain how to correct a submitted request or what to do if an acknowledgment email fails to arrive, when those instructions match the service.
Measure clicks and completed submissions separately
Separate button clicks from completed inquiries when evaluating a change. More clicks can coexist with more abandoned forms.
Two example measures are:
- Button click rate: the share of sessions where the button was displayed that included at least one click on it.
- Form completion rate: the share of sessions where entry began that included at least one successful submission.
A session is the unit an analytics system uses for a visit. These definitions describe session-based measures, which differ from the number of inquiries. Count repeated actions consistently across comparisons.
If traffic sources or service prices change at the same time, a before-and-after difference cannot be attributed to wording alone. Set the comparison and measurement rules before publishing a variation.
Keep the wording consistent with the service
Read the button labels, instructions, errors, and confirmation as one process. Each statement should match what the system and the business do. Update website descriptions and form guidance when terms or response methods change.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To build a website where you can keep service descriptions and contact guidance up to date, give SpreadSite a try!
Build a website with SpreadSite →
