Morten A. Giraffe

PUBLIC PREVIEW · NOT FOR SALE

WEBSITE AUDIT & CLIENT HANDOFF KIT

Find it.
Fix it.
Prove it.

Turn “we should fix that” into work someone can actually finish.

A practical system for independent designers and small teams: spot the friction, agree the scope, verify the change, and hand it over with a clear next step.

No email gate. Real editable files. One clearly fictional example.

JUNIPER / FICTIONAL PROJECTJCR—04

A finding is
just the start.

Make the next step unmistakable.

OBSERVATION“Book” opens an inquiry.
01
DECISIONConfirm the intended flow.
02
ACCEPTANCELabel predicts the next screen.
03
STATUS / OPENEvidence before confidence.
01 → 05

One connected trail.
Observation to ownership.

20practical checks
with manual tests
07editable files
you can actually use
01worked finding
from start to handoff

Not a score.
A way to decide what happens next.

THE WORK AFTER THE CHECKLIST

A list tells you what to notice.
This connects the work.

An audit that stops at “here are the problems” leaves someone else to work out what matters, who owns it and what “fixed” means.

This kit puts the test, evidence, owner and acceptance criteria beside the finding. Then the same record becomes a scope conversation, a client report and a handoff.

You still do the thinking. You get a clearer place to put it.

Inspect every included file

GOOD FIT

You build or improve client websites.

You want a repeatable way to review a service site, explain findings and close a handoff without pretending every question has an answer.

NOT THE PROMISE

No magic grade. No compliance badge.

This is a manual workflow, not an automated scanner, legal opinion, security review or full accessibility certification. Specialist and real-device reviews can still be needed.

01 / THE WORKSPACE

Start with the task that needs to work.

Open a check for the test, evidence and acceptance criteria. Pick the checks you need, then export a starter register. Nothing here inspects your website or marks it passed.

01Say who this is forDirection

A visitor should recognize the audience, problem and next step without decoding the brand language.

Try this

Open the home page and the main service page. Read only the first screen. Write the audience, problem, offer and next action in your own words. Compare that with the owner’s approved description.

Keep this evidence

A screenshot of each first screen, the four answers and owner-approved wording. Record ambiguity rather than assuming conversion loss.

A useful acceptance test

The intended customer can identify a relevant service and a credible next step. An unfamiliar reviewer can explain the offer without a verbal introduction.

Suggested owner content owner

Brief your AI assistant

Review these supplied first-screen captures and the approved offer. Identify unclear audience, problem, offer or next action. Quote the confusing copy; propose a precise revision without inventing claims. Return finding, evidence, owner question and acceptance test. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

02Make the offer inspectableDirection

Price, scope and boundaries prevent the same misunderstanding from returning in every sales call.

Try this

Compare the service page, pricing section, inquiry form and any sales PDF. Note conflicting prices, minimums, inclusions, exclusions or delivery promises. Ask the owner to resolve the conflicts.

Keep this evidence

A side-by-side offer inventory with source URL, review date and approved resolution for each mismatch.

A useful acceptance test

The same offer means the same thing at every entry point; unknown price or timing is described as a quote, not an invented promise.

Suggested owner business owner

Brief your AI assistant

Using only the supplied offer sources, build an inclusions/exclusions/price/timing comparison. Flag contradictions. Do not set a price or promise availability. Draft questions for the owner and a consistency recheck. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

03Give proof its proper contextDirection

A beautiful result is useful proof when people understand what was done, who did it and what is actually known.

Try this

Review case studies, testimonials, logos and outcome claims. For each, identify its source, permission, date, contribution and measurement method where applicable. Mark unsupported statements for review.

Keep this evidence

A claims list linked to source evidence. Keep qualitative design observations separate from measured business outcomes.

A useful acceptance test

Each public claim has an approved source or is clearly described as a concept/observation. Missing evidence is not replaced by a stronger adjective.

Suggested owner content owner

Brief your AI assistant

Audit this supplied proof inventory. Separate measured outcomes, qualitative observations, owner assertions and unsupported claims. Suggest factual wording using available evidence only; list permission or method gaps. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

04Match the label to the next stepDirection

People should know whether a button opens an inquiry, checkout, booking page or download.

Try this

Follow each primary CTA from home and service pages in a local or approved test environment. Compare the label with the next screen. Check back navigation and alternative contact paths.

Keep this evidence

Start URL, visible and accessible label, final URL/screen and expected action. Include a mobile capture.

