Files
AndreaSlopFotografie/aidlc-docs/features/frontend-shell/construction/build-and-test/manual-test-instructions.md
T
SluijsensandClaude Opus 5.5 069c7cb7eb Adds AI-DLC construction docs for the front-end shell feature
Functional design, NFR requirements, code generation plan and summary,
and build-and-test instructions with results.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-18 17:05:03 +02:00

45 lines
2.8 KiB
Markdown

# Manual Test Instructions — frontend-shell
The automated tests cover structure, roles and labels (Testing Library + axe) and Lighthouse covers contrast. What they cannot judge is how the site **feels** with a keyboard and a real screen reader (NFR-A-04). Run this checklist on the built site.
## Setup
```bash
pnpm build && pnpm preview # http://localhost:4173
```
- **Screen reader**: NVDA (Windows, free) with Chrome, or VoiceOver (macOS/iOS) with Safari.
- **Phone**: open `http://<your-PC-IP>:4173`. For that, run `pnpm preview --host`.
## Keyboard (no mouse)
| # | Step | Expected |
|---|---|---|
| K1 | Load `/`, press Tab once | "Direct naar de inhoud" appears top left |
| K2 | Press Enter | Focus jumps to the content; the next Tab goes to the first link in the page |
| K3 | Tab through the header | Logo, then the menu items, each with a clearly visible focus ring |
| K4 | Below 1024 px: Tab to the menu button, Enter, Escape | Menu opens; Escape closes it; the page does not scroll behind it |
| K5 | Open a page from the menu | Page starts at the top; focus is in the content (next Tab = first link in the page) |
| K6 | Browser back | Previous page at the previous scroll position |
| K7 | Scroll down, Tab to "Terug naar boven", Enter | Page scrolls up; the button disappears; focus is in the content |
| K8 | At the top of the page, Tab | "Terug naar boven" is skipped while invisible |
| K9 | Footer links | Visible focus; Facebook/Instagram open in a new tab |
## Screen reader
| # | Step | Expected |
|---|---|---|
| S1 | List landmarks (NVDA: D / VoiceOver: rotor) | Banner, "Hoofdmenu" navigation, main, content info, "Footermenu" navigation |
| S2 | List headings (NVDA: H) | One heading level 1 per page; "Socials" and "Contact" at level 2 |
| S3 | Footer social link | "Facebook, opent in nieuw tabblad, link" (wording differs per reader) |
| S4 | Follow a menu link | The new page is read from the start of the content |
| S5 | Unknown URL `/bestaat-niet` | "Pagina niet gevonden" is read; header and footer present |
| S6 | Hero arrows and social icons | "Vorige foto", "Volgende foto", "Instagram, opent in nieuw tabblad" |
## Visual / responsive
| # | Step | Expected |
|---|---|---|
| V1 | Widths 320, 390, 820, 1440 and ultrawide (DevTools device toolbar) | No horizontal scrolling, nothing cut off |
| V2 | Footer brand column | Mobile: logo and tagline centred, stacked. Tablet and desktop: logo with the tagline beside it |
| V3 | 32:9 screen | "Terug naar boven" aligns with the content edge, not the screen corner |
| V4 | Browser zoom 200% | Everything readable, nothing overlaps |
| V5 | OS "reduce motion" on | No smooth scrolling or slide/fade animations on the to-top button |
Record findings with page, step and browser/reader, and report them as a bug (Bug Fix lane) or a change request.