Rules · bypass
Failure reference
No way to skip repeated blocks.
Keyboard users tab through the full navigation on every single page unless a skip link or landmark structure lets them bypass it.
What fails — and who it fails
The failure, in plain language.
Fifty tab-stops of header before the content, on every page view. A skip link is one line; landmarks come almost free with semantic markup.
Detection — what the machine can and cannot judge
How the scanner finds it.
- Pages are checked for a skip mechanism: a skip link, or main/nav landmarks that assistive tech can jump between.
- What automation cannot judge: whether the skip link is visible on focus and lands somewhere useful — the journey extension records that.
The legal reading — factual, not fearful
Where this sits in enforcement.
A structural Level A criterion assessors test in the first minute: press Tab, watch what happens. Cheap to fix, prominent when absent.
The fix — by pattern
The pattern that clears it.
+ <a class="skip" href="#main">Zum Inhalt springen</a>
…
<main id="main">Fix the template, not the page — one change typically clears every instance at once. The triage engine groups findings by template pattern for exactly that reason.
Verification — resolution is evidence, not a checkbox
Fixed means a scan said so.
On monitored domains, mark the finding fixed and the next scan verifies it: zero remaining instances converts the finding to Resolved, and both the claim and the confirmation land in the append-only ledger. Criteria that need human judgement close through sign-off in the coverage matrix — covered by the right method, never by assumption.
See where your templates stand.
A complimentary assessment renders up to 25 public pages in an EU-hosted browser and shows every instance of this failure — grouped, ranked, and honest about what still needs a human.