5 exercises — Practice writing concise, useful tooltips and inline help text for settings fields, icon buttons, technical inputs, and timestamp labels.
0 / 10 completed
1 / 10
A tooltip appears when a user hovers over a "Two-factor authentication" toggle in account settings. Which tooltip is best?
Tooltips should add value beyond the label — explain the why or the benefit, not just restate the label.
Tooltip writing guidelines:
• Maximum ~15 words — tooltips are scanned, not read
• Explain benefit/outcome ("why do this"), not just definition
• Don't repeat the label word-for-word — that's redundant
• Avoid dry technical definitions — speak to user goals
Option A — dictionary definition; too long; creates more questions than it answers
Option B — restates the obvious ("toggle this switch to enable/disable"); no added value
Option C ✓ — explains what it does ("second verification step") and why ("recommended")
Option D — too short; gives no information
Key vocabulary:
• Tooltip — a small contextual popup that appears on hover over a UI element
• Benefit copy — text that explains why a feature matters, not just what it is
• Label redundancy — tooltip text that just repeats the element's label (an anti-pattern)
• Contextual help — inline or overlay help that appears in context of the relevant UI element
2 / 10
A form field asks for "API Key." The help text appears below the field. Which is best?
Help text for technical fields should answer: where to find it, what it looks like, and a key gotcha.
The three jobs of API key help text:
1. Where — "Found in Settings → API → Your keys" (navigation path)
2. What it looks like — "Starts with sk-" (reduces wrong-paste errors)
3. Critical warning — "Keep it private" (security nudge at the moment of use)
Option A — states the obvious; adds no new information
Option B — technical definition the user doesn't need; doesn't help them find it
Option C — better, but missing the security warning
Option D ✓ — all three jobs covered in one short line
Key vocabulary:
• Help text — persistent text below or beside a form field (visible without hover)
• Navigation path — step-by-step direction using UI labels (Settings → API → Keys)
• Contextual security nudge — brief inline warning about sensitive actions or data
• Hint text — placeholder or label that shows the expected format inside the field
3 / 10
A "Webhook URL" field in an integration settings panel needs help text. The user should enter a URL that will receive POST requests. Which is best?
Technical field help text should answer: what goes here, what technical requirements does it have, and show an example.
Three parts of excellent technical help text:
1. Plain-language description — "where we'll send event notifications"
2. Technical requirement — "must accept POST requests" (prevents a common misconfiguration)
3. Example — a plausible example reduces copy-paste errors and clarifies format
Option A — textbook definition; doesn't actually help the user fill in the field
Option B — too short; doesn't explain requirements
Option C ✓ — all three parts present
Option D — label annotation, not help text
Key vocabulary:
• Technical requirement — constraints the input must meet (e.g., "must accept POST")
• Example value — a representative value that shows the expected format
• Misconfiguration prevention — help text written to prevent the most common user errors
• Field-level documentation — contextual technical explanation at the point of configuration
4 / 10
An icon button in a dashboard shows a downward-arrow icon. A screen reader needs an accessible label, and sighted users should get a tooltip on hover. Which text is best for both the aria-label and tooltip?
Icon button labels and tooltips should be concise action phrases — not descriptions of the icon, not verbose sentences.
Good icon label formula: [Action verb] + [specific object]
• "Download as CSV" — verb (Download) + specific format (CSV)
• Short enough for a tooltip
• Descriptive enough for a screen reader announcement
Option A ("Down") — describes icon direction, not the action
Option B ("Arrow") — describes the icon itself, completely unhelpful
Option C — too verbose for a tooltip; screen readers should be concise too
Option D ✓ — perfect: action + specific outcome
Key vocabulary:
• aria-label — accessible name for UI elements without visible text labels
• Icon button — a button with only an icon (no visible label text)
• Action phrase — a label that describes what the button does, not what it looks like
• Accessible name — the label announced by screen readers for interactive elements
5 / 10
A "Last modified" column in a file list shows a relative timestamp (e.g., "3 days ago"). A user hovers and should see the full timestamp. Which tooltip content is best?
Tooltips over relative timestamps should provide the exact absolute value — that's their sole job.
The relative display ("3 days ago") is optimized for quick reading. The tooltip exists specifically to provide:
• Full date AND time
• Timezone (UTC or local — whichever is more useful for the audience)
• A specific, unambiguous absolute timestamp
Options A, B — no actual data; just labels for what the user already sees
Option C ✓ — provides the exact information the relative display withholds
Option D — just restates the relative value in different words; adds no information
Key vocabulary:
• Relative timestamp — human-readable time relative to now ("3 days ago")
• Absolute timestamp — a specific date and time value (Thu, 12 Jun 2025 at 14:32 UTC)
• Progressive disclosure — showing summary info by default with detail on demand (hover)
• Tooltip data reveal — using tooltip to expose the precise underlying value behind a formatted display
6 / 10
John, a junior developer, is reviewing a PR that adds a new endpoint to the user authentication service. The code includes a field labeled 'refresh_token'. He needs help understanding what this token does and why it's critical for security. Which of the following help texts would be most effective?
The key here is explaining the *purpose* of the refresh token in a way a junior developer can grasp. Option 1 provides this context clearly, detailing its role in session management and access tokens. Options B and C are too technical for a beginner, while option D is simply insufficient.
7 / 10
Sarah, a UX writer on the mobile app team, is crafting help text for an API response that indicates a rate limit has been exceeded. The JSON response looks like this:
```json{
"status": "error",
"code": 429,
"message": "Too many requests"
}
```
Which of the following help texts is best to display alongside this response?
Sarah needs to translate the technical error code into plain language that the user can understand. Option 1 directly explains the meaning of the response and provides actionable advice (trying again later). Options B, C, and D are either too technical or simply don't explain what's happening.
8 / 10
David is writing a Slack message to announce the release of a new feature - automated log analysis. The message should include a link to more information. Which of the following options for help text is MOST effective?
David's goal is to inform users about the new feature and direct them to learn more. Option 1 provides a clear call to action with a link, which is essential for Slack messages. The other options are either too technical or simply don't encourage engagement.
9 / 10
Maria is writing the description for a pull request that implements a new user profile field. The PR includes code to validate the input data before saving it to the database. Which of the following descriptions best explains this functionality?
Maria needs to clearly communicate the value of this PR. Option 1 describes what's being added and how it's ensuring data quality. The other options are too technical or simply don't convey the importance of the validation step.
10 / 10
Ben is designing a standup update where he needs to explain that the team has been working on improving the performance of a critical API endpoint. Which of the following phrases would be MOST helpful in providing context for his audience?
Ben needs to quantify the improvement and explain its impact. Option 1 provides specific metrics (20% reduction) that are easily understood and demonstrate value. The other options are too technical or don't communicate the benefits of the work.
This exercise, "Tooltip & Help Text Writing", tests your understanding of ux writing vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this 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 presents a realistic 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.
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.
Who is this UX Writing exercise for?
It's designed for IT professionals and learners who want to sound natural discussing ux writing topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
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 UX Writing exercises?
Browse the full UX Writing exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.