Links and navigation
bypass
WCAG 2.4.1 Bypass Blocks Level A
Who this affects
A keyboard user has to tab through the whole navigation on every page before reaching the content.
How to fix it
Add a skip link as the first focusable element, pointing at the main content, and make sure it becomes visible on focus.
How much work is it?
Usually a template or design change. That is a rough guide for planning, not an estimate for your codebase. A single content edit repeated across a template is a template change.
What a person still has to check
Passing this rule does not mean 2.4.1 passes. Automation checks part of the criterion, and the rest is a judgement:
Tab from the top of the page and confirm the skip link appears, takes focus, and works.
Read 2.4.1 Bypass Blocks in plain language
Where this check comes from
This is an axe-core rule. We run axe in a real browser on every page we scan. Deque’s reference for bypass
Find out whether your site does this
A scan checks this rule on every page it visits, and shows you the code and a screenshot of each place it fires.