2.4.1 Bypass Blocks
- Level A
- Operable
- Since WCAG 2.0
Summary
Every page on a typical site opens with the same header, the same navigation, sometimes the same cookie banner and search bar, before the unique content begins. A mouse user glides past all of it. A keyboard-only user must Tab through every one of those links, on every single page: forty presses to reach the first paragraph, then forty more on the next page. This criterion protects keyboard users, switch users, and screen reader users from that repeated toll by requiring at least one mechanism to jump past the repeated blocks: a skip link, landmark regions, a sound heading structure, or some combination.
The auditor's mental model is a two-part question. First, does any bypass mechanism exist on the page? Second, does it actually work for the people who need it? A skip link that cannot receive focus, or that scrolls the viewport without moving focus, is decoration, not a mechanism. And a mechanism that only assistive technology can operate leaves sighted keyboard-only users behind, which is where most of the honest grading judgement in this criterion lives.
Official wording
A mechanism is available to bypass blocks of content that are repeated on multiple web pages.
EN 301 549 mapping
- Web pages
- Clause 9.2.4.1
- Software and native apps
- No software requirement: the corresponding chapter 11 clause is void in the standard.
Clause 9.2.4.1 applies this criterion to web pages unchanged. For software the standard declares the corresponding clause void, so native apps carry no mandatory equivalent: the requirement is written for sets of web pages, and equivalent sets of software programs are extremely rare.
Clause references are to EN 301 549 V3.2.1 (2021-03), the harmonised European standard. Descriptions are our own summary, not the text of the standard.
In practice
Web
Load the page fresh and press Tab once. The best implementations reveal a "Skip to main content" link as the first focusable element. It is fine for the link to be visually hidden until it receives focus, but it must then appear on screen (invisible-on-focus skip links fail: a sighted keyboard user cannot activate what they cannot see). Activate it and press Tab again: focus must now land on the first interactive element inside the main content, not back at the top of the navigation. Watch for the classic broken pattern where the link's anchor scrolls the page but focus never moves, usually because the target element is not focusable and lacks tabindex="-1". Also check the anchor still exists; skip links pointing at removed IDs silently do nothing.
Next, check the structural mechanisms in the browser's accessibility tree (devtools accessibility panel): are there header, nav, and main landmarks, and a heading at the start of the main content? With a screen reader running, confirm you can jump by landmark or by heading directly to the content. W3C accepts heading structure and ARIA landmarks as sufficient techniques, so a page with proper landmarks and headings can conform without an explicit skip link where screen reader navigation suffices.
Be honest about the gap in that position: landmarks and headings are only operable through assistive technology. A sighted keyboard-only user, someone with a motor impairment and no screen reader, gets nothing from a main element. Where a page relies solely on landmarks, record the conformance outcome but flag the keyboard-only experience: if those users still have to traverse the full repeated navigation on every page, recommend a skip link as the fix, and grade a fail where no mechanism of any kind exists. The strongest pages ship both: landmarks for AT users, a visible-on-focus skip link for everyone else.
iOS
The European standard declares this criterion void for software: it is written for sets of web pages, and equivalent sets of software programs are extremely rare. Native iOS apps therefore carry no mandatory equivalent, and a missing skip mechanism in an app is not a conformance failure under this criterion.
Auditors still apply good-practice guidance here, marked as guidance rather than a requirement. VoiceOver users benefit enormously from being able to jump past repeated chrome: check that section titles carry the header trait so the rotor's Headings setting can move straight to content, and that grouped regions (navigation bars, tab bars, repeated card shells) can be stepped over with container navigation rather than element by element. The escape gesture (two-finger scrub) should back out of modal layers cleanly. Well-structured headings, which you grade under 1.3.1, deliver the same practical benefit a skip link delivers on the web: note weaknesses as advisory findings.
Android
As on iOS, the European standard declares this criterion void for software, because it targets sets of web pages and equivalent sets of software programs are extremely rare. Android apps carry no mandatory equivalent, so grade app screens as not applicable under this criterion.
As guidance, verify that TalkBack's reading controls can shortcut the repeated furniture: swipe up or down to select the Headings reading control, then confirm heading-to-heading navigation lands on the start of each content section. That only works when screens mark their section titles as headings (android:accessibilityHeading, ViewCompat.setAccessibilityHeading, or semantics { heading() } in Compose), which again is graded under 1.3.1 but delivers the bypass benefit in practice. Check that repeated toolbars and bottom navigation are traversed as compact groups, not as long runs of individual elements, and raise dense repeated blocks with no heading structure as advisory findings.
Pass and fail examples
Passes:
- The first Tab press on every page reveals a "Skip to main content" link; activating it moves focus so the next Tab lands on the first link inside the article.
- A skip link that is visually hidden by default and pops into view at the top of the page the moment it receives keyboard focus.
- A site with
header,nav, andmainlandmarks and a heading opening each content region, where screen reader landmark navigation jumps past the repeated blocks (sufficient under W3C techniques; still recommend a skip link for keyboard-only users). - A page offering several skip links ("Skip to content", "Skip to search"), each of which genuinely moves focus to its target.
Fails:
- Forty navigation links repeated at the top of every page with no skip link, no landmarks, and no headings: keyboard and screen reader users must traverse all of them on every page.
- A skip link styled with
display: none, so it never enters the tab order and no keyboard user can reach it. - A skip link that scrolls the main content into view but never moves focus: the next Tab press starts back at the top of the navigation, so nothing was bypassed.
- A skip link pointing at
#main-contentafter a redesign removed that ID: activating it does nothing. - A skip link that receives focus but remains invisible while focused, so sighted keyboard users cannot tell it is there.
Not a fail under this criterion:
- A page with a working skip link but a jumbled heading hierarchy (an
h4directly under theh1): the bypass mechanism exists, so file the structure problem under 1.3.1 Info and Relationships. - Focus moving through the main content in a confusing sequence: that is a 2.4.3 Focus Order finding, not a bypass finding.
- Navigation links appearing in a different relative order on different pages: file under SC 3.2.3 Consistent Navigation.
- A single long page of unique content with no internal shortcuts: this criterion targets blocks repeated across multiple pages, not length as such.
Commonly confused with
- Info and Relationships, SC 1.3.1. Heading structure quality belongs there: wrong levels, visual-only headings, missing programmatic structure. Under 2.4.1 the question is narrower: does some mechanism exist to bypass the repeated blocks? Headings can be the evidence for both, but they are separate findings.
- Focus Order, SC 2.4.3. 2.4.3 grades the sequence focus follows through the content; 2.4.1 grades whether users can skip a chunk of it entirely. A skip link that moves focus to the wrong place can raise both, but do not file a missing skip link under focus order.
- SC 3.2.3 Consistent Navigation. That criterion requires repeated navigation to appear in the same relative order across pages. It is about predictability of the repeated block; 2.4.1 is about escaping it.
- SC 2.4.7 Focus Visible. A skip link that appears on focus is not a focus indicator trick; it is content. But a skip link that stays invisible while focused fails 2.4.1 for keyboard users and may also evidence a focus visibility problem: grade each on its own terms.
How AUDITSU tests this
AUDITSU's audit walkthrough covers bypass mechanisms at the start of every web page review. The walkthrough prompts you to press Tab on a fresh page load and record what appears, confirm the skip link is visible on focus and actually moves focus into the main content, and inspect the landmark and heading structure with a screen reader running. Each question records a pass, fail, or not applicable result per screen with the evidence attached, so a broken skip link is tied to the exact page where you found it.
For native app screens the walkthrough reflects the European standard's position that this criterion is void for software: app screens are recorded as not applicable, and the heading and grouping checks that deliver the equivalent benefit are captured as guidance notes alongside your 1.3.1 results rather than as conformance failures.
For the full guided workflow, see the audit platform.