A useful acceptance test

The label accurately predicts the destination; the destination opens and retains useful context. Any external/new-tab behavior is understandable.

Suggested owner designer

Brief your AI assistant

Given these CTA labels and observed destinations, identify misleading transitions. Propose the smallest label or path fix. Preserve established URLs and describe the mobile, keyboard and back-navigation verification. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

05Read every important stateUsability

Text and controls can become unreadable over images, gradients or disabled/error surfaces.

Try this

Inspect default, hover, keyboard focus, disabled, selected and error states against their actual backgrounds. Use a contrast checker for text and controls; manually inspect layered surfaces and images.

Keep this evidence

Component/state/background matrix with measured colors, screenshots and unresolved cases. State which accessibility target the project uses.

A useful acceptance test

Important information and controls meet the agreed contrast target in each tested state, including errors and focus. Do not infer full accessibility from one automated pass.

Suggested owner designer

Brief your AI assistant

Review this component-state contrast evidence. Group defects by reusable component and real background. Prioritize unreadable instructions, errors and focus. Propose token-level changes and a manual recheck matrix. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

06Keep the keyboard path intactUsability

A task is blocked if focus disappears, becomes trapped or lands somewhere unexpected.

Try this

Use Tab, Shift+Tab, Enter, Space and Escape through navigation, dialogs and the main task. Close each overlay and check focus returns to its opener. Confirm visible focus and a logical order.

Keep this evidence

A task-by-task focus trace, browser/device, expected/actual destination and screenshots of focus visibility.

A useful acceptance test

Every required control is reachable and operable; overlays release focus predictably; the visitor can leave and resume the task.

Suggested owner developer

Brief your AI assistant

Use this keyboard trace to locate the smallest semantic or focus-management defect. Explain expected behavior, propose a focused change and tests for forward/backward order, Escape and focus restoration. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

07Make the small view usableUsability

A scaled desktop screenshot is not evidence that a phone or zoomed browser can complete a task.

Try this

Check 320 CSS-pixel width, portrait and landscape, and actual 200% browser zoom. Open navigation, errors, long labels and disclosures. Check sticky elements do not hide actions. Use a real phone when available.

Keep this evidence

Viewport, device/browser, zoom method, task results and overflow captures. Label emulation separately from physical-device checks.

A useful acceptance test

The key task works without clipped text or hidden controls. Expected scroll regions are usable; unfinished native-device coverage stays named.

Suggested owner designer + developer

Brief your AI assistant

Review these responsive task captures. Find clipping, overlap, tiny targets and sticky obstructions. Propose the smallest shared layout fix. Preserve content and list separate desktop-emulation and native-device tests. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

08Describe the meaning of imagesUsability

Alternative text should explain useful meaning or the action of a linked image, without narrating decoration.

Try this

Review images in their page context. Identify decorative images, informative images, linked images and diagrams. Inspect accessible names and nearby text; use a screen reader where available.

Keep this evidence

Image inventory with role, surrounding context, current alternative, proposed alternative and duplicate-announcement notes.

A useful acceptance test

Useful meaning and linked purpose are available in text; decorative images retain empty alternatives; complex diagrams have a readable explanation.

Suggested owner content owner

Brief your AI assistant

Review this image/context inventory. Classify purpose before suggesting alternatives. Preserve empty decorative alt text; avoid redundant linked-image announcements. Draft concise alternatives and explain which diagrams need nearby long text. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

09Recover from a form errorCritical journeys

Validation is part of the task. A visitor should know what failed and keep the information already entered.

Try this

In a local or mocked environment, test empty, invalid, slow, failed and successful states. Check labels, focus, error summaries, preserved values, loading state and duplicate-send protection. Use synthetic data only.

Keep this evidence

Test fixture, steps, field/state captures, observed result and request count. Separate mocked success from real delivery.

A useful acceptance test

Errors identify an actionable correction; entered data is preserved appropriately; loading prevents accidental duplicate actions; a failed request never claims success.

Suggested owner developer

Brief your AI assistant

Using this form-state matrix, identify blocked recovery and false success. Propose targeted validation/focus/state changes without altering delivery contracts. Include timeout, duplicate and keyboard regression tests with mocked services. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

10Trace the handoff after SendCritical journeys

A provider accepting a message does not prove the intended person received a usable brief.

Try this

Map the intended visitor and internal messages, recipients, Reply-To and attachments. First test locally. If a live test is approved, send once with a unique synthetic marker and verify each actual inbox separately.

