# First accessibility review: fictional worked example

This is an invented demonstration, not an evaluation of a real website or a record of completed client work. Every observation, change and retest below is fictional. A closed sample issue does not establish WCAG conformance or legal compliance.

## Review scope

- Site: fictional Sample Workshop website, `https://example.com/`.
- Review date: October 8, 2026.
- Reviewer: sample reviewer role.
- Pages: `/`, `/workshops`, `/contact`.
- Tasks: open navigation, find a workshop, read the details, complete an inquiry in an isolated test form with fictional data.
- States included: navigation closed/open, form empty/error/success.
- Illustrative environment: Windows desktop, Chromium-based browser, 100%, 200% and 400% browser zoom. A 1280 CSS-pixel content viewport at 100% provides an equivalent 320 CSS-pixel width at 400%; a separate responsive preview uses a measured 390 by 844 CSS-pixel viewport at 100%.
- Actual review records should include the browser name/version, operating-system version, keyboard settings, test date and the measured viewport. These illustrative environment notes are not test evidence.
- Checks represented: keyboard access and visible focus; enlarged text and narrow layouts; title/headings; solid text contrast; image alternatives; visible form labels and error handling.
- Not checked: screen-reader output, other assistive technology, real phone behavior, video, third-party booking, every page or state, and the complete WCAG criteria.
- Test safety: inquiry form is a fictional isolated fixture. On a real site, agree the test and confirm how messages, bookings or payments are prevented before submitting.

The records below show how to write two findings. They do not imply that every other check passed. Keep a separate page/check coverage record for a real review.

## A11Y-001 — Menu trigger cannot be reached by keyboard

- Page URL: `https://example.com/workshops`.
- Page state: small-screen navigation closed.
- Check area: keyboard operation.
- Environment: fictional desktop browser review, responsive preview 390 by 844 CSS pixels, 100% zoom; keyboard navigation enabled for controls.
- Steps to reproduce:
  1. Load the page at the recorded width and close the navigation if open.
  2. Use Tab from the start of the page through the header.
  3. Observe that focus moves from the logo link to the content and never reaches the visible menu trigger.
  4. Try to open the menu without a pointer.
- Expected behavior: the menu trigger can receive keyboard focus and be operated; its state and menu content are available to users.
- Observed behavior: the trigger is skipped and the navigation cannot be opened with the keyboard.
- User impact: a keyboard user cannot reach the navigation options through this menu.
- Evidence reference: `A11Y-001-keyboard-notes` — fictional identifier only; no recording is included.
- Priority: blocks a visitor task. This is a work priority, not a WCAG conformance level.
- Owner: site maintainer role.
- Status: Open.
- Target date: to be agreed with the owner.
- Next action: inspect the trigger's semantics and keyboard behavior; implement and test the appropriate button/menu behavior.
- Change reference: none yet.
- Retest date: Not checked.
- Retest result: Not checked.
- Remaining action: test opening, focus visibility/order, keyboard access inside the menu, closing and useful focus return after a proposed fix; check the same shared menu on other pages.

## A11Y-002 — Ordinary text contrast below the AA threshold

- Page URL: `https://example.com/contact`.
- Page state: introductory paragraph before form entry.
- Check area: text contrast.
- Environment: fictional style inspection; opaque solid sRGB foreground and background; ordinary 16 CSS-pixel regular text.
- Viewport and zoom: 1280 by 800 CSS pixels, 100% zoom. The same text style appears at the narrower layouts.
- Steps to reproduce:
  1. Inspect the paragraph's actual foreground and background colors in the page styles.
  2. Enter foreground `#777777` and background `#FFFFFF` in Plainview's Color Contrast Checker.
  3. Read the normal-text AA result, then check the actual page state.
- Expected behavior: ordinary text has at least 4.5:1 contrast under WCAG's AA text criterion.
- Observed behavior: this pair has approximately 4.478:1 contrast, below 4.5:1. Rounding it to one decimal must not turn it into a passing result.
- User impact: the paragraph can be difficult to read for someone with reduced contrast sensitivity.
- Evidence reference: `A11Y-002-color-values` — fictional record identifier; the numeric ratios can be independently calculated from the colors.
- Priority: makes reading harder. This is a work priority, not a WCAG level.
- Owner: designer and site maintainer roles.
- Fictional change reference: `sample-change-002`, changed this text style to `#595959` on `#FFFFFF`.
- Fictional retest date: October 8, 2026.
- Fictional retest result: the intended solid pair is approximately 7.005:1; ordinary-text AA passes. The illustrative reviewer checks that the corrected pair is used by this paragraph in the recorded layouts, with no opacity or background image changing it.
- Status: Closed for this specific contrast issue only.
- Remaining action: inspect other text and interactive states separately; this check did not assess every page, transparency, gradients or photographic backgrounds.

## Review summary

- Demonstration findings recorded: 2.
- Open findings: 1, the keyboard menu barrier.
- Closed findings after an illustrative retest: 1, the specified ordinary-text contrast pair.
- Broader review: still incomplete; the Not checked items above remain untested.
- Next step: assign a date for the menu correction, repeat its steps after the change, and arrange the remaining review work.

## Using the blank CSV issue log

The companion CSV has these columns:

`issue_id`, `page_url`, `page_state`, `check_area`, `environment`, `viewport_css_px`, `zoom_percent`, `steps_to_reproduce`, `expected_behavior`, `observed_behavior`, `user_impact`, `evidence_reference`, `priority`, `owner`, `status`, `target_date`, `change_reference`, `retest_date`, `retest_result`, `remaining_action`.

It contains one unfilled row whose status is Not checked. Replace or duplicate that row for real findings. Keep an independent list of pages/checks attempted: no rows does not mean no barriers exist.

Suggested workflow statuses are Open, In progress, Ready for retest and Closed. Keep Not checked for missing review/retest evidence. Enter one issue per row and number reproduction steps within the cell. Use a stable issue ID so a screenshot or correction can be traced back to it. Record dates consistently, for example YYYY-MM-DD, when a real date is known.

Do not include passwords, tokens, payment details or personal form submissions. Store evidence in an appropriate shared location and link to a sanitized reference. When opening any CSV containing user-supplied text, import it as text and review spreadsheet formula handling; this blank template contains no formulas.

## Reference links

- [First website accessibility review](https://plainviewweb.com/guides/first-website-accessibility-review)
- [W3C: Easy Checks](https://www.w3.org/WAI/test-evaluate/preliminary/)
- [W3C: Keyboard](https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html)
- [W3C: Contrast (Minimum)](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html)
- [Plainview Color Contrast Checker](https://plainviewweb.com/tools/color-contrast-checker)