L14 · Make the output usable by another person
Skill packs and prompts are provided in English so they work best with the AI tools. Use them as-is.
Make the output usable by another person
Learning time: about 23.4–34.2 active minutes. Choose ONE presentation: the text (about 4.2 minutes, estimated) OR the lesson video (3:21, measured). Then 20–30 minutes of practice and checking (estimated). Do not count both presentations. Setup delays and optional extra study are separate; learner timing has not yet been piloted.
Where you are: Module 7, lesson 2 of 2.
A correct calculator can still be difficult to use. In this lesson you will inspect the visible page, keyboard operation, error messages and handover instructions. O7 and O8 require usable evidence, not just a screenshot that looks attractive.
What you will do
Ask whether someone can find the inputs, understand the result, recover from a mistake and use the page on a narrow screen. Save observations with the tested version. This is a practical accessibility and usability check, not a claim of complete standards compliance.
Teaching
Use descriptive labels next to controls. A placeholder that disappears when someone types is not a reliable replacement for a label. Money needs a named currency. Capacity and attendance need whole-person units. Error messages should explain what to change and must not depend only on red coloring.
Keyboard access matters because some people cannot use a mouse. Press Tab through the page. Each important control should receive visible focus in an understandable order. Enter or Space should operate the button as appropriate. Results should be available as text, not only in a chart. A narrow screen should not hide the action button or force horizontal scrolling for an ordinary form.
An automated checker can identify some faults. It cannot establish that a beginner understands the decision, that all screen readers work, or that the final LMS behaves like your local file. Separate “checked locally” from “tested by representative users.” Final recordings also need checked captions; a narration script is not an audio-aligned caption file.
Worked example
A prototype labels an input “N” and displays a green 84 with no explanation. The number is right for one case, but a colleague cannot tell whether it is revenue, profit or attendance. Improve the output to “Surplus / loss: USD 84.00,” retain the assumptions and state that bookings remain unconfirmed. The change makes the same calculation easier to interpret; it does not create new financial evidence.
Now enter 13 attendees against capacity 12. Suppose the error says “invalid” but leaves 84 on screen. A busy user may reuse 84. Clear the stale result and say “Attendees cannot exceed capacity.” Then return to valid input and confirm that the error disappears and the result recalculates.
Do it yourself
Open your own calculator from a local file or an approved local preview. Do not publish it. With the mouse aside, move through every input and Calculate. Note any missing focus indicator or unexpected order. Try an error and a correction. Resize the browser to roughly 375 pixels wide or use its device preview. Check labels, button, result and long messages. Zoom the page and see whether the content remains readable.
Give a reviewer this request:
Inspect this exact local calculator version. Check labels, currency, whole-number constraints, keyboard order, visible focus, error recovery, old-result clearing and narrow layout. Report observations separately from assumptions. Do not claim full accessibility compliance or user testing. Do not change the file. Recommend the smallest repair for each observed problem.
Write a five-line README: purpose, how to open, inputs, what the output means and limits. Close the page, reopen it using only those instructions, and repeat a normal and invalid case. Capture no personal desktop content in evidence screenshots.
Feedback and retry
Pause. A satisfactory record names what you actually did: “Tab reached five labelled inputs and Calculate; Enter submitted; capacity error cleared old output; 375-pixel view had no horizontal overflow.” “Accessible” alone is too broad. If you used only an AI reading the HTML, say code inspection rather than keyboard test.
Retry with a small decision memo: remove all colors and ask whether its headings and wording still distinguish facts, assumptions and decisions. Explain the currency and an unresolved decision in plain text. This checks transfer to documents without requiring another website.
Check your understanding
Choose an answer and write one sentence explaining why before you read the answers.
- A browser screenshot shows a beautiful calculator. Does it prove keyboard access?
- A. Yes, if every control is visible.
- B. No: you need an actual interaction test.
- C. Yes, if the screenshot was taken at 375 px width.
Answers
- B. No. You need an actual interaction test. A screenshot can support a visual observation, while keyboard use, assistive technology and learner comprehension need their own evidence.
Summary
A usable output communicates what to do, what happened and what remains uncertain. Keep the limits of each check visible so the producer knows what still needs a learner or accessibility specialist.
Sources
Course-owned usability procedure (internal quality controls still in draft). Local reference observations are in the course production record (not a learner download). They cover the reference file only and are not final LMS evidence.
