Verification
What was checked.
What still needs work.
A release is more than an attractive screenshot. Useful verification describes what was checked, on which version, and what remains unverified.
Evidence, not a badge
A specific result.
Not a blanket promise.
Name the check.
Identify the page, task, environment, and expected behavior.
Record what happened.
Keep the observed result and supporting evidence together.
Keep the limitations visible.
Untested devices, integrations, or user tasks do not become passing results.
What the checks mean.
Does a passing test mean the whole site is perfect?
No. A test supports a specific result within its scope. Changes can invalidate that evidence.
What remains unverified in this preview?
Real email delivery, unfamiliar-customer comprehension, physical devices, broader assistive-technology coverage, and field performance. Browser checks do not replace those tests.