Keep this evidence

Approved test manifest, acceptance result, provider response, inbox receipt, Reply-To and attachment hash/content where relevant. Never put credentials or real customer data in shared evidence.

A useful acceptance test

Each required message arrives with correct routing and usable content, or the gap is explicitly reported. No automatic retry after an uncertain result.

Suggested owner developer + operations owner

Brief your AI assistant

Create a single-send delivery test from this supplied routing map. Specify synthetic fields, recipients, expected messages, Reply-To, attachment checks and stop rules. Distinguish provider acceptance from inbox receipt; do not execute or retry anything. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

11Deliver the promised downloadCritical journeys

A download button must lead to a usable file, with a name and contents that match the promise.

Try this

Open every important download in the browser and its intended reader. Inspect filename, type, contents, links, readability and mobile access. Test direct links without submitting unrelated personal details.

Keep this evidence

Download URL, status, filename, byte count/hash, opened-file observation and document version.

A useful acceptance test

Files download and open, match the described contents and have readable structure. Any rights or usage terms are owner-approved, not guessed.

Suggested owner content owner

Brief your AI assistant

Compare these advertised downloads with the supplied actual files. Flag missing sections, stale links and misleading labels. Produce a file-by-file correction plan and opening/readability tests; reserve licensing decisions for the owner. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

12Match the privacy choice to behaviorCritical journeys

The visible explanation and technical behavior must describe the same data flow.

Try this

Inventory forms, analytics, embeds, storage and providers. In an isolated test, inspect requests before choice, after denial, after approval and after withdrawal. Compare actual fields/purposes with the notice.

Keep this evidence

Names-only data-flow map, request categories, consent states and factual wording discrepancies. Keep policy/retention decisions assigned to the owner and qualified reviewer.

A useful acceptance test

The implementation respects the documented choice; private answers are absent from analytics. Any uncertain legal requirement or retention commitment remains a human decision.

Suggested owner developer + policy owner

Brief your AI assistant

Compare this redacted data-flow map, consent request trace and current notice. Identify factual mismatches and personal-data leakage risks. Propose technical tests and factual corrections only; do not invent retention periods or declare legal compliance. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

13Give each page a distinct promiseDiscovery & speed

Titles and descriptions should represent page intent, rather than repeat one generic message everywhere.

Try this

Export current public routes with titles and descriptions. Check missing, duplicate and inaccurate values before reviewing length. Start with shared templates and document deliberate length exceptions.

Keep this evidence

Route inventory, template owner, before/after text and URL-specific reason for exceptions.

A useful acceptance test

Every intended public page has accurate, distinct metadata; shared template changes preserve meaning and reviewed exceptions. Search display is not guaranteed.

Suggested owner content owner

Brief your AI assistant

Review this metadata inventory by page intent and shared template. Prioritize missing, duplicate or misleading content before project length targets. Propose concise differentiated copy and document intentional exceptions by URL. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

14Publish only what should be foundDiscovery & speed

Sitemaps, canonical links and indexing directives should agree with the intended public route set.

Try this

Compare routes, sitemap, canonical, robots and page indexing directives. Keep drafts/private material out of public discovery. Inspect authenticated Search Console data only if access is authorized.

Keep this evidence

Intended-route inventory and observed directives/status; distinguish eligibility, crawl, index status and ranking.

A useful acceptance test

Discovery files consistently describe intended public pages. Private content has actual access control. Eligible does not mean indexed or ranked.

Suggested owner developer

Brief your AI assistant

Compare this route/directive inventory with the approved public scope. Identify contradictory canonicals, unintended indexable drafts and sitemap omissions. Suggest the smallest correction; do not treat robots rules as access control. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

15Close the broken-link graphDiscovery & speed

A correct homepage can still send visitors to a missing fragment, old asset or external redirect loop.

Try this

Check internal routes, hydrated fragment targets, downloads and important external destinations. Follow redirects with a bounded checker; manually exercise priority booking/contact links without completing the action.

Keep this evidence

Source URL/link text, destination/final URL, status, fragment result and manual task observation. Record external timeouts as uncertain, not automatically broken.

A useful acceptance test

Priority links reach their intended page or target; preserved old URLs still resolve; uncertainty is separated from confirmed failures.

Suggested owner developer

Brief your AI assistant

Group this link-check output by root cause. Separate missing route, missing fragment, bad asset, redirect issue and uncertain external timeout. Propose minimal fixes preserving established URLs, then give exact link-level retests. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

