Quiz feedback: show the mistake and the next step

Keep the learner’s submitted choice visible.

Khan Academy marks the selected incorrect option and provides a Not quite panel with Try again, Get help and Skip for now. Tahanan highlights the chosen wrong translation with an x and offers Try Again. Both retain a connection between the user’s action and the feedback state.

Distinguish selected, submitted and graded states. A learner should know whether an answer is still editable or has already been checked. If a retry clears the previous selection, do so deliberately and retain enough context to understand the earlier mistake. Do not change the question while leaving old feedback attached to it.

Keep the submitted response readable when the prompt is long or contains media. A useful correction needs the relevant context, not merely a general Incorrect label. For multi-select questions, identify whether the answer set was incomplete or contained an extra choice if the product can support that explanation truthfully.

Differentiate revealing an answer from explaining it.

ABA English displays the user’s answer and the correct answer together. Quizlet provides a Missed state with a term and its corresponding definition. These screens illustrate how showing the expected response can resolve one uncertainty while still leaving room for a deeper explanation.

Name the relationship between the two responses. Your answer and Expected answer are more informative than placing two phrases in differently colored cards with no labels. If several answers can be acceptable, avoid presenting one preferred wording as the only possible truth unless that is the actual assessment rule.

A correction should not look like a new answer option that still needs selection. Keep the feedback surface distinct from the input surface. If revealing the answer affects the score or a future retry, explain that consequence at the point of use rather than letting learners discover it from a changed progress number later.

Offer a useful explanation route.

Gleam shows a Best answer and a WHY IT WORKS explanation alongside RETRY and CONTINUE. Coconote identifies a correct option and exposes Review why. These references show two choices for depth: explanation within the feedback surface or an explicit route to inspect it.

Keep explanations specific to the actual submitted choice when possible. A generic encouragement message does not explain why one response was wrong. If an explanation is generated, distinguish it from the grading rule and provide an appropriate way to report an issue. Do not let a plausible paragraph conceal an inconsistent answer key.

Avoid forcing a lengthy explanation over the entire task when the learner simply needs to review a known mistake. A concise summary with an accessible expansion can preserve flow. If the explanation opens another surface, return to the same graded question with the relevant retry and continuation actions still available.

Connect help to the concept, not a generic destination.

Uxcel offers View theory beneath an Incorrect state. Pickup Music pairs a refresher suggestion with Retake question and Go to Lesson. These actions make a useful distinction between another attempt and revisiting the material that supports the answer.

Take the learner to the relevant explanation rather than an unrelated course home screen. Preserve the question identity and progress so returning from the lesson does not start an entirely different quiz. If review opens a separate resource, make the return path understandable and avoid silently consuming another attempt.

Decide whether review is optional, recommended or required, and communicate that choice honestly. A large primary button to revisit a lesson can be appropriate, but the learner should still understand whether the current answer has been recorded. Do not imply that viewing theory automatically repairs the grade or completes the question.

Make the next action’s meaning predictable.

Preply shows an incorrect selected option, an error message and Continue. Cake uses So close feedback with a Next action and audio support. These interfaces demonstrate why a continuation label must align with the assessment’s behavior, not just move the person away from the red state.

Define whether Continue accepts the recorded mistake and advances, opens an explanation or starts a retry. Use a more specific label when the distinction is consequential. If attempts are limited, make remaining attempts and their consumption understandable before another submission rather than treating a retry as a harmless navigation action.

Avoid encouraging speed through correction at the expense of comprehension. The primary action needs visual clarity, but it should not cover the selected answer or make the explanation inaccessible. If the product auto-advances, provide enough time and an appropriate way to revisit feedback, including when assistive technology is reading it.

Keep grading separate from local presentation.

Represent question identity, submitted answer, grading result and attempt count explicitly. A double tap should not consume two attempts or advance twice. If grading needs a network response, keep the answer in a pending state and do not display confident feedback before the result is available.

Define retry behavior for the same item, a new variant and a later review session. Clearing a selection does not necessarily reset the score. Preserve the recorded result appropriately while letting the interface explain what a new attempt can change. Keep answer-key updates and explanation revisions coherent when content changes.

Handle ambiguous or disputed questions through a report route that retains context without requiring the learner to reconstruct the prompt. Do not silently replace their graded response after a content update. A reliable correction flow includes the possibility that the question or answer key, not the learner, is wrong.

Test understanding of the feedback state.

Ask participants to answer incorrectly, explain which response was graded and choose between retry, review and continuation. Inspect whether they can predict what happens to the attempt count and score. If they correctly notice the error but cannot tell whether Continue advances, the feedback remains incomplete.

Repeat with long answers, multi-select choices, media prompts, delayed grading and an explanation that fails to load. Measure accidental extra submissions, repeated attempts caused by unclear state and difficulty reaching the relevant review material. Completion speed alone cannot establish educational effectiveness or knowledge retention.

Use explicit status text and icons rather than red and green alone. Announce the grading result once in a meaningful focus order, preserve access to the submitted choice and support large text without covering the controls. Avoid automatic sound or motion that is the only indication of correctness, and test feedback with a screen reader.

Review the correction moment.

Use these checks on a working build, not only on the polished reference state.

• ✓Retain the submitted answer and question context.
• ✓Distinguish selected, pending and graded states.
• ✓Label the expected response and explanation clearly.
• ✓Separate retry, theory review and continuation.
• ✓Define scoring and attempt consequences.
• ✓Test status announcements and disputed-question recovery.

Related learning-app decisions

For bringing someone back to an unfinished lesson, compare the learning-app re-engagement examples and preserve the same question context after review.

For the broader product introduction, study the language-learning onboarding examples without using the correction state as another onboarding interruption.