This is a triage pass, not an audit. Work from what a visitor can observe, preserve the evidence, and choose one next action rather than collecting an unranked list of irritations.

Finish with

Outcome

A one-page review record with five observations, one priority, an owner, and a next action that another maintainer can understand.

What you need

  • The public site address and a private browser window.
  • A fifteen-minute timer and a worksheet or plain document.
  • A keyboard with a Tab key and permission to inspect, but not necessarily edit, the site.
  • A person or role that can receive questions about uncertain facts.

The observable problem

A polished page can still hide a wrong date, an unclear purpose, a broken primary action, or a control that cannot be reached from a keyboard. Those problems differ in consequence, so recording them in the same concrete format matters.

Separate three things in every note. The observation is what happened, such as “Tab moved from the logo to the footer.” The interpretation is what that may mean, such as “the menu might not be keyboard reachable.” The recommendation is what someone should do next, such as “ask the developer to inspect the menu button.”

Invented for instruction

Fictional worked example

Fictional worked example: Northbank Neighbours is an invented community group. Its homepage says “Building brighter tomorrows,” promotes a spring meal dated last year, uses “Learn more” for three different destinations, and has a menu that does not receive visible keyboard focus.

The reviewer records the event date as an incorrect public fact and the menu behavior as a blocked route. The completed worksheet row reads: URL, /events/spring-meal/; observation, page announces 12 April last year as upcoming; evidence, visible heading and booking paragraph; consequence, visitor may plan around an expired event; owner, events coordinator; next action, confirm whether to archive or replace the page.

The reviewer chooses the stale event as the immediate priority because it is demonstrably wrong. The keyboard issue is also logged for prompt technical investigation. The slogan is useful follow-up work, but it does not outrank an incorrect event or blocked navigation.

Procedure

  1. Minutes 0 to 3: identify the purpose

    Open the homepage privately and ignore what you already know. Using only the first screen, write one sentence that identifies the organization or resource, the intended reader, and the main offering. If you cannot, quote the words that caused uncertainty instead of writing “unclear.”

  2. Minutes 3 to 6: inspect facts that expire

    Scan the homepage and one task page for dates, hours, prices, names, locations, contact details, policies, event states, and words such as current or new. Record the visible evidence and mark unknown facts for an owner. Do not silently correct from memory.

  3. Minutes 6 to 9: test labels and destinations

    Read primary links before opening them. Follow at least one important route and compare its label with the destination title and content. Record broken links, repeated vague labels, unexpected downloads, and labels that promise more than the destination provides.

  4. Minutes 9 to 12: use only the keyboard

    Return to the page top, put the mouse aside, and press Tab through the primary route. Note whether focus is visible, follows a sensible sequence, reaches every control, and can leave menus or dialogs. Stop if an action would submit or delete data.

  5. Minutes 12 to 15: request a missing path and rank

    Add a clearly invented path to the site address. Record the message, useful recovery choices, and response status if you know how to inspect it. Then rank all observations by factual harm, blocked primary tasks, and uncertainty. Assign one owner and next action.

Reusable worksheet

Reusable 15-minute review record. Copy the blank row for each observation.
URLObservationEvidencePossible consequenceOwnerNext action
/events/spring-meal/Upcoming event shows a date from last yearHeading and booking paragraphVisitor may rely on expired informationEvents coordinatorConfirm archive or replacement
BlankWrite only what happenedQuote text or name the interactionState a plausible effect without certaintyName a roleUse one verifiable action

Decision rules

  • If a public fact is demonstrably incorrect, fix or withdraw it before polishing the surrounding wording.
  • If the primary task is blocked, prioritize restoring that path before correcting a cosmetic inconsistency.
  • If ownership, policy, or accuracy is uncertain, assign verification and escalate rather than guessing.
  • If an observation cannot be reproduced, record the browser, path, and steps, then seek a second check before prescribing a fix.

Limitations and escalation

  • Fifteen minutes cannot provide a complete content inventory, screen-reader evaluation, contrast assessment, form-error review, security review, privacy analysis, or legal conclusion.
  • Private browsing does not recreate every visitor context. Authentication, personalization, regional variation, cached pages, and assistive technology can change the experience.
  • A missing-path check shows one deployed behavior at one moment. Hosting rules and application routing still need technical verification.

Review list

Check the work

  • Five timed passes are complete and each note separates observation from interpretation.
  • The record includes a URL, evidence, possible consequence, owner, and next action.
  • An incorrect fact and a blocked primary task were considered before cosmetic work.
  • Uncertain claims were assigned for verification rather than silently resolved.
  • One priority is explicit and the limits of this short review are recorded.

Review again when

  • A major navigation change
  • A new form or primary task
  • A hosting or routing change
  • A public report of a barrier
  • A change to time-sensitive information