The Life Starter
0 of 6 complete0%
Course Library · Lesson 4 of 6
Create · Guided lesson

Review access before testing

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

A product design case study with a need brief, concept comparison, prototype, access review, simulated usability log, and evidence-linked revision.

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

What to include

  • A product-need brief with simulated observations, a task-centered statement, constraints, and a success measure.
  • A three-concept comparison with a selected prototype, two decision criteria, and a switching condition.
  • A versioned low-risk reminder prototype with fictional content, a text description, and a core task sequence.
  • An access-review note with three corrected barriers, a text alternative, and explicit untested areas.
  • A neutral usability script and simulated observation log with a 60% unassisted completion result and issue notes.
  • A product design case study with a three-version history, evidence-linked changes, and an honest next-test plan.

Review and revise

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

  • Need and concept reasoning: distinguishes simulated observations from assumptions and compares three functionally different concepts against the same task and constraints.
  • Prototype and access continuity: preserves the fictional content across named versions, documents obvious access improvements, and distinguishes paper review from untested digital behavior.
  • Test integrity: uses a neutral voluntary test script, keeps assisted completion separate, computes three of five as 60%, and labels the records simulated rather than customer research.
  • Evidence-linked iteration: connects each Version 2 change to a specific tested issue, preserves the version history, and states that the revision still needs a new test.
Open the full course project
Want more background?
Before you begin

The idea in everyday life

People interact with information in different ways. A reminder can fail because text is hard to read, meaning depends only on color, wording is unclear, or a digital control cannot be reached with a keyboard. Review obvious barriers before inviting anyone to test. The supplied practice can be completed alone and does not simulate or claim another person’s disability experience.

The idea

Access review and user feedback complement each other; neither is a universal guarantee.

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

    Read the prototype for meaning without relying on color or decorative elements. Identify every place where a label, instruction, or location depends on a symbol or abbreviation that the case has not explained.

  2. 2

    Revise three obvious barriers using text labels, clear language, readable presentation, and a text alternative. Keep the underlying fictional return details unchanged so later comparisons address design rather than different content.

  3. 3

    Record what you checked and what is still untested. For a digital idea, list questions about keyboard use and assistive technology, such as screen readers. A paper prototype cannot show whether those features meet technical standards.

  4. 4

    Plan how varied feedback could be gathered respectfully in a future real project, including accessible materials and voluntary participation. For this course, use the supplied barrier list and never require a participant to disclose disability or imitate another person’s experience.

Example

See how it works.

Fictional practice: Version 1 contains the correct date and spelled-out location, but its visual review finds small decorative lettering, faint gray text, and crowded date and location fields. Dev uses larger plain type, darker text, and more space between fields. The labels “Return by” and “Return to” remain, and Dev keeps the selectable text description from Lesson 3. These presentation changes form Version 1.1 for testing. A future digital version would require keyboard and appropriate standards checks; a paper sketch cannot demonstrate those features. Dev records the three corrected barriers and does not claim that this review establishes accessibility for everyone.

Check your work

Did you cover these?

  • Meaning does not depend only on color
  • Readable type, contrast, and field spacing are reviewed
  • The review states scope and untested features
Your work

What to finish

An access-review note with three corrected barriers, a text alternative, and explicit untested areas.

Common mistake

Watch for this

Calling a design universally accessible after a checklist or one person’s feedback.

How can I tell I understand it?

You can demonstrate all three checks using your lesson deliverable and explain the reason for each decision.

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 prototype indicates “overdue” only with red color. What is a stronger design?
2A paper sketch shows a button. Can the learner claim its keyboard operation has passed testing?
3One participant with a disability finds the design useful. Which conclusion is appropriate?
0 of 3 answeredApply the lesson to a short question, then review the explanation.
4
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 initial barrier review, participant variation, evaluation limits, and combining user evaluation with standards. Web-specific conformance claims are not applied to paper prototypes; the course claims no accessibility certification.

Access: Public reading verified without an account; optional further reading, no paid course or certificate required.

Reuse: Reference only; original Life Starter explanations and practice. Public access is not permission to copy materials or logos.

Digital.gov — Design Concepts Guide
Source & access notes · checked 2026-09-10

Read human-centered design concepts, multiple iterations, prototype feedback, expertise limits, and participant roles. The fictional practice protocol is original and does not reproduce government templates.

Access: Public reading verified without an account; optional further reading, no paid course or certificate required.

Reuse: Reference only; original Life Starter explanations and practice. Public access is not permission to copy materials or logos.

Report a problem with this lesson

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

No sign-in needed.