Define the task
Write the person's goal, consequence, and context before choosing an interface pattern.
Use the checklist to expose unresolved decisions and assign the next check. A completed count organizes the discussion; approval should depend on the evidence and the consequences of a mistake.
Worked decision · constructed example
A team is choosing the interface for importing 200 contact records. The happy-path upload works, but duplicate rows, partial failure, and keyboard recovery still need decisions. An attractive upload area alone does not establish that the workflow is ready.
| Review question | Evidence in this constructed case | Next decision |
|---|---|---|
| What is the person's task? | Add contacts and know which records were accepted. | Write that outcome in the implementation brief. |
| Which alternatives fit? | File import and manual entry solve different volumes of work. | State when the person should choose each route. |
| What happens to duplicates? | The prototype has no defined duplicate policy. | Assign the product owner to choose skip, merge, or review behavior. |
| What happens after partial failure? | The accepted and rejected counts are not yet reconciled. | Specify a durable result and a route to correct rejected rows. |
| Can everyone recover? | Keyboard and assistive-technology checks are still outstanding. | Make those checks part of acceptance rather than marking the flow ready. |
| What supports the choice? | Standards inform control behavior; the task assumptions remain hypotheses. | Link the sources and test the import task with representative people. |
A useful review produces an implementation decision, its evidence, and named follow-up work. The same score can hide very different risks, so discuss the unresolved items individually.
This is an editorial review aid, not a validated usability scale or an accessibility certification. Use relevant standards and direct task evidence alongside it. Prioritize high-consequence failures even when most boxes are checked.
W3C informs the correction-feedback checks. It does not establish the validity of this checklist or its scoring bands. W3C: User notification ↗
The confirmation pattern informs reviewing a completed transaction and its next steps. The import policy in this example is a separate product decision. GOV.UK: Confirmation pages ↗
These source claims were checked on . The scenario and decision analysis are illustrative; the checks are a test plan, not reported results from a user study.
Start with the task and risk. Choose the pattern only after the context is clear.
Check each item supported by evidence. Use the count to find review gaps and discuss their consequences.
Use the score to locate the next design question. High-consequence flows need a complete state plan, accessibility checks, and evidence before implementation.
Write the person's goal, consequence, and context before choosing an interface pattern.
Compare alternatives and specify the states, access needs, and recovery route.
Resolve the remaining question and record its owner before implementation.
Check the evidence behind each answer and resolve remaining high-consequence risks before approval.
Use this in design reviews, issue templates, PR descriptions, or AI prompts.
Use the direct checklist URL when referencing it from articles, course notes, issue templates, or design-system docs.