UX writing: why button labels and error messages sell
The small words in an interface decide whether people finish a form, find their way or give up. What UX writing is, with examples for buttons, forms, error messages and empty states.
Request an AI summary
A website can look great and still lose people at the last step: a button that doesn’t say what happens next, a form field nobody understands, an error message that sounds like a machine. The words in an interface are small, but they sit exactly where people decide whether to continue.
UX writing is the craft of those words: labels, buttons, hints, messages, everything a person reads while using a site or app.
1. UX writing: what it is
Marketing copy wants to convince. UX writing wants to help someone get something done. It answers the questions a person has at each step: where am I, what can I do here, what happens if I click, and what went wrong?
Good interface text is:
- Clear: one meaning, plain words, no internal jargon.
- Short: as long as needed, no longer. People scan; they don’t read.
- Useful: it tells people what to do, not just what’s wrong.
- Consistent: the same thing has the same name everywhere.
2. Buttons: say what happens
A button label is a promise. The clearer the promise, the more people click.
- “Submit” → “Send message”
- “OK” → “Delete project” (when that’s what the OK does)
- “Continue” → “Continue to payment”
- “Click here” → “Download the price list (PDF)”
The pattern: a verb plus what it acts on. It helps everyone, and especially screen reader users, who often jump from button to button without the text around them.
3. Forms: fewer questions, clearer fields
Forms are where most visitors drop out. Words help keep them:
- Labels stay visible. A placeholder inside the field disappears as soon as someone types, and with it the question.
- Say why you ask. “Phone (so we can reach you about the delivery)” gets more answers than “Phone*”.
- Mark the exception, not the rule. If most fields are required, mark the optional ones.
- Show the format before the mistake. “Date of birth (DD.MM.YYYY)” instead of an error after the fact.
4. Errors: explain and help
An error message has two jobs: say what went wrong and how to fix it. In the user’s language, not the system’s.
- “Error 0x4F” → “We couldn’t send your message. Please check your connection and try again.”
- “Invalid input” → “Please enter an email address, like name@example.com.”
- “Password does not meet requirements” → “Your password needs at least 12 characters.”
The tone matters too: no blame (“You entered an invalid value”), no exclamation marks, no jokes when someone’s order just failed.
5. Empty states and confirmations
Some of the most useful text appears when there’s nothing to show, or right after something happened:
- Empty states: an empty cart, an empty search result, a new account with no projects. “No results” leaves people stuck; “No results for ‘oak table’. Try a shorter term or browse all tables” moves them on.
- Confirmations: after a form, say what happens next. “Thanks, your message is on its way. You’ll get a copy by email.” A blank page with “Success” leaves people wondering.
6. Voice: one way of speaking
A brand has a voice in its marketing and should have the same voice in its interface. A bank speaks differently from a skate shop. A short guide with a few rules keeps it consistent across pages and people: formal or informal address, how errors are phrased, which terms are used for what, words to avoid.
For multilingual sites, the guide covers each language. German text often runs a third longer than English, so layouts need room for that, and a direct translation of a button label rarely sounds as natural as one written for the language.
7. Testing: words are design too
Interface text can be tested like any other part of a design: watch a few people use a form, compare two button labels, look at where visitors drop out. Small wording changes on high-traffic steps, such as the checkout or the contact form, can make a measurable difference.
The short version
- UX writing is the text people read while using a site: labels, buttons, hints, messages.
- Buttons say what happens: verb plus object.
- Forms keep labels visible, explain why they ask and show formats up front.
- Errors explain what went wrong and how to fix it, without blame.
- Empty states and confirmations tell people what to do next.
- Voice stays consistent, in every language.
If your website or app should speak more clearly, get in touch.