16Fix a measured loading delayDiscovery & speed

A speed change needs a reproducible cause and a matched comparison, not just a greener score.

Try this

Record the main content element and loading trace. Run matched mobile lab measurements with the same build, device and network. Test one plausible cause with a small bounded before/after set. Inspect field data separately if available.

Keep this evidence

Build, device/network, run values, main element, trace, change and comparison. Record missing or insufficient field data honestly.

A useful acceptance test

A shipped speed change shows repeatable benefit without degrading visual or task behavior. Lab results are not real-user metrics.

Suggested owner developer

Brief your AI assistant

Analyze these matched traces and measurements. Identify the strongest supported bottleneck, one minimal experiment and a bounded retest. Distinguish field from lab evidence and reject a change if the result is noisy or regressive. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

17Keep machine-readable claims honestRelease & ownership

Structured data must match what people can see and what the business can support.

Try this

Compare JSON-LD, social cards and machine-readable summaries with visible pages and approved facts. Check types, canonical URLs, identity and unsupported review/rating/FAQ claims.

Keep this evidence

Parsed output, visible supporting section, validator result and source for each proof-sensitive property.

A useful acceptance test

Structured claims match visible/source-backed content; no invented authority, ratings or unavailable services. Validation alone does not promise enhanced search display.

Suggested owner developer + content owner

Brief your AI assistant

Audit this structured-data output against visible content and approved facts. Flag unsupported properties, identity mistakes and canonical drift. Suggest minimal corrections with field-to-source mapping, without adding speculative search features. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

18Test the exact release candidateRelease & ownership

Passing a local build does not prove the reviewed Preview or live domain works.

Try this

Record the full commit and target environment. Reuse a Ready deployment of that exact source and unchanged build inputs. Verify its affected tasks; for Production also confirm the live domain points to it.

Keep this evidence

Commit, environment, deployment ID/URL, CI results, domain assignment and observed task checks. Block analytics and unapproved mutations during smoke checks.

A useful acceptance test

Exact-head checks pass, the actual deployed flow works and any untested gate is explicit. A verification request alone never authorizes a rebuild or release.

Suggested owner release owner

Brief your AI assistant

Prepare a release gate matrix from these commit, CI and deployment records. Identify exact-head mismatches and missing runtime checks. Reuse matching deployments, specify safe smoke tests and do not infer deployment authorization. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

19Name the way backRelease & ownership

Rollback is useful only when someone knows the target, trigger, authority and consequences.

Try this

Identify the last working deployment/source and confirm availability. List rollback triggers, operator, command/mechanism and post-rollback checks. Review data/schema compatibility if the change touches them.

Keep this evidence

Named rollback reference, verified availability, required approval, expected effects and smoke plan. Never execute as an unapproved practice drill.

A useful acceptance test

A responsible operator can explain and execute the approved recovery path. Irreversible effects and remaining risk are acknowledged before release.

Suggested owner release owner

Brief your AI assistant

Using this change and environment map, draft a concrete rollback plan. Name the known-good source/deployment, triggers, operator approval, data compatibility and verification. Do not execute or imply a database rollback is safe without evidence. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

20Leave a usable next actionRelease & ownership

A handoff should distinguish what is complete from what merely stopped receiving attention.

Try this

Review every finding with an owner. Mark verified, failed, deferred, not tested or not applicable with a reason. Record support ownership, access transfer and the next review trigger without sharing secrets.

Keep this evidence

Dated decision register, client summary, remaining gaps, owners, acceptance/approval and safe credential-transfer instructions.

A useful acceptance test

Every open item has an owner and next decision. The receipt states tested scope and limitations; no unresolved item silently becomes a pass.

Suggested owner project owner

Brief your AI assistant

Turn this evidence register into a concise client handoff. Separate verified work, failures, deferred decisions and untested coverage. Give each open item an owner and trigger. Do not claim delivery, accessibility or revenue outcomes beyond evidence. Start with read-only review of supplied evidence. Mark unknowns and use synthetic data for tests. Do not fix, submit, change providers, commit, push or deploy beyond the explicitly approved scope. Never invent results.

02 / A WORKED FINDING

From “that’s odd” to “here’s the next step.”

Juniper Cycle Repair is fictional. This written example shows the process, not real client evidence or a verified result. Follow JCR-04 through the five stages.

Open

Record the friction. Don’t invent its cost.

In the fictional Juniper Cycle Repair site, the service page says “Book a repair.” The next screen is an email inquiry with no calendar. The label promises an action the destination does not provide.

THE EVIDENCE TRAIL

Sample observation: /repairs → /contact, 390px viewport. This is a written demonstration, not a tested live business.


Next decision
Open · confirm the intended booking process with the owner.

Finding JCR-04 · check 04 · owner: designer

Needs decision

Useful context beats an impressive score.

The mismatch sits on the main inquiry path. Treat it as a priority task-clarity issue, while an actually broken send action would come first. Do not claim lost revenue from a label alone.

THE EVIDENCE TRAIL

Impact: expectation mismatch. Reach: main service entry. Confidence: direct route observation. Effort: small copy change after owner confirmation.


Next decision
Next · owner confirms whether the flow should stay an inquiry.

Register: P1 / evidence confidence: observed

Ready to verify

Change the cause, not the whole website.

If the owner confirms an inquiry-first workflow, rename the action “Ask about a repair” and explain that the team will reply. Preserve the destination. Do not promise a response time that is not established.

THE EVIDENCE TRAIL

Illustrative patch only: CTA label + one sentence beside the form. No production edit or real message is performed by this kit.


Next decision
Candidate · implementation still needs review and testing.

Scope: copy, accessible name, related confirmation wording

Not tested

A plausible fix is still an unverified fix.

Recheck the visible and accessible label, final destination, mobile wrapping and keyboard path. A separate approved delivery test is needed to establish actual inbox receipt; a local form mock does not prove it.

THE EVIDENCE TRAIL

Required: before/after capture, browser/device, commit, task result and reviewer. This sample has no real runtime test attached.


Next decision
Not tested · the sample must not be marked passed.

Acceptance: label predicts inquiry, task remains usable

Open

End with an owner, not a vague thumbs-up.

The client summary explains the observation, approved direction and remaining delivery check. A release receipt names the exact source/deployment only after release is approved and checked.

THE EVIDENCE TRAIL

Sample next owner: project lead. Remaining gap: approved workflow decision and real delivery evidence. No fake screenshot or completed status is supplied.


Next decision
Open · owner decision and verification required before release.

Client report + evidence log + handoff record

Ready to verify is not verified. A failed test stays failed. A human decision stays open. A handoff names both.

03 / THE DELIVERABLES

Take the working files. Leave the busywork.

Seven editable documents, connected by check ID. Open the CSV files in a spreadsheet and the Markdown in any text editor. Start with the quick guide, then make the workflow your own.

The complete preview bundle

All seven files in one ZIP. No purchase or signup. Resource terms apply.

Download the complete kit

04 / CHOOSE YOUR NEXT STEP

Learn it. Work through it. Get a hand.

The guides explain what to look for. The kit connects the observations to the work. Direct help is there when you want someone involved in the change.

FREE / THE KNOWLEDGE

Learn what to look for.

  • Journal guides and launch checklist
  • Tools and Design Blueprint exports
  • Public explanations and practical prompts
Read the free launch guide

KIT / PUBLIC PREVIEW

Connect the work and the handoff.

  • Checks linked to tests, evidence and owners
  • Editable scope, report and release documents
  • One worked finding and a consistent status language
See the workflow in action

DIRECT HELP / EXISTING SERVICE

Work through it together.

Need someone to help shape, design and build the change? The service offer remains separate from this kit.

Explore working together

BEFORE YOU DOWNLOAD

A few useful answers.

Does this run an audit for me?

No. It provides a structured manual process, tests and reusable documents. The page never scans a website. You supply observations and verify each finding in the right environment.

Is the sample a real client result?

No. Juniper Cycle Repair is fictional. Its finding is a written demonstration with open decisions and untested behavior, not a success story.

Can I buy the kit now?

This is a usable public preview, available without purchase. There is no paid edition or checkout here. Download the files and review the resource terms before using them.

What does it not cover?

It is not a specialist legal, security or full accessibility review, an ecommerce payment test plan, or a performance guarantee. Adapt the scope to the site and involve the right specialists for those decisions.

What happens to my selections?

Selections are held only in this page’s memory and reset on reload. They are not submitted or included in analytics. Export before leaving; the file contains template checks, not personal answers. The website’s optional measurement follows your privacy and cookie choices.

MAKE THE NEXT STEP EASIER TO EXPLAIN

Pick one finding.
Give it a useful ending.