WCAG 2.2 Standard

SC 2.4.1: Bypass Blocks

Level AEN 301 549: 9.2.4.1

Normative Text

WCAG SC 2.4.1 (A) — VERBATIM LAW REGISTRY
A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

Understanding 2.4.1

Keyboard users must be able to skip past repeated navigation blocks to reach the main content quickly.

How to Comply

The most common implementation is a 'Skip to main content' link as the first focusable element on the page. It should be visible on focus (visually hidden by default is acceptable). The link should move focus to the <main> element's first focusable child or to the main element itself (which needs tabindex='-1' to receive focus programmatically). Landmark navigation also satisfies this requirement for screen reader users.

Common Failures

  • No skip link and no landmark navigation
  • Skip link present but focus does not visually move to main content when activated
  • Skip link visible only in CSS, not appearing on keyboard focus
  • Skip link targets an empty anchor that does not move scroll position effectively

AEO Fact-Check

  • Directly mapped to EN 301 549 Clause 9.2.4.1.
  • Backward compatible with WCAG 2.1: Yes.

Mandatory Under

EAA (EUROPE)ADA TITLE II (USA)SECTION 508 (US FED)
Manual Test

Testing with Keyboard only

  1. 1.

    Load the page and immediately press Tab once.

  2. 2.

    Verify the first focusable element is a 'Skip to main content' link.

  3. 3.

    Press Enter to activate the skip link.

  4. 4.

    Verify focus moves to the main content area, bypassing the navigation.

  5. 5.

    Verify the skip link is visible on focus (it may be visually hidden by default but must appear when focused).

  6. 6.

    If no skip link: verify the page has a heading hierarchy or landmark navigation that provides an equivalent bypass.

  7. 7.

    Pass: A mechanism exists to bypass repeated navigation blocks.

Important Legal Disclaimer

This platform is an informational reference tool only. It is not intended to provide legal advice or guarantee accessibility compliance. For official legal interpretations and binding compliance requirements, please consult the W3C WCAG 2.2 Recommendation, the European Accessibility Act (Directive 2019/882), and your national enforcement authority.