01 · CONTEXT
Set up the report before recording findings
Complete the report title, evaluator, interface or project,
evaluation method, and evaluation goal or task. These fields form
the context of your submitted report and are required before you
can export the PDF.
02 · FINDINGS
Record one usability issue at a time
Each row should describe one focused issue. Give it an ID,
identify where it occurs, choose a category, record what you
observed, select a primary heuristic, and recommend what could be
changed or tested next.
OBSERVATION FIRST
Describe what happened before explaining why
Start with evidence from the evaluation. Avoid inventing findings
or reporting what you expected to happen instead of what was
observed. A good description should let another designer
understand the issue without being present for the test.
HEURISTICS
Use the library as an analytical reference
The library combines Nielsen, Andy Budd and Bruce Tognazzini.
Shared concepts are consolidated and the library includes
definitions, things to look for, examples and related principles.
You do not need to memorise the list.
PRIMARY + RELATED
Choose the principle that best explains the issue
Select one primary heuristic. Related principles can be useful
when the same issue can be understood from more than one
perspective. Use them to deepen your explanation rather than to
collect labels.
SEVERITY
Prioritise issues by impact
Minor indicates a lower-impact usability concern.
Moderate indicates a problem that meaningfully
interferes with the interaction.
Serious indicates a high-impact problem that
significantly obstructs, confuses or prevents the intended task.
Use severity to help prioritise the report.
OPTIONAL NOTES
Use evidence and heuristic reasoning when useful
Why does this heuristic apply? gives you space to
explain the connection between the observation and the principle.
Evidence / notes can capture participant
comments, frequencies, screenshot references or other supporting
information. Both are optional.
VALIDATION
Required information cannot be left blank
The tool will stop a finding from being saved when required fields
are missing. It will also stop PDF generation until the report
context is complete. Red fields identify exactly what needs
attention.
REVIEW
Use the table to check your report
Saved findings return to the condensed table. Click any row to
edit it. Use the search, severity, category and heuristic filters
to review particular groups of issues, then sort them to help
prioritise your work.
PDF OUTPUT
The PDF is a report, not a screenshot of the tool
Print / Save PDF creates a simplified document containing the
report context and findings table. The working editor, filters and
other interface controls are removed from the print layout. A
generated timestamp is included.
LOCAL STORAGE
Your work is stored in this browser
The tool uses browser localStorage and has no server-side
database. Browser data can be cleared or lost, so export JSON
regularly, especially before changing browser, device or computer.
REPORT QUALITY
A usability report is detailed evaluation evidence
A usability report records focused findings, analysis and
recommendations from evaluation. It is not the same as a UX case
study or a visual summary. Prioritise clear evidence and
well-substantiated reasoning over the number of findings.