UX Error Messages and Onboarding 1 — Questions and Answers
Question 1: What are the three components of an effective error message?
- Apology, explanation, and legal disclaimer
- Problem identification, cause explanation, and solution guidance (Correct answer)
- Error code, technical description, and stack trace
- Warning icon, red color, and 'Error' label
Correct answer: Problem identification, cause explanation, and solution guidance
Effective error messages tell users what went wrong, why it happened (if helpful), and what they can do to fix it.
Question 2: What is the ideal placement for an inline form validation error message?
- At the top of the page in a banner alert
- In a modal popup that interrupts the user's flow
- Directly below or beside the field that caused the error (Correct answer)
- At the bottom of the form near the submit button
Correct answer: Directly below or beside the field that caused the error
Inline validation errors placed adjacent to the relevant field reduce the cognitive work of matching errors to their fields, especially in long forms.
Question 3: Which strategy for form validation messaging is most user-friendly?
- Validate all fields only when the user submits the form
- Display all errors upfront before the user has typed anything
- Use real-time inline validation that confirms correct input as users complete each field (Correct answer)
- Show errors only if the user asks for help via a tooltip
Correct answer: Use real-time inline validation that confirms correct input as users complete each field
Real-time inline validation gives users immediate feedback as they complete each field, preventing them from submitting a full form only to discover multiple errors.
Question 4: What tone is appropriate for a 404 error page on a consumer product?
- Highly technical to explain why the page was not found
- Apologetic and overly formal to acknowledge the inconvenience
- Light, helpful, and redirecting — acknowledging the issue while guiding users to a useful next step (Correct answer)
- Blame-assigning to indicate the URL the user entered was wrong
Correct answer: Light, helpful, and redirecting — acknowledging the issue while guiding users to a useful next step
A 404 page should acknowledge the error with a light touch and immediately guide users to the homepage or a search function so they can continue their journey.
Question 5: Why should error messages avoid blaming the user?
- Legal compliance requires neutral language
- Blame increases frustration and erodes trust, making users less likely to retry or continue using the product (Correct answer)
- Users never make errors, so blame is inaccurate
- Blaming the user violates WCAG guidelines
Correct answer: Blame increases frustration and erodes trust, making users less likely to retry or continue using the product
User-blaming error messages like 'You entered an invalid email' increase frustration; neutral or system-focused framing like 'That email doesn't match our records' maintains goodwill.
Question 6: What is the purpose of a 'success state' message in a form workflow?
- To upsell the user on additional product features
- To confirm the user's action was completed successfully and tell them what happens next (Correct answer)
- To collect user feedback about the form experience
- To redirect users away from the form page automatically
Correct answer: To confirm the user's action was completed successfully and tell them what happens next
Success messages confirm the action was completed and set expectations about next steps (e.g., 'Check your email to verify your account'), closing the feedback loop.
UX Error Messages and Onboarding 1
What are the three components of an effective error message?