UX Writing: How Microcopy Improves Digital Product Experiences

UX writing is the practice of designing the words in an interface, the microcopy on buttons, labels, forms, errors, empty states and confirmations, so people understand what they can do, what's happening and what to do next. Good microcopy is clear, specific, concise and consistent, uses the user's vocabulary, and appears exactly where a decision or problem occurs. It reduces errors and support requests, makes products easier to learn and is essential for accessibility. Write it alongside the design, test it with users and keep it in the design system.

UX writing covers every word users read while using a product: navigation labels, buttons, field labels, hints, error and success messages, notifications and onboarding. The shortest of these are usually called microcopy.

It differs from marketing copywriting in purpose. Marketing copy aims to attract attention and persuade; interface copy aims to help someone finish a task without thinking about the words. The best microcopy is rarely noticed. Content design is a broader discipline that decides what content users need and in what form; UX writing is usually part of it.

Start with a verb and say what happens. Users should be able to predict the result of a click from the label alone, and screen reader users often navigate by button names without surrounding context.

Navigation labels should match the words users would use, not internal team names or brand concepts. Put the distinguishing word first so labels scan quickly, avoid clever or ambiguous terms, and keep labels consistent with page titles. Test them with card sorting or tree testing as part of information architecture work; label changes are among the cheapest findability fixes available.

Every field needs a visible label that stays visible while typing. Placeholder text disappears as soon as users start, so it shouldn't carry labels or instructions. Put format hints (“DD/MM/YYYY”, “As shown on your card”) near the field, mark optional fields rather than scattering asterisks, and briefly explain why you need sensitive information such as a phone number.

Good form copy prevents errors instead of reporting them afterwards, which is exactly what the error prevention heuristic asks for.

Nielsen Norman Group's error-message guidelines come down to three things: make the error visible next to where it happened, explain the problem in plain language without blame, and help users fix it efficiently, including by keeping what they already entered.

Empty screens appear when there's nothing to show yet, after a search or filter returns nothing, or after a user clears everything. Nielsen Norman Group's empty state guidelines recommend using them to communicate system status, help users learn the product and offer a direct path to the next task. An empty dashboard should say what will appear there and offer the one action that gets it started, not just show a blank area.

Success messages confirm what happened and, where relevant, what happens next: “Order placed. We've sent a confirmation to anna@example.com.” Keep them short and put them where users are looking.

Confirmation dialogs for destructive actions should name the action and the object: “Delete ‘Q3 report’? This can't be undone.” with buttons labelled “Delete report” and “Keep report”. Generic “Are you sure?” dialogs with “OK” and “Cancel” train users to click without reading. Where possible, offer undo instead of asking for confirmation.

Onboarding copy should get users to their first success quickly, not explain every feature. Tell users what they'll achieve, keep steps short, let them skip, and teach features in context when they're needed. The guide to mobile app onboarding covers the structure; microcopy is what makes each step feel short.

Checkout copy answers the questions that make buyers hesitate: what the total will be, when it will arrive, what happens if it doesn't fit, and whether payment is secure. Show delivery dates, not just delivery speeds; explain what a promo code field is for so it doesn't send users off to search for codes; label the final button with the action and amount where possible, such as “Pay £48.00”. See the checkout UX guide for the wider design.

A search placeholder can hint at what's searchable (“Search products, brands or order numbers”). No-results messages should confirm what was searched, suggest corrections or broader terms and offer ways to continue, such as popular categories. “No results” on its own is a dead end. See ecommerce search UX.

Many WCAG 2.2 success criteria depend on words. Forms need labels or instructions (3.3.2) and errors must be identified in text (3.3.1), with suggestions for fixing them where known (3.3.3). The purpose of each link should be clear from its text or context (2.4.4), so avoid “click here”. Status messages such as “Item added to cart” should be announced to assistive technology without moving focus (4.1.3). Images that convey information need text alternatives (1.1.1).

Plain language helps everyone: people using screen readers, people with cognitive disabilities, people reading in a second language and anyone in a hurry. See accessibility in UI/UX design.

Voice is the product's consistent personality; tone adapts to the situation. A playful voice can work in a celebration message and grate in an error message about a failed payment.

Write so copy can be translated. Many languages need more space than English, so design components that allow text to grow rather than truncating it. Avoid idioms and wordplay, don't build sentences by joining fragments in code (word order differs between languages), handle plurals properly, and format dates, numbers, currencies and addresses for each locale. Keep a glossary so key terms translate consistently.

Treat copy like other design decisions. Keep a short content style guide covering voice, tone, capitalization and terminology; define standard messages for common states in your design system; write real copy in designs instead of placeholder text; and give developers final strings with the design so words aren't invented during build.

Microcopy is design. Clear buttons, visible labels, helpful errors, purposeful empty states and honest confirmations make products easier to use and more accessible. Write words alongside layouts, keep them consistent through a design system and test them with users. For the visual side of interface clarity, see UI design principles and microinteractions.