In short
Microcopy is the short text that guides an action: buttons, labels, hints, error messages, empty screens and confirmations. Write it from the visitor’s side: what are they thinking now, what do they need to know, and what is the shortest honest answer? A button says what happens, an error message says how to fix it. WCAG 2.2 asks for labels or instructions and errors described in text.
Same form, different words
The same field and the same button, twice. Feel the difference.
Invalid input.
You will hear from us within two working days.
In the demo above, the same field with the same button appears twice. The first version asks for “Email*”, reports “Invalid input.” and ends with “SUBMIT”. The second asks for “Your email address”, says what it is for (“for our reply, nothing else”), tells you when you will hear back and ends with “Request your quote”. The field is the same, and so is the technology. Only the words differ. Eight more mistakes of this kind, from long forms to poor contrast, are in UX mistakes that cost customers.
Those words are called microcopy. Below you will read where they appear, how to write them, what WCAG 2.2 asks of them and how to test them. What we say about our own sites is on their case pages.
What is microcopy?
Microcopy is every short text that helps someone do something on your site or in your app. It is rarely more than a few words, and it sits where a visitor makes a choice: do I click, do I fill this in, do I carry on?
The difference with ordinary web copy is the purpose. Copy on a service page explains and persuades: why you, what the customer gets, what the next step is. Microcopy guides the action itself. It no longer has to persuade; it removes the last doubt. Same craft, different scale. You can read more about longer texts in our article on web copy.
Because the texts are so small, they are easily forgotten. Then the system’s default text is left in place, such as Submit or Invalid input. The good news: a better button text needs no new design, only attention.
Where does microcopy appear?
Wherever a visitor has to do something or hesitates for a moment. Each place answers a question of its own:
- Buttons and links: what happens when I click, and am I committing to something?
- Labels: what should I enter here?
- Hints and examples: in what format, and why are you asking?
- Error messages: what went wrong, and what do I do now?
- Empty screens: why do I see nothing, and how do I start?
- Confirmations: did it work, and what happens now?
- Status labels: what does this little word next to a product, a shop or an order mean? On snelrepareren.nl shops carry the label Verified or Not verified.
Which three questions do you ask for every sentence?
One: what is the visitor thinking at this moment? Two: what do they need to know to carry on? Three: what is the shortest honest answer to that? You need no more method than this.
Take the error message from the demo. “Invalid input” describes the system: it rejected something. Whoever reads it still does not know what to do. “That email address is missing an @” describes the solution. Same error, different outcome.
The same three questions also rewrite your buttons. Submit says what the system does; Request your quote says what the visitor gets. Write for the side that has to click.
Do not write what the system did. Write what the user needs to do now.
How do you write a button?
A button is a promise: if you press this, this happens. The more precise the promise, the less someone has to guess.
- Start with a verb and say what happens. Request your quote, Register, See the price. The UK government’s design system puts it like this: describe the action the button performs.
- Use sentence case, not capitals. The same design system recommends button text with only a capital at the start. SUBMIT in the demo falls outside that.
- Use the same word everywhere. If the menu says Register, let the button and the page heading also be about registering.
- In a form with steps, say where you are. A Next button is fine between the steps; the last button says what really happens then, such as Send request.
- Do not disable a button without explanation. A grey button that does nothing leaves the visitor guessing what is missing. The UK government advises against disabled buttons: they have poor contrast and confuse some people. Let the button work and say after the click what is missing.
How do you write a label?
A label says what belongs in a field. It sits next to the field, stays in place while you type, and uses the visitor’s words, not your database’s. “Your email address” reads like a question from a person; “Email*” like a column in a table.
- Every field its own label, including every choice in a row of radio buttons or checkboxes. Whoever ticks a box must know what for.
- An example in the field is not a label. The W3C writes that such example text (a placeholder) disappears as soon as you start typing, often has less contrast and is not read as a label by screen readers. Put the label above it.
- Say in words what is required, or what is not. An asterisk alone only works if people know what it means. If almost all fields are needed, add (optional) after the few that are not. Our own request form does that, for example with Description (optional).
- Split what you need separately. First name and last name in two fields each get a label of their own.
How do you write a hint?
A hint sits with a field and answers the question the label leaves open. Usually it is one of these three:
- Why are you asking this? Whoever hands over their details wants to know what happens to them. In the demo the email address says: for our reply, nothing else.
- In what format? A date, a phone number, a postcode or a file with a maximum size. The W3C names this explicitly: say what format you expect, especially if it differs from what people are used to.
- What happens next? “You will hear from us within two working days” removes the question of whether anything will happen with your request.
A hint can also prevent an error instead of fixing it. On ArtsenPool, a platform for doctors and hospitals that has not launched yet, every form warns: do not enter medical or patient data. In an emergency: 112.
Do keep it short. With the requirement for labels and instructions, the W3C writes that too much information or instruction can be just as harmful as too little. Only answer the question the visitor really has here.
How do you write an error message?
A good error message does three things: it points to the field, says what is wrong and says how to fix it. In ordinary words, without blaming the visitor.
NL Design System, the Dutch public-sector collection of design systems to which municipalities and national agencies such as RVO and Logius contribute, gives exactly this example. Not “Invalid input” or “This field is required”, but “Enter a valid email address, for example name@example.nl.” Or: “Enter the house number so we can send your order.” The design system also says: never blame the user, and end with a full stop, so a screen reader pauses.
The UK government goes a step further in its design system. It advises against writing valid or invalid, because those words add nothing, and also against sorry, please and informal words such as oops. Use the words of the label in the message, and read it aloud: does it sound like something you would say yourself?
When do you show the error?
Not while someone is still typing. Both the British and the Dutch design systems advise against it. NL Design System calls a message that appears after the first letter irritating and confusing; the British guidance points to people who type more slowly. After that they differ: the British system only checks when you continue or submit, the Dutch one also when you leave a field you have changed. Choose one and test it with real people.
After an error, keep what was entered, the British guidance writes: anyone who gets an empty form back has to do everything again. And if there are several errors on one page, put a summary at the top, next to the message at the field itself. Both design systems advise this.
Red alone is not an error message. Someone who has trouble telling colours apart does not see a red border. Put the message in words, with colour as an extra.
What goes on an empty screen and in a confirmation?
An empty screen is a search without results or an overview without items. “No results” is true, but leaves the visitor stranded. Say why it is empty and what they can do now. For example: “No results for ‘crown’. Try another word or see all treatments.”
A confirmation says three things: it worked, what happens now and when. After sending, our own request form says: Request sent. Your request has reached us. You will usually hear back within two working days.
In a form with steps: do not ask again for what the visitor already entered. Whoever gave their address in step one does not want to type it again in step three. Since WCAG 2.2 that is also a requirement.
What does the difference look like, per kind of text?
Everything above in one place. On the left what you often see, on the right a version that answers the visitor’s question. These are examples, not fixed texts: write them in your own words and for your own form.
| Kind of text | Before | After | What is better |
|---|---|---|---|
| Button | SUBMIT | Request your quote | Says what the visitor gets |
| Label | Email* | Your email address | In the visitor’s words, with no code to decipher |
| Hint | (nothing) | For our reply, nothing else. | Says why you are asking |
| Optional field | Comments | Comments (optional) | Says in words that it is allowed |
| Error: empty field | This field is required. | Enter your email address. | Names the field and says what to do |
| Error: wrong format | Invalid input. | Enter an email address like name@example.com. | Says how to get it right |
| Empty screen | No results. | No results for ‘crown’. Try another word or see all treatments. | Gives a next step |
| Confirmation | Sent. | Request sent. You will hear from us within two working days. | Says it worked and what happens now |
What does WCAG 2.2 ask of your microcopy?
WCAG is the international guideline for accessible websites, from the W3C. Version 2.2 is a W3C Recommendation; the current text is from 12 December 2024. Part of the requirements is literally about words on buttons and in forms. These are the main ones, with their level (A is the first level, AA the second):
| Requirement | Level | What it asks | What it means for your text |
|---|---|---|---|
| 3.3.2 Labels or Instructions | A | Labels or instructions when someone has to enter something | Every field and every choice a label; say what format you expect |
| 3.3.1 Error Identification | A | An error that is detected automatically identifies the field and describes the error in text | Colour or an icon alone is not enough |
| 3.3.3 Error Suggestion | AA | If it is known how to fix the error, the visitor gets that suggestion | Say how to get it right, not just that it is wrong |
| 2.4.6 Headings and Labels | AA | Headings and labels describe topic or purpose | No vague labels such as Details or Other |
| 2.5.3 Label in Name | A | The visible text of a button or field is also in its name in the code | What you read on the button, you can also say with voice control |
| 4.1.3 Status Messages | AA | Status messages are announced without the focus moving | A confirmation or error count must also reach a screen reader |
| 3.3.7 Redundant Entry | A | What someone already entered in the same process, they do not have to type again | New in WCAG 2.2; fill it in yourself or let them choose it |
| 1.4.1 Use of Color | A | Colour is not the only way to convey information | A red border alone is not an error message |
Two things stand out when you read the W3C’s explanation. First, the bar for an error message is lower than you think: according to the explanation of 3.3.1, “Email is not valid” is already enough to identify the error. How to fix it falls under 3.3.3. A good message does both. Second, with 2.5.3 the W3C advises starting the name in the code with the text on the button, so that someone using voice control can press it with exactly those words.
Whether your organisation is legally required to meet these requirements, you can read in our article on the European Accessibility Act. How to make a site accessible is under web accessibility.
Which tone suits microcopy?
The same tone as the rest of your site, but calmer. A few rules of thumb:
- Choose a register and stick to it. A site that is casual on the homepage and formal in the error message sounds like two different counters.
- Be direct, and do not joke about an error. A wink on a page that does not exist can work. When a payment fails or a registration does not go through, someone only wants to know what to do.
- One word for one thing. Decide which words you use: request or quote request, register or sign up. A design system records what a button looks like; record in it what it is called as well.
Good microcopy cannot save a busy screen. Fewer fields, one question per step and no duplicate messages give the words room. And say honestly why you ask for something: honesty reads as calm.
The final test is simple: read your form aloud. Does it sound like a person at a counter, or like a system message from 2009? You hear it straight away.
How do you test whether your microcopy works?
You do not need a lab for it:
- Read everything aloud, from the first button to the confirmation.
- Fill the form in wrongly. Leave a required field empty, type an email address without an @, choose a date in the past. Is every error in words at the right field, and does your input stay in place?
- Do it on a phone, with one hand. Do you see the error message without scrolling?
- Do it with only the keyboard and a screen reader, such as VoiceOver on an iPhone or Mac or NVDA on Windows. Do you hear the label for each field, the error message and the confirmation?
- Give it to someone who does not know your site, with a real task: register, request a quote. Watch and say nothing.
- Look at your statistics per step, if you have them: where do people drop off? Change one thing at a time.
In a UX audit we go through the routes from landing to request, including forms and texts. In UI/UX design every button and every field gets its states, including what appears when something goes wrong.
When this does not apply
Microcopy does not fix a form that asks too much. If you ask for twelve fields where four are enough, first remove fields; better labels do not make a long form short. And if your offer or your price is unclear, no button text will fix that. Then start with conversion optimisation.
With legal texts, such as consent for newsletters, terms and conditions or a privacy statement, precision counts for more than brevity. A shorter sentence can mean something else there. Have such texts checked by someone who knows the rules.
What we do not know: we have not measured how many extra requests better microcopy brought on our own sites or those of clients, so we give no number. The British guidelines are written for English-language government services, and the guidelines of NL Design System are, according to the site itself, still in beta. And WCAG is a minimum: meeting every requirement does not tell you whether people understand the text. You only know that once you let them try.
Frequently asked questions
What is microcopy?
Microcopy is the short text that guides an action: buttons, labels, hints, error messages, empty screens and confirmations. It answers the question a visitor has at that moment, such as what happens when they click.
Is microcopy not just copywriting?
Same craft, different scale. Web copy explains and persuades; microcopy guides the action itself, at the moment someone fills something in or makes a choice. You write both from the reader’s side.
What do you put on a submit button?
What the visitor gets or what happens, with a verb at the start, such as Request your quote or Register. A general word like Submit only says what the system does.
How do you write a good error message?
Point to the field, say what is wrong and how to fix it, in ordinary words and without blaming the visitor. For example: enter an email address like name@example.com. Keep what was already entered.
Can I improve my microcopy myself?
Yes. Go through your forms with three questions: what is the visitor thinking now, what do they need to know, and what is the shortest honest answer? Read everything aloud and fill in the form wrongly yourself. For a thorough look at your forms and routes there is the UX audit.
Wondering where your form causes friction? Send us the link to your form or request page, and we will take a look. More about how we design screens and forms is under UI/UX design, and what a thorough review delivers under UX audit. You work directly with Nawid, with a fixed team of five specialists.
Also worth reading: Everyone has the same AI website. Do you still stand out?
Written with the help of AI, reviewed and edited by Nawid Rasa, who is responsible for the content. Sources are listed below the article. Spotted an error? Email hi@empireyo.com.
Where do your visitors drop off?
Send the link to your form or request page. We point out the three lines you can improve this week.
Sources
Consulted on 3 November 2026.
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation (12 December 2024)
- W3C, Understanding WCAG 2.2: Labels or Instructions (3.3.2)
- W3C, Understanding WCAG 2.2: Error Identification (3.3.1)
- W3C, Understanding WCAG 2.2: Error Suggestion (3.3.3)
- W3C, Understanding WCAG 2.2: Headings and Labels (2.4.6)
- W3C, Understanding WCAG 2.2: Label in Name (2.5.3)
- W3C, Understanding WCAG 2.2: Status Messages (4.1.3)
- W3C, Understanding WCAG 2.2: Redundant Entry (3.3.7)
- W3C WAI, Forms Tutorial: Form Instructions (updated 13 May 2024)
- NL Design System, Foutmeldingen (guidelines in beta, in Dutch)
- NL Design System, Schrijf een duidelijke foutmelding (in Dutch)
- NL Design System, Controleer op het juiste moment op fouten (in Dutch)
- GOV.UK Design System, Error message
- GOV.UK Design System, Button
- GOV.UK Design System, Validation (pattern)
- Empireyo, Tandartsenpraktijk Alexander case
- Empireyo, Atiq Tandartsen case
- Empireyo, Taxi Grou case
- Empireyo, ArtsenPool case
- Empireyo, snelrepareren.nl case