When this helps
Use a visual audit before publishing a graphic, releasing an interface, or declaring a design fixed. Source code can tell you what was intended. The rendered result tells you what a reader gets.
From a vague verdict to a useful finding
“Looks good.”
No viewport. No revision. No evidence that the page was opened or the controls were used.
The timestamp is clipped.
At 360 px wide, the tracker’s evidence time runs beyond the card. Let the row wrap, then recheck the same revision at that width and with enlarged text.
Illustrative review notes, not findings about this live page.
The method
- Capture the real frame.
Open the exact revision at desktop and mobile sizes. Keep a full-frame capture before cropping a detail. Record the viewport, browser, and state.
- Check the content and composition.
Look for weak hierarchy, cramped spacing, poor contrast, overflow, unreadable labels, and mismatched numbers. Review a tracker at the size it will appear in chat.
- Use the controls.
Test keyboard focus, links, downloads, repeated clicks, long text, empty states, and failed actions. A screenshot cannot prove an interaction works.
- Keep the character. Remove the friction.
This workshop is intentionally whimsical. Test its bounce, pause control, and reduced-motion mode rather than replacing its personality with the main docs theme.
- Recheck the changed result.
Repeat the original conditions after a fix. Report what is fixed, what remains, and what you could not test.
Give each finding a job
Record the location, observed behavior, evidence, effect on the task, severity, and proposed correction. Mark a design preference as a suggestion, not a defect.
| Severity | Use it when |
|---|---|
| Blocking | The primary task cannot be completed or key information is inaccessible. |
| Major | A substantial usability or accuracy problem has a workaround. |
| Minor | A localized defect does not block the task. |
| Suggestion | You are proposing an optional improvement or a stylistic preference. |
When the browser will not cooperate
Record what failed: The browser did not start, the computer was unreachable, a sign-in expired, or the page returned an error. Those are different problems. Do not claim a reboot fixed access without checking that the computer is reachable again.
Source review and supplied screenshots may still be useful. Label them as code-only or screenshot-only. Neither establishes the current live appearance, and neither justifies “visually verified.”
No amount of careful prompting repairs an unreachable machine. The field notes explain why this is part of the workflow. The field report covers the daily crashes in more detail.
Try it on your own work
Version 0.2.0 · MIT · Copyable workflow instructions, not a native plugin installer. Adapt the inputs and check the tools available in your account. Local page tests are not live dot or connector certification. Manifest.