5 exercises — Practice the vocabulary UX writers and product designers use every day: microcopy, empty states, CTAs, onboarding flows, destructive actions, and more.
User flows: onboarding flow, progressive disclosure, confirmation dialogue, destructive action
Constraints: character limit, truncation, localisation, tone of voice
0 / 10 completed
1 / 10
A UX writer is reviewing the design for a new dashboard. When a user logs in for the very first time, there is no data to display yet. The designer has left placeholder text that reads "No data found."
The UX writer flags this and says: "This is a missed opportunity — we should write a proper empty state here."
Which of the following best describes what an empty state is and why it matters?
Empty state (also called zero state for a first-time user): the screen or component a user sees when there is no content to display — typically on first use, after clearing data, or when a search returns nothing. A good empty state has three parts: explain what is missing and why ("You haven't added any projects yet"), motivate ("Your projects will appear here"), and act — a clear CTA to help the user get started ("Create your first project →"). "No data found" is considered poor UX writing because it is cold, technical, and gives the user no path forward. Empty states are one of the highest-value microcopy opportunities because they appear at critical moments in the onboarding flow.
2 / 10
Fill in the blank with the most appropriate term.
"After the user saves their settings, a small pop-up appears at the bottom of the screen for three seconds, confirming: 'Settings saved.' This UI pattern is called a ________."
Which term correctly completes the sentence?
A toast notification (sometimes called a snackbar in Material Design) is a brief, non-blocking message that appears temporarily — usually at the bottom or top of the screen — to confirm that an action was completed. It disappears automatically after a few seconds and does not require user input. Examples: "Settings saved", "File deleted", "Link copied to clipboard." The copy should be concise (ideally under 60 characters) and use past tense to confirm what happened. A tooltip is different — it appears on hover to explain a UI element. A confirmation dialogue is a modal that asks the user to confirm or cancel before an action is taken — it requires interaction and is typically used for destructive actions.
3 / 10
Match the definition to the correct term.
"A UX design pattern that reveals information gradually — showing only what the user needs at each step, rather than presenting all options and settings at once — in order to reduce cognitive overload."
Which term does this definition describe?
Progressive disclosure is a UX writing and interaction design principle: present users only the information or options relevant to their current task, and reveal more detail as they need it. Examples: advanced settings hidden behind "Show more options", a long form split into steps, or a tooltip that only appears when a user hovers over a complex term. It reduces cognitive load and prevents beginners from being overwhelmed. As a UX writer, you apply progressive disclosure to help text — writing the minimum useful copy upfront and providing links to deeper explanations ("Learn more"). It also directly informs onboarding flow design: new users see a simplified version of the product first.
4 / 10
A product team is designing a "Delete account" feature. The engineer suggests: "We'll just make it a standard button — the user can always contact support to recover it."
The UX writer disagrees: "This is a destructive action — we need a confirmation dialogue with very specific button labels."
Which approach to the button labels in a confirmation dialogue for a destructive action follows UX writing best practice?
A destructive action is any action that permanently deletes or significantly alters data in a way that cannot easily be undone — deleting an account, permanently removing files, cancelling a subscription. UX writing best practice for destructive actions: (1) Always use a confirmation dialogue — a modal that forces the user to actively confirm before proceeding. (2) Write button labels that describe the outcome, not generic words. "Delete my account" is unambiguous; "OK" requires the user to remember what they are confirming. (3) Make the destructive button visually distinct (typically red) and place it so it is harder to click accidentally. (4) Consider adding a character limit-style friction device — asking the user to type "DELETE" to confirm. "Yes/No" and "OK/Cancel" are considered anti-patterns for high-stakes dialogues because they force cognitive recall rather than recognition.
5 / 10
A senior UX writer explains a concept during a team workshop:
"Good microcopy is the difference between a user completing a task and abandoning it in frustration. It includes every small piece of text in the interface — button labels, error messages, placeholder text, tooltips — anything that isn't the main body copy. The goal is to guide, reassure, and reduce friction at exactly the right moment."
A junior team member asks: "So microcopy is the same as UX writing?"
Which answer best distinguishes the two terms?
Microcopy: the small pieces of functional text embedded in a UI — button labels, error messages, placeholder text, form helper text, tooltips, toast notifications, empty states. It is called "micro" because each instance is short (often under 10 words), but collectively it has a large impact on usability and conversion. UX writing (also called UI writing or product writing): the professional discipline responsible for all words inside a product — including microcopy, onboarding flows, in-app tutorials, push notifications, transactional emails, and broader content strategy. A UX writer thinks about the user's entire journey through language, not just individual labels. In practice, the terms are often used loosely, but the cleaner distinction is: microcopy is a deliverable (a type of text); UX writing is a discipline (a practice and job role). Both differ from copy in the traditional marketing sense, which refers to persuasive text used in advertising and promotion.
6 / 10
Alex (Senior Frontend Developer) comments on a PR draft:
"This button says 'Submit'. It's…vague. Users need to know *what* they're submitting. Could we add something like 'Submit Changes' or 'Save Draft'?"
Alex correctly identifies that 'Submit' lacks context. Microcopy isn't just about technical accuracy; it needs to guide the user's action. Using clear verbs like 'Save Draft' or 'Submit Changes' dramatically improves understandability and reduces potential friction.
7 / 10
Sarah (UX Writer) drafts a Slack message to the design team:
"Okay, let's refine the error message for failed API requests. Currently it says: 'Request Failed'. That's… too technical. We need something more user-friendly that explains *why* the request failed and what they can do next."
Sarah is right to push for a user-centric approach. The original message 'Request Failed' isn't helpful because it doesn't explain *why* the request failed. A good error message should guide the user toward resolving the issue – something like 'Unable to connect to the server, please try again later.'.
8 / 10
Ben (Product Manager) is reviewing the copy for a new onboarding flow:
"We want to encourage users to connect their social media accounts. The current text says: 'Connect Social'. Is that effective?"
Ben correctly identifies that 'Connect Social' is bland and doesn't motivate users. Effective microcopy goes beyond simply stating an action; it highlights the value proposition – in this case, perhaps 'Unlock exclusive content' or 'Easily share your progress'. The phrasing should persuade the user to take the desired action.
9 / 10
Chloe (UX Writer) is writing a PR description for a new feature:
"'This update improves the user experience by streamlining the process of creating a new account.' Is this a good PR description?"
Chloe is correct in that this description effectively communicates the benefit. Good PR copy should clearly articulate *why* the change was made and how it improves the user experience – framing it from a business perspective helps stakeholders understand its value.
10 / 10
David (Lead UX Designer) is discussing design principles with his team:
"We need to ensure all labels and instructions are written in plain language. What does 'plain language' primarily refer to?"
'Plain language' focuses on readability and understandability. It's about stripping away jargon and complex phrasing to ensure everyone – regardless of their technical background – can easily grasp the meaning. This is crucial for effective microcopy.
What does the "UX Writing & Microcopy Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to ux writing & microcopy vocabulary through 10 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.