SiteLint documentation and guidelines

Verify bypass blocks

Description

This rule does not automatically validate anything. It simply reminds you to manually verify that a mechanism is available to bypass blocks of content that are repeated on multiple Web pages. Users who navigate sequentially through content, such as keyboard-only users and screen reader users, benefit from being able to skip directly to the primary content rather than tabbing through every repeated navigation block, header, or sidebar on each page. The most common technique is a Skip to main content link placed as the first focusable element on the page. This requirement is defined by WCAG Success Criterion 2.4.1 (Level A).

Disabilities impacted

  • Visual – Blind and low-vision users who rely on screen readers must listen to every repeated block of content before reaching the main content. Without a bypass mechanism, each page load forces them to navigate through the same navigation links, search bars, and banners, creating a frustrating and time-consuming experience.
  • Motor control – Users with limited dexterity, tremor, or who rely on switch devices or voice control must perform many more actions to reach the primary content without a skip link. Repeated tabbing through navigation increases physical effort and can lead to fatigue or abandonment.
  • Screen reader – Screen reader users navigate via virtual cursor or quick navigation keys. Repeated blocks with no bypass mechanism interrupt the reading flow and make it difficult to locate the main content efficiently, especially on sites with complex or multi-level navigation menus.

Why it matters

Every page on a website typically shares common structural elements: a site-wide header, navigation bar, breadcrumb trail, and sidebar. Users who cannot scan visually must traverse these elements one by one on every page. Providing a bypass mechanism, such as a skip link or properly labeled landmarks, is one of the most impactful accessibility improvements a site can make. It directly reduces cognitive load, saves time, and enables independent use for people relying on assistive technologies. WCAG 2.4.1 is a foundational Level A requirement, meaning failure to meet it blocks access to content for a significant portion of users.

Coding problems and solutions

Common coding problems

  • Missing skip link – The page does not include any skip-navigation or skip-to-content link as the first focusable element.
  • Skip link not focusable or hidden – The skip link is present but hidden with display: none, visibility: hidden, or aria-hidden="true", making it inaccessible to keyboard and screen reader users.
  • Broken skip target – The skip link points to an id that does not exist or is not focusable, so focus jumps nowhere and the user remains at the top of the page.
  • No visible focus indicator – The skip link is not visible when it receives focus (e.g., it uses position: absolute; left: -9999px but never reappears on focus), leaving sighted keyboard users unaware of its presence.
  • Missing or ambiguous landmark roles – Navigation regions are not identified with ARIA landmark roles (role="navigation" or <nav>), so screen reader users cannot use landmark navigation to bypass them.
  • Multiple unlabeled navigation regions – The page contains several navigation landmarks but none have distinct labels, making it impossible for users to choose the correct one.

How to fix it

Place a skip link as the very first focusable element in the DOM. It should link to the id of the main content container. The link must be focusable and become visible when it receives keyboard focus.

Correct example
<a href="#main-content" class="skip-link">Skip to main content</a>

<nav aria-label="Site navigation">
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
    <li><a href="/contact">Contact</a></li>
  </ul>
</nav>

<main id="main-content" tabindex="-1">
  <h1>Page title</h1>
  <p>Primary content begins here.</p>
</main>
Incorrect example
<!-- Skip link is hidden and non-focusable -->
<a href="#main-content" style="display: none;">Skip to main content</a>

<nav>
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
  </ul>
</nav>

<!-- target id does not exist -->
<div>No main content landmark or skip target.</div>

When the skip link itself uses a title attribute for additional context (e.g., <a href="#main" title="Skip past navigation">Skip to content</a>), note that support for the title attribute varies across screen readers. For instance, VoiceOver by default has Hints set to Never or Speak after delay, which may prevent the title from being announced. Do not rely solely on title for critical information.

Use the :focus pseudo-class to reveal the link when a keyboard user tabs to it. Keep it visually hidden until focused to avoid cluttering the visual design.

Correct example
.skip-link {
  position: absolute;
  top: -100%;
  left: 0;
  z-index: 10000;
  padding: 8px 16px;
  background: #000;
  color: #fff;
  text-decoration: none;
}

.skip-link:focus {
  top: 0;
}
Incorrect example
/* Skip link is permanently hidden, even on focus */
.skip-link {
  display: none;
}

Use ARIA landmark regions to structure the page

Apply landmark roles to the major sections of the page so that screen reader users can navigate directly to the region they need without tabbing through every interactive element.

Correct example
<header role="banner">
  <a href="/"><img src="logo.png" alt="Site name"></a>
</header>

<nav aria-label="Main navigation">
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/products">Products</a></li>
    <li><a href="/contact">Contact</a></li>
  </ul>
</nav>

<main role="main">
  <h1>Welcome</h1>
  <p>Page content.</p>
</main>

<aside role="complementary" aria-label="Related articles">
  <h2>Related</h2>
  <ul>
    <li><a href="/article-1">Article 1</a></li>
  </ul>
</aside>
Incorrect example
<!-- No landmark roles or semantic elements -->
<div class="header">
  <a href="/"><img src="logo.png" alt="Site name"></a>
</div>

<div class="nav">
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/products">Products</a></li>
  </ul>
</div>

<div class="content">
  <h1>Welcome</h1>
  <p>Page content.</p>
</div>

Label repeated regions distinctly

When a page contains multiple landmarks of the same type (e.g., two <nav> elements or two <aside> elements), give each a unique, descriptive label using aria-label or aria-labelledby. This allows screen reader users to distinguish and bypass to the correct region.

Correct example
<nav aria-label="Main navigation">
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
  </ul>
</nav>

<nav aria-label="Footer navigation">
  <ul>
    <li><a href="/privacy">Privacy</a></li>
    <li><a href="/terms">Terms</a></li>
  </ul>
</nav>
Incorrect example
<!-- Two navigation regions with no distinguishing labels -->
<nav>
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
  </ul>
</nav>

<nav>
  <ul>
    <li><a href="/privacy">Privacy</a></li>
    <li><a href="/terms">Terms</a></li>
  </ul>
</nav>

Known Limitations

  • Manual verification required – This rule does not automatically detect the presence or correctness of a bypass mechanism. It only flags structural elements for manual review. The auditor must inspect the page and confirm that a functional skip link, landmark, or other bypass technique is present and working.
  • Single-page applications (SPAs) – In SPAs where content updates dynamically via JavaScript, the skip link may only work on the initial page load. Developers must ensure that focus management also handles view transitions and dynamically loaded content.
  • Shadow DOM – Skip links and landmark regions defined inside a Shadow DOM root may not interact correctly with the host page’s main content. The rule flags elements in the light DOM only; components with shadow roots require separate manual inspection.
  • iframes – Content inside iframes creates nested browsing contexts. A skip link on the parent page cannot bypass content inside an iframe, and each iframe must independently provide its own bypass mechanisms.
  • Dynamic content loading – If new navigation or repeated blocks are injected after the initial page render (e.g., a cookie consent banner, a chat widget), the auditor must verify whether these new blocks also offer a bypass or dismiss mechanism.

Resources

Rule

  • Audit: accessibility
  • Standard: WCAG
  • Level: A
  • Success Criteria: 2.4.1
  • Rule ID: bypass-blocks