UX Writing English

Microcopy refers to the small pieces of text in a user interface — button labels, error messages, placeholder text, tooltips, confirmation dialogs, and empty states. Despite being short, microcopy has a disproportionate impact on usability and conversion. Clear, action-oriented microcopy reduces user anxiety, prevents errors, and guides users through critical flows. The vocabulary of UX writing includes terms like affordance, friction, progressive disclosure, and copy hierarchy.

Effective error messages follow three principles: explain what went wrong (without blaming the user), say why it happened (if useful), and tell the user what to do next. Good error messages are specific ("Your password must be at least 8 characters") rather than generic ("Something went wrong"). They avoid technical jargon, use plain English, and maintain the product's tone of voice. The structure is often: problem + cause + resolution.

Onboarding copy guides new users from sign-up through their first meaningful action (the "aha moment"). Effective onboarding copy is brief, benefit-focused, and progressive — it reveals information as it becomes relevant rather than overwhelming users upfront. Key components include welcome messages, empty state prompts, tooltip walkthroughs, and success confirmations. The goal is activation: getting users to complete the action that makes them likely to return.

A call-to-action (CTA) is the strategic prompt that drives a user toward a desired action — it may span a button, a link, and surrounding copy. A button label is the specific text on the interactive element itself. Effective button labels use the verb-noun formula ("Download report", "Start free trial") so users know exactly what will happen when they click. Labels like "Submit" or "OK" are considered weak because they describe the mechanism rather than the outcome.

Common UI text conventions include: sentence case for most UI elements (e.g. "Saved successfully" not "Saved Successfully"), title case only for proper product names and page titles, avoiding full stops in labels and tooltips, using second-person ("your account") not third-person, writing in active voice, and keeping labels consistent across the product (never mixing "Delete" and "Remove" for the same action). Accessibility conventions include writing meaningful link text instead of "click here".

Accessibility writing ensures that UI copy is understandable and usable by people with disabilities, including those using screen readers, those with cognitive disabilities, and non-native speakers. Key practices include: writing descriptive alt text for images, ensuring link text is meaningful out of context, avoiding directional language ("click the button on the left"), using plain language (aim for reading level Grade 8 or below for consumer products), and writing descriptive form labels rather than relying solely on placeholder text.

Progressive disclosure is a design principle where information is revealed gradually, only when the user needs it. In UX writing it means providing brief primary copy with optional expandable detail ("Learn more", "See advanced options"). This reduces cognitive load for most users while still making information available for those who need it. It is commonly applied in tooltips, accordions, inline help, and onboarding flows.

In a microcopy review UX writers evaluate proposed copy against brand voice, clarity, consistency, and accessibility standards. Common review language includes: "This label is ambiguous — the user doesn't know what will happen", "This error message is too technical", "The CTA doesn't reflect the value exchange", and "These two labels are inconsistent across screens". UX writers also collaborate in content audits, where existing copy is systematically evaluated and scored for quality.

An empty state is the view a user sees when there is no data to display — an empty inbox, a new dashboard with no widgets, or a search with no results. Good empty state copy does not just say "No results found." Instead it explains why the state exists, provides a clear next action ("Add your first contact"), and if appropriate, offers encouragement. Empty states are often conversion opportunities and should be treated as onboarding moments.

Voice is the consistent personality of a product's communication — it does not change. A product might have a voice that is "direct, human, and encouraging." Tone is how that voice adapts to context — the tone in an error message is more serious and empathetic than the tone in a celebratory success state. UX writers document voice and tone in a content style guide and use it as a reference when writing and reviewing copy across different parts of a product.