Deliverable preview / Fictional example
Sample website review
See how the report presents findings, steps to reproduce them, and suggested fixes. This example uses a fictional website.
Summary
In this fictional scenario, a visitor can discover the service but one quote button leads to a missing page. A mobile overlay blocks part of the contact form, and a required field has no programmatically associated label. These are example findings, not measured results.
High priorityES–001 · Fictional
Quote link opens a missing page
- Affected location
- https://example.invalid/services · Both example viewport sizes
- Reproduction steps
- Open the Services page.
- Activate the “Request a quote” button below the service list.
- Inspect the destination page.
- Expected behaviour
- The quote request page loads with a visible way to begin an enquiry.
- Illustrative observation
- The link points to /quote-old, which displays a 404 page.
- Evidence status
- Fictional description only. A real finding would include the observed destination, timestamp, browser details and a screenshot or relevant response evidence.
- Suggested action
- Confirm the current enquiry URL and update this CTA. Check any other links that use the same destination.
- Retest status
- Pending. No change or outcome has been verified.
Medium priorityES–002 · Fictional
A fixed banner overlaps the contact form
- Affected location
- https://example.invalid/contact · 390 × 844 example viewport
- Reproduction steps
- Open Contact at the example mobile viewport.
- Leave the announcement banner open.
- Scroll to the lower section of the form.
- Expected behaviour
- The form fields and its action remain visible and operable, or the overlay can be dismissed.
- Illustrative observation
- The fixed banner covers the form action. Its dismiss control falls outside the visible viewport.
- Evidence status
- Fictional description only. A real finding would include the viewport, a captured screenshot and the observed behaviour during scrolling.
- Suggested action
- Review fixed-position behaviour at narrow widths. Keep dismissal visible and allow enough page space for the final form controls.
- Retest status
- Pending. No change or outcome has been verified.
Medium priorityES–003 · Fictional
A required field has no associated label
- Affected location
- https://example.invalid/contact · Both example viewport sizes
- Reproduction steps
- Open the Contact form.
- Inspect the required project-summary input and its accessible name.
- Move focus to that field using the keyboard.
- Expected behaviour
- The field has a persistent visible label and a programmatically associated accessible name.
- Illustrative observation
- Only a placeholder describes the field. There is no associated label or alternative accessible name.
- Evidence status
- Fictional description only. A real finding would include the observed markup or accessibility tree and relevant screenshot.
- Suggested action
- Add a visible label associated with the field’s unique ID, then confirm the accessible name.
- Retest status
- Pending. This example is not an accessibility compliance assessment.
What a check record distinguishes
| Check | Sample status | Interpretation |
|---|---|---|
| Primary CTA destination | Illustrative issue | Fictional finding ES–001 demonstrates a reproducible record. |
| Mobile form visibility | Illustrative issue | Viewport testing does not establish physical-device behaviour. |
| Live form submission | Not tested | No operator authorization; no enquiry was submitted. |
| Inbox delivery | Not tested | No mailbox evidence. A success screen would not prove delivery. |
| Safari / Firefox | Out of scope | This pilot specifies one Chromium browser. |
| Security / compliance | Out of scope | A journey review is not a penetration test or certification. |
Suggested handover order
- Correct the quote destination and verify it from the affected page.
- Resolve the narrow-viewport overlap and check keyboard operation.
- Associate the project-summary label and confirm its accessible name.
- Request the included retest of reported findings within seven days of delivery.
Priority reflects the reviewer’s assessment of the observed journey impact. It does not quantify lost enquiries or guarantee an increase in conversions.