For a business buying a catalogue or customer portal, ask the supplier to demonstrate the second page visit with a keyboard. A reader should not have to traverse the same long header before reaching every new task. The deliverable is an actual route past the repeated block, with a sensible next focus position.
Primary evidence and claim boundaries
WCAG 2.4.1 requires a mechanism to bypass repeated blocks. WAI lists skip links, landmarks and headings among techniques; one particular visual design is not mandated. Primary reference · Read 18 October 2026.
Filled acceptance example
Original synthetic teaching scenario, not a client case, provider integration test or business result. The example policy needs the actual owner’s approval; scroll the table on narrow screens.
| Input and state | Declared check | Expected output and decision |
|---|---|---|
| Catalogue page2: header has18links | First Tab reveals “Skip to catalogue” | Enter reaches results; next Tab reaches first product link |
| Skip target renamed from main to results | Link still points to#main | Reject: target missing; visible link alone is insufficient |
| Skip target behind a fixed bar | Focus moves but title is obscured | Record visibility failure, not keyboard success |
| Direct visit to page3 | Same bypass mechanism and destination role | Repeat path; do not infer from page2 |
Practical handover procedure
- Give the supplier two representative pages with different task content and the same repeated header. Write the intended destination and next interactive control for each.
- Start from a fresh visit, use Tab and Enter without the pointer, and record the revealed link, destination visibility and next focus stop.
- Repeat with magnification and the actual supported assistive technology. Retain failures after route or header changes rather than hiding them in an aggregate score.
Interpret the outcome
The first row defines a complete shortcut, not merely an anchor in the source. The broken-target row makes the check falsifiable. A landmark may be useful to a screen-reader user while a visible-on-focus skip link helps sequential keyboard navigation; assess the supported journey instead of requiring redundant controls everywhere.
Acceptance decision
Accept after the repeated block can be bypassed on both supplied pages and focus continues into the intended task. Do not label a static manifest a keyboard or screen-reader test.
Limits and unverified work
Original synthetic acceptance paths, not an audit of MadRaven’s frozen navigation or a full WCAG conformance report. No old page is changed.
Download the filled bilingual acceptance record — Contains the inputs, steps, expectations and limits. This is a teaching record, not an executable production integration.