The Life Starter
0 of 6 complete0%
Course Library · Lesson 5 of 6
Digital · Guided lesson

Distinguish usability evidence from a functional failure

About 22 minutes · 6 reading + 16 practice and checks
Time includes reading, practice, and questions. Extra videos or further study are optional.
See this course’s project requirements

Review the Room Picker simulation from initial contract through a verified rule repair.

Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.

What to include

  • Define scope and observable acceptance criteria.
  • Record eight diverse cases with expected and observed outcomes.
  • Write a minimal reproducible bug report with impact.
  • Show a one-change repair experiment and relevant comparisons.
  • Deliver retest evidence and a usability hypothesis with honest limits.

Review and revise

Use these criteria to check your work and choose what to improve.

  • Coverage: cases represent relevant classes and boundaries.
  • Reproducibility: state, steps and results are sufficient to repeat.
  • Reasoning: the repair follows evidence and preserves valid behavior.
  • Handoff: claims stay within the observed version and scope.
Open the full course project
Want more background?
Before you begin

The idea in everyday life

Functional checks ask whether the product does what its specification says. Usability observations ask whether people can understand and complete the task. Accessibility evaluation adds further perspectives and should include relevant users where possible. Here you will analyze invented observation notes, clearly labeled as synthetic, without recruiting participants or pretending a classroom simulation represents real users.

The idea

A product can follow its rules and still make the user’s task difficult.

Try it

One step at a time.

Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.

  1. 1

    Use the supplied fictional task: "Choose two places for Cedar and check the details without confirming." The v2 button still reads "Next" and opens the Review screen, where a separate Confirm button appears.

  2. 2

    Read three invented observations, also called synthetic observations: tester A pauses at Next; tester B clicks it but worries a booking was sent; tester C reaches Review and completes the task. Record their actions before explaining why.

  3. 3

    Classify the issue as uncertain action meaning rather than a proven booking failure. All three can reach Review, but two notes show uncertainty about whether Next commits the request.

  4. 4

    Propose changing Next to "Review selection" and adding "You will confirm on the next screen." Preserve the no-real-booking explanation for the practice flow.

  5. 5

    Write a future evaluation question: can a reader predict what this button does before activating it? Label the evidence synthetic, and describe a consent-based user review as optional later work rather than completed research.

Example

See how it works.

Fictional observation table: A waits eight seconds, saying "Will this book it?" B presses Next, then returns to inspect whether a confirmation occurred. C reads the Review screen and stops as requested. None of these notes proves that a real booking happened. They suggest that the action label does not make the next state clear. The proposed label "Review selection" states the immediate action, while a brief instruction clarifies that confirmation comes later. This is a hypothesis for further testing, not a claim that three invented testers represent all users or all accessibility needs.

Check your work

Did you cover these?

  • All observations are labeled synthetic.
  • Functional and usability findings are distinguished.
  • The proposed improvement has a future evaluation question.
Your work

What to finish

An observation-to-hypothesis note and one clearly testable wording improvement.

Common mistake

Watch for this

Treating synthetic observations as completed user research or equating hesitation with user incompetence.

How can I tell I understand it?

Separate observed action, inferred difficulty and proposed change.

Try 3 questions

Quick knowledge check

Answer all 3 questions. Get at least 2 right and the lesson completes automatically.

Not yet passed

You’ll get an explanation for each answer. Signed in? Your results save to your account.

1A participant hesitates at a working button and asks what it does. What does this support?
2Which button label better communicates opening a review screen before commitment?
3You analyze three invented observation records. How should your report describe the evidence?
0 of 3 answeredApply the lesson to a short question, then review the explanation.
5
Finish this lesson

Pass the check. We’ll save the progress.

Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.

Go to the knowledge check
Tools, templates, and lesson sources

Tools and templates

Tools open in a new tab so you can keep your place here.

Sources and further reading

Explore the references behind this lesson.

W3C WAI — Involving Users in Evaluating Web Accessibility
Source & access notes · checked 2026-09-10

Read the distinction between standards evaluation and user evaluation; synthetic observations are explicitly labeled and no disability simulation substitutes for user involvement.

Access: Free public reading; no account or certificate is required for this Life Starter course.

Reuse: Linked for reference. Examples, activities and assessments here are original; free access alone does not grant permission to reuse source text or branding.

Report a problem with this lesson

Tell us what went wrong. Please leave out personal information and private project contents.

No sign-in needed.