WCAG 2.4.1 Bypass Blocks: what it means and how to fix it
Short answer: Give keyboard and screen reader users a way to skip repeated navigation, usually a "Skip to content" link plus proper page landmarks.
What it requires
There must be a mechanism to bypass blocks of content that repeat on multiple pages, such as the header and navigation menu. A visible-on-focus skip link, headings, and landmark regions (header, nav, main, footer) all help.
Who it affects
Keyboard users, who otherwise have to Tab through dozens of menu links on every page, and screen reader users, who jump by landmarks.
How it shows up in ADA website claims
Complaints describe having to listen to or tab through the entire navigation menu on every page before reaching products.
How to check your site
- Load a page and press Tab once. A "Skip to content" link should appear.
- Press Enter. Focus should move to the main content.
- Check that the page has one
mainlandmark.
How to fix it
<body>
<a class="skip" href="#main">Skip to content</a>
<header>...<nav>...</nav></header>
<main id="main" tabindex="-1">...</main>
<footer>...</footer>
</body>
.skip { position: absolute; left: -9999px; }
.skip:focus { left: 1rem; top: 1rem; z-index: 999; background: #fff; padding: .5rem 1rem; }
Frequently asked questions
Do I need a skip link if I have landmarks?
Landmarks technically satisfy 2.4.1 for screen reader users, but sighted keyboard users cannot use landmarks without extra software. A skip link covers both.
Should the skip link always be visible?
It can stay hidden until it receives keyboard focus. It must not be permanently hidden with display: none.
Does a one-page site need this?
If there is a repeated block before the main content, yes. It takes two minutes to add.
Automated rules that test this (axe-core): bypass, region, landmark-one-main. Our scanner runs these checks.
Other commonly cited criteria
- 1.1.1 Non-text Content
- 1.2.2 Captions (Prerecorded)
- 1.3.1 Info and Relationships
- 1.4.3 Contrast (Minimum)
- 1.4.4 Resize Text
- 2.1.1 Keyboard
- 2.4.2 Page Titled
- 2.4.4 Link Purpose (In Context)
- 2.4.7 Focus Visible
- 3.1.1 Language of Page
- 3.3.2 Labels or Instructions
- 4.1.2 Name, Role, Value
Read the official WCAG 2.1 specification at W3C.
Proof of Access provides technical accessibility assessments. We are not a law firm and nothing on this page is legal advice. If you have received a demand letter or a lawsuit, talk to an attorney.