Controlled demonstration. Deliberate fixture defects; not customer results. The recorded temporary local URL is no longer running. Read the before-and-after walkthrough.
Handoff Desk · demo / WEBSITE HANDOFF EVIDENCE
Cedar Studio — controlled demonstration
http://127.0.0.1:62226/
17 Nov 2026, 12:08 UTC · staging · msedge.exe 157.0.4341.60
Declared main-button check: 0 passed; 2 expected destination not reached; 0 could not complete.
These results apply to the named control and destination in each recorded browser view, separately from page observations.
4 rule types produced 6 recorded entries. Repeated elements and browser views are preserved in the evidence.
This is an automated report, ready to use without mandatory operator review. It is not acceptance of the website or a guarantee that it has no bugs.
For the customer and developer
Use the plain explanation to decide what to discuss. Open the locations and developer details to reproduce an observation and copy a specific request. Visual observations need context; declared action results apply only to the recorded expectation.
1Pages visited
4Rule types with observations
6Recorded entries, not independent defects
DECLARED BEHAVIOUR
Main-button action
Only the named control and expected destination below were tested. A successful navigation does not verify form delivery, payments or the whole visitor journey.
Expected result not reacheddesktop
Book a consultation
After one click, the browser URL was http://127.0.0.1:62226/missing-booking (last HTML/navigation response: HTTP 404). Expected http://127.0.0.1:62226/contact.
Starting page
http://127.0.0.1:62226/
Expected destination
http://127.0.0.1:62226/contact
Observed address
http://127.0.0.1:62226/missing-booking
Recorded steps
Open http://127.0.0.1:62226/ at 1440 × 1000.
Find exactly one link or button named “Book a consultation”.
Click once and expect the exact URL http://127.0.0.1:62226/contact.
Action screenshotDeclared action result — desktop
Expected result not reachedmobile
Book a consultation
After one click, the browser URL was http://127.0.0.1:62226/missing-booking (last HTML/navigation response: HTTP 404). Expected http://127.0.0.1:62226/contact.
Starting page
http://127.0.0.1:62226/
Expected destination
http://127.0.0.1:62226/contact
Observed address
http://127.0.0.1:62226/missing-booking
Recorded steps
Open http://127.0.0.1:62226/ at 390 × 844.
Find exactly one link or button named “Book a consultation”.
Click once and expect the exact URL http://127.0.0.1:62226/contact.
Action screenshotDeclared action result — mobile
OBSERVATIONS TO DISCUSS
What needs attention
Observation — assess in context1 recorded entry
Content extends beyond the browser width
Part of the page reaches beyond the checked width. It may need sideways scrolling, or it may be intentional off-screen content.
Request for the developer: Reproduce the page at the recorded browser size. Inspect the listed element and confirm whether the overflow is intentional; otherwise repair the layout.
Locations and evidence (1)
mobile · http://127.0.0.1:62226/
Recorded element — mobile Cropped context; the outline locates the recorded element and does not itself confirm a defect.Developer details and a request to copy
Rule
horizontal-overflow
Conditions
390 × 844 · msedge.exe 157.0.4341.60
Tool technical priority
high — this is not a confirmed measure of business impact
Recorded element
html > body > main > div
Raw observation
Document width is 1126px; viewport content width is 390px. Candidates: html > body > main > div (1100px)
Rule suggestion: Inspect the listed elements for fixed widths, transforms or off-screen content. Some off-canvas designs are intentional.
Select and copy this request:
Reproduce the page at the recorded browser size. Inspect the listed element and confirm whether the overflow is intentional; otherwise repair the layout.
Page: http://127.0.0.1:62226/
Browser view: 390 × 844
Observation: Horizontal overflow at 390px
Evidence: Document width is 1126px; viewport content width is 390px. Candidates: html > body > main > div (1100px)
Element: html > body > main > div
Observation — assess in context1 recorded entry
An internal link returned an error
A checked destination responded with an unsuccessful status. Its effect on the visitor needs context.
Request for the developer: Open the recorded link destination and correct the address, redirect or server response if needed.
Locations and evidence (1)
all · http://127.0.0.1:62226/
No located screenshot evidence was recorded for this entry. Use the page capture and technical details where available.
Developer details and a request to copy
Rule
broken-link
Conditions
all · msedge.exe 157.0.4341.60
Tool technical priority
high — this is not a confirmed measure of business impact
Raw observation
Link target: http://127.0.0.1:62226/missing-booking
Rule suggestion: Fix the link target or route, or review whether the server response is intentional.
Select and copy this request:
Open the recorded link destination and correct the address, redirect or server response if needed.
Page: http://127.0.0.1:62226/
Browser view: all
Observation: Internal link returned HTTP 404
Evidence: Link target: http://127.0.0.1:62226/missing-booking
Observation — assess in context2 recorded entries
A visible image did not load
An image visible to the browser had no successfully loaded image content at the time of this check.
Request for the developer: Check the image address, response and permissions, then repeat the page check.
Locations and evidence (2)
desktop · http://127.0.0.1:62226/
Recorded element — desktop Cropped context; the outline locates the recorded element and does not itself confirm a defect.Developer details and a request to copy
Rule
broken-image
Conditions
1440 × 1000 · msedge.exe 157.0.4341.60
Tool technical priority
medium — this is not a confirmed measure of business impact
Recorded element
html > body > main > img
Raw observation
http://127.0.0.1:62226/missing-image.png
Rule suggestion: Check the image URL, access permissions and response content.
Select and copy this request:
Check the image address, response and permissions, then repeat the page check.
Page: http://127.0.0.1:62226/
Browser view: 1440 × 1000
Observation: A visible image did not load
Evidence: http://127.0.0.1:62226/missing-image.png
Element: html > body > main > img
mobile · http://127.0.0.1:62226/
Recorded element — mobile Cropped context; the outline locates the recorded element and does not itself confirm a defect.Developer details and a request to copy
Rule
broken-image
Conditions
390 × 844 · msedge.exe 157.0.4341.60
Tool technical priority
medium — this is not a confirmed measure of business impact
Recorded element
html > body > main > img
Raw observation
http://127.0.0.1:62226/missing-image.png
Rule suggestion: Check the image URL, access permissions and response content.
Select and copy this request:
Check the image address, response and permissions, then repeat the page check.
Page: http://127.0.0.1:62226/
Browser view: 390 × 844
Observation: A visible image did not load
Evidence: http://127.0.0.1:62226/missing-image.png
Element: html > body > main > img
Observation — assess in context2 recorded entries
The browser recorded a JavaScript error
A script raised an error. This alone does not show which visitor actions were affected.
Request for the developer: Reproduce the recorded browser error and establish whether it affects the agreed visitor action.
Up to 1 same-origin pages. desktop 1440 × 1000; mobile 390 × 844. Recorded internal links, page metadata, browser errors, layout observations and automated accessibility rules.
Outside the automated scope: form delivery, payment completion, authenticated areas, external link targets, physical phones, Safari and other browser engines, design-mockup approval, security testing, legal compliance and overall WCAG conformance.
Narrow Chromium captures are not tests on a real phone. The scanner uses fresh browser sessions, bypasses CSP for instrumentation and blocks service workers. Screenshot evidence represents one moment. Automated accessibility rules can require further contextual review.
Additional handoff checks and separate workspace records
Submit a test enquiry and confirm it reaches the intended inbox or CRM.
Workspace record: pending. These records are separate from the automated checks.
Test booking, checkout or payment flows when applicable.
Workspace record: pending. These records are separate from the automated checks.
Review interactions on real devices and the required browsers.
Workspace record: pending. These records are separate from the automated checks.
Review content, consent, analytics and account ownership with the client.
Workspace record: pending. These records are separate from the automated checks.
Confirm backups, rollback access and the support handover.
Workspace record: pending. These records are separate from the automated checks.
Captured pages
Expand a capture to inspect the full page. Outlines in the observations identify recorded element positions; they do not determine whether a design choice is wrong.
Home — Cedar Studio demo
http://127.0.0.1:62226/
desktop · 1440 × 1000 · captureddesktop capture of http://127.0.0.1:62226/mobile · 390 × 844 · capturedmobile capture of http://127.0.0.1:62226/