Browser and integration acceptance checklist

Run this in an authorized development environment after extracting the package. This checklist is for later acceptance; its items are not completed merely because they are listed here. Keep results with browser version, operating system, URL or file path, viewport/zoom, observation, and any fix.

1 Open and navigate the course reader

  1. Open index.html, learner-guide.html, modules 00–09, each practice/solutions page, all assessments/answers, capstone pages, sources, and this QA section.
  2. At 320 CSS pixels, check the reader’s full page width and module 02’s long heading “Connect pages and make media understandable.” Headings should wrap and no essential prose should require sideways page scrolling. Code blocks may scroll within their own boxes.
  3. Check every diagram and its adjacent explanation. Confirm nothing is clipped and text alternatives remain available. Do not count repeated garden copies as distinct diagrams.
  4. Tab through reader navigation, check focus visibility, and verify previous/next links go to the intended module.

2 Open progressive site versions

  1. Open versions 00–03 and confirm expected unstyled progression. Version 00 should have one heading and one paragraph; later versions add semantics, image/navigation, then the practice form.
  2. Open versions 04–07 and confirm each CSS stage loads. Version 07 intentionally remains a one-column grid.
  3. Open versions/09 and capstone/reference at 320, 768, and 1280 CSS pixels, plus one intermediate width. Inspect the whole page for horizontal overflow, clipped controls, and unreadable text. Confirm the hero/cards adapt and header links remain available.
  4. Test 200% browser zoom and a 400% narrow-equivalent check where practical. Test a larger default text size independently. Insert a long title in a disposable copy and repeat.

3 Verify keyboard and form behavior

  1. From the top, use Tab to reach the skip link. Activate it and verify main content is reached. Continue through all navigation and event links in sensible order.
  2. Open and close the break-area disclosure by keyboard. Confirm focus remains visible and no content is trapped.
  3. Try submitting empty fields, an invalid invented email, and then Alex Example / alex@example.com. Record browser-specific validation feedback without expecting identical wording.
  4. With valid invented values, confirm the local result page appears and its URL contains none of the entered name, email, category, or question. Read the result: it must not claim a registration. Inspect a network request if using HTTP to confirm no named field values are present.
  5. Try a screen reader: headings/landmarks should be useful, the form’s labels/hints should be announced, and the disclosure state should be understandable. Record the screen reader and browser used.

4 Check media and alternate formats

  1. Play the optional two-tone audio only if appropriate. Confirm native controls work and the text alternative conveys its complete information without listening.
  2. Check contrast for actual rendered states, including focus on light backgrounds and the dark button. Use a suitable contrast tool; do not rely only on visual impression.
  3. Inspect print preview for the reference site and a long lesson. Check that content is not cut off and code remains readable.
  4. Repeat core checks in a second browser engine and on a physical small-screen device when available. Mark unavailable combinations explicitly.

5 Integrate without inventing completion

  1. Use a preview/staging location authorized for the website. Preserve relative assets and lesson ordering. Avoid importing the reader stylesheet globally into an unrelated existing site.
  2. Map course navigation and downloads to the destination platform, keeping practice and solutions separate. Confirm that embedded code remains selectable and not interpreted as live markup.
  3. Recheck all links after integration under the actual subdirectory path. Test a fresh browser session and verify the course is not accidentally public before approval.
  4. Run a small beginner pilot. Ask a learner to reach module 03 and module 07 from written instructions without silent instructor repair. Record blockers and actual timing before publishing duration claims.
  5. Only mark acceptance complete when the evidence supports it. A successful file upload is not browser, accessibility, or learner acceptance.