← Back to DrawChicken

Sample / Synthetic fixture / Non-client

Example technical website report

Source checked · Not browser verified

This report contains actual checker output from an owned synthetic test fixture, not an actual client audit. The deliberately broken local fixture was inspected as saved source text, without executing its HTML or requesting a website. It is a non-client sample, not a live capture.

The observations below need manual rendered-browser verification before they can be treated as defects. The checker has not tested resource availability, responsive behavior, form delivery, or a customer journey. No scores or business outcomes are claimed.

Source review record

Synthetic owned fixture: source-only sample

8 source observations requiring rendered-browser verification. These are not confirmed customer bugs. No live site was tested.

Owned fixture: fixtures/broken.html
Explicit synthetic source/base URL (not fetched): https://example.invalid/demo/index.html
Captured time: unknown

Observations and next verification

`UNRESOLVED_LOCAL_ANCHOR`

Source observation only · Browser verification required

Source location: Line 5, column 1 · Element a
Evidence: href=#missing; no matching source id or anchor name
Next manual verification: In a local rendered copy, check whether scripts create the target or intercept navigation; confirm keyboard navigation.

`MALFORMED_MAILTO`

Source observation only · Browser verification required

Source location: Line 6, column 1 · Element a
Evidence: href=mailto:not-an-address
Next manual verification: Inspect the rendered link and intended address with the owner. Do not send a message.

`MALFORMED_TEL`

Source observation only · Browser verification required

Source location: Line 7, column 1 · Element a
Evidence: href=tel:call-us
Next manual verification: Inspect the rendered contact link and intended URI syntax. Do not place a call.

`IMAGE_ALT_ABSENT`

Source observation only · Browser verification required

Source location: Line 8, column 1 · Element img
Evidence: Image has no alt attribute and no recognized source name.
Next manual verification: Determine whether the rendered image is informative or decorative. Verify its computed accessible name before proposing alt text.

`CONTROL_NAME_MISSING`

Source observation only · Browser verification required

Source location: Line 11, column 1 · Element input · ID unlabeled
Evidence: No nonempty recognized label, ARIA name, title or applicable native button name in source.
Next manual verification: Inspect the rendered control and accessibility tree, including dynamic labels and visibility. Do not submit the form.

`CONTROL_NAME_MISSING`

Source observation only · Browser verification required

Source location: Line 12, column 37 · Element textarea · ID notes
Evidence: No nonempty recognized label, ARIA name, title or applicable native button name in source.
Next manual verification: Inspect the rendered control and accessibility tree, including dynamic labels and visibility. Do not submit the form.

`CONTROL_NAME_MISSING`

Source observation only · Browser verification required

Source location: Line 13, column 1 · Element select
Evidence: No nonempty recognized label, ARIA name, title or applicable native button name in source.
Next manual verification: Inspect the rendered control and accessibility tree, including dynamic labels and visibility. Do not submit the form.

`CONTROL_NAME_MISSING`

Source observation only · Browser verification required

Source location: Line 14, column 1 · Element button
Evidence: No nonempty recognized label, ARIA name, title or applicable native button name in source.
Next manual verification: Inspect the rendered control and accessibility tree, including dynamic labels and visibility. Do not submit the form.

Checker scope and limitations

Static saved HTML snapshot only. No network requests, script execution, calls, email, form submissions or screenshots.
Source observations require manual rendered-browser verification. They are not confirmed accessibility defects, conversion/revenue estimates, security findings or form-delivery claims.
The stdlib HTML parser is tolerant, not a browser HTML5 tree builder or conformance validator. Truncated tokens are rejected; other malformed nesting can be recovered differently by browsers.
CSS, JavaScript, computed accessible names, shadow DOM, frames, authenticated states, responsive layouts and actual resource availability are not evaluated.
Accessible-name checks cover common native control patterns, not the full accessibility name computation. Explicitly hidden and template content is skipped. Custom ARIA controls are not inspected.
Empty image alt is recorded as an intentional/decorative possibility, not a defect. Absent alt with presentation/hidden semantics or another source name is not flagged.
Only fragment links resolving to this exact source document URL are compared to source IDs or legacy anchor names. Other documents, query variants and text fragments are not verified.
Contact URI checks catch obvious source syntax problems only. Address existence, deliverability, telephone routing and ownership are not tested.
Capture time is user-supplied provenance or unknown, never inferred from file mtime. A zero-observation report does not certify a site. Outreach is never authorized by this report.

Repair options and handoff

A real report would distinguish supported repair proposals from changes needing more investigation. It is one possible technical artifact, not a required first purchase or the main studio offer.

Repairs require agreed access, a backup or rollback plan, and approval before changes begin. A handoff would record the approved changes, verification performed, and unresolved limitations.

What a check cannot promise

A bounded check is not a full security audit, accessibility certification, legal opinion, or compliance guarantee. Automated checks cannot establish every usability issue or business outcome. Timing and costs are quoted only after the scope is understood.

Want to discuss a bounded website check or a software project? Contact DrawChicken with the context. Nothing is sent automatically.