Grammar in UX Writing for Buttons, Forms, and Messages

UX writing is writing the text people use to navigate a digital product, make decisions, and complete tasks. UX stands for user experience. The short pieces of text that do this work are often called microcopy. They include field labels, button text, hints, error messages, and status updates.

Grammar tells people who acts, what the action does, and when it happens. Follow a fictional community center’s room-booking form from the first instruction to the final confirmation to see how those choices work together.

Write labels and actions for the task

A field label can be a noun phrase, a group of words built around a noun. Number of people names the information the field collects. A status can use a fragment, a group of words that does the job without forming a complete sentence. Awaiting staff review works when the heading or context makes clear what is being reviewed. Use a complete sentence when readers need to know who acts or what happens next.

Give buttons a verb and a clear object

An imperative verb tells someone what to do. Review booking request starts with the imperative review. The understood subject is you, and booking request tells you what you’ll review. Choose a verb that matches the button’s effect. In this service, reviewing opens a preview and sending submits the request to staff. GOV.UK Design System guidance on button text.

Keep names and points of view consistent

Use booking request for the item staff must review and booking once staff confirm the room. Carry those terms from the form to the email. In instructions, you and your refer to the person making the request. Name staff when they act, as in Center staff will review your request and email you with their decision. Listen for the terms people use when they describe the task and check whether they understand the terms in the interface.

Follow a room-booking request from form to confirmation

The center’s small meeting room holds up to eight people, and larger rooms are available. Visitors can save a draft, review a request, and send it to staff. Staff decide whether to confirm the booking. Here’s the copy a visitor might see at each point.

Shorten the field instruction and keep the rule

Before. Please provide the total number of individuals who will be in attendance, including yourself, in the form of a whole number between one and eight, inclusive.

After. Enter a whole number from 1 to 8. Include yourself.

Enter names the immediate action. Whole number keeps the format, and from 1 to 8 keeps the limits. The second sentence makes it clear that the visitor counts toward the room’s capacity.

Keep the voice consistent and adjust the tone

Voice is the recognizable way a service speaks. The center uses everyday words, addresses visitors directly, and names who does what. Tone is the attitude a message conveys in a particular situation. The field hint is matter-of-fact. The capacity error stays calm and gives the visitor options. The confirmation can include a brief welcome after the room, time, and check-in details.

Grammar helps carry those changes. Use a statement to explain what happened, an imperative to give a next step, and an if clause when a step applies only in certain circumstances. In If your group has more than 8 people, choose a larger room, the condition makes clear who needs to act.

Write inclusive and accessible interface text

Name roles without making assumptions

You works for anyone completing the form. If a second person needs to be named, use their role. Enter the group organizer’s email address identifies whose address the center needs without assuming their gender or relationship to the visitor. Ask for details that serve the task.

Make instructions and errors easy to identify

Keep Number of people visible as the field label. Put the range and counting rule beside the field and have the implementation associate the label, hint, and any error with the input. Describe the problem in text so a red border is an additional cue. Use descriptive links such as View room sizes so the destination is clear when the link is read on its own. W3C guidance on form instructions, WCAG guidance on error identification, and WCAG guidance on use of color.

Explain what went wrong or what happened next

Give a reason and a way to recover

Invalid number leaves the visitor guessing whether the problem is the format or the room capacity. In the worked example, the first sentence gives the room limit. The second gives two actions that fit the visitor’s situation. If nine people really are coming, choosing a larger room lets them keep the correct count. An error summary that links to the field can help the visitor find the problem. GOV.UK Design System guidance on error messages.

Match the status to what the service has done

Use Draft saved after the details have been stored for later. The visitor still has to send the request. Use Sending booking request while the service is submitting it. Once the center receives it, Booking request sent confirms submission while staff review is pending. When staff reserve the room, Booking confirmed signals that the visitor can make plans and tells them where to check in. Verify the trigger and the next step for every message. GOV.UK Design System guidance on confirmation pages.

Ask people to predict and recover

Give likely visitors a room-booking task in a prototype. Before they choose a button, ask what they expect it to do. Give them a scenario with nine attendees and observe whether they can explain the error and find a room that fits. After they send a request, ask whether they think the room is reserved and what they expect to happen next. Include people who use assistive technology and test whether they can find the labels, instructions, and feedback. GOV.UK Service Manual on moderated usability testing.

If visitors think the room is already reserved after submission, test a clearer status such as Booking request awaiting staff review. Repeat the task and check whether they can now explain what happened and who acts next.

Try six room-booking edits

Write each revision using the facts given.

1. A field collects the total attendance. Change Details to a descriptive noun phrase.
2. A button opens a screen where the visitor can check the request before sending it. Rewrite Continue.
3. The room fits up to eight people, including the visitor. Rewrite the field hint Input the total count in numeric format. The field accepts whole numbers only.
4. The visitor enters nine. A larger room is available. Rewrite Invalid entry. so the visitor knows the cause and can recover.
5. The service has saved the form as a draft. The visitor still needs to review and send it. Rewrite Booking complete.
6. Staff have confirmed the small meeting room for May 14 from 2 to 3 p.m. Visitors check in at the front desk. Replace Done! with a status and instructions.

Show answers and explanations

1. Number of people. The noun phrase identifies what to enter, even when the field is read on its own.
2. Review booking request. The imperative names the next action, and the object identifies what the visitor will see.
3. Enter a whole number from 1 to 8. Include yourself. The two imperatives cover the format, range, and counting rule.
4. The small meeting room holds up to 8 people. Enter a whole number from 1 to 8 or choose a larger room. A statement explains the limit, and an instruction gives the visitor two ways to continue.
5. Draft saved. Open your draft to review and send your booking request. The status names what was saved. The instruction names the work that remains.
6. Booking confirmed. The small meeting room is reserved for you on May 14 from 2 to 3 p.m. Check in at the front desk when you arrive. The status confirms the booking, and the sentences give the details and the next action.

Related writing guides

• Use the same direct wording when answering support questions. How to Write Effective FAQs.
• Choose words that describe people and roles accurately. Inclusive Language in Professional and Academic Writing.
• Practice trimming wordy phrases while preserving meaning. The Power of Concise Writing.