Sample Manual QA & Usability Report

A format-and-method sample for the paid Manual QA & Usability Audit. The observations below are real things I saw during a two-minute first-pass on a public website, but the site is deliberately not named: this is not client work, I have no permission to publish a named critique, and no production impact is claimed. It exists so you can judge the structure and honesty of the report before engaging.

What this document is

The paid service delivers a short, structured report for one web app or job board: what I tested, what broke or felt wrong, how to reproduce it, severity, and a prioritized fix list. This sample applies that exact structure to a public site I opened in Chromium on 2026-11-21. The site is anonymized as “Subject Site”.

No screenshot, video, Safari/Firefox run, physical mobile-device test, analytics access, or client data is shown here. Those are only included in a paid engagement when access and permission exist.

1. Scope and limits, stated plainly

2. Severity rubric used in the report

SeverityMeaningExample in this method
CriticalBlocks a core task for most users, with no reasonable workaround.Search returns an error for every query.
MajorMisleads a user on important data or blocks a meaningful subset of a core task.Location/region label contradicts itself on a listing.
MinorConfusing or untidy, but the user can still complete the task.Duplicated count text on a card.
CosmeticVisual polish only; no task impact.Inconsistent spacing or a garbled apostrophe.

3. Worked findings

F1 — Duplicated hidden-count presentation on job cards. Severity: Minor.

F2 — Region/location label contradicts itself. Severity: Major.

F3 — Garbled apostrophe encoding in listing summaries. Severity: Cosmetic.

4. Copyable bug-report template

ID: F1
Title: Duplicated hidden-count presentation on job cards
Severity: Minor
Environment: Chromium desktop / page URL / date
Preconditions: country selector resolved; results grid visible
Steps:
  1. Open the page.
  2. Scan the tag row on a card with extra tags.
Expected: one count indicator, not two.
Actual: "+N" chip followed by "and N more".
Evidence: screenshot or DOM excerpt (included only when permitted)
Impact: harder scanning; no core-task block.
Recommendation: keep one count representation.
Owner/status: unassigned / open

5. Deliverable format in a paid engagement

A paid audit returns: (1) the agreed scope and environment, (2) the severity rubric, (3) findings with steps, expected/actual, evidence where permitted, impact and recommendation, (4) a prioritized fix list, and (5) one revision after delivery. I do not claim real-device or multi-browser coverage unless that access is provided, and I do not claim a formal UX-audit portfolio I do not have.

Service and pricing: Manual QA & Usability Audit on Contra — $150 / one surface. Back to services: Contract Engineering Services.