Aim: identify what headline, breadcrumb, menu, link and heading do for navigation; a mockup is not a tested website. Prepare: Card E in text or large print; optional keyboard to use its actual anchor. Codes: AC9E4LA05, AC9E4LY05, AC9E4LY04.
- Retrieve · 2 min. Ask where Card A puts its limit. Key: second heading; show how a heading helps find it.
- Model · 5 min. Read Card E aloud exactly as a linear screen reader might: breadcrumb, headline, menu label, main heading, body, question heading. Say what each offers: place, page topic, options, section topic, jump. Follow the Jump to questions link in the Markdown view if available, then show the text-equivalent route on paper. A drawn arrow is not automatically a working link.
- Guide · 6 min. Ask: “Where would you look for what the drawing cannot tell?” Key: question heading or jump link. “Where would you look for labelled features?” Key: Plan details menu or main heading. Ask why “Plan details ▾” needs an accessible label when implemented. Do not claim the mockup is a conformant live site.
- Choose · 7 min. Day 12 learner route: organise a mini page in one of three domains and explain two navigation decisions. On paper, the child can point to verbalised links; online use is optional.
- Exit · 3 min. Offer two readers: one wants the page location, one wants a section. Key: breadcrumb for location; heading/jump for section. If a learner confuses a menu with a source fact, separate navigation from content.
- Record · 2 min. Record whether the child found information by hearing, seeing, touching or using a link; record independent reading separately.