Issue Bug New Quiet

#109474Add a Bypass Link to meet WCAG SC 2.4.1

Philipp Tautz 04/02/26, 15:17 updated 10/21/26, 16:07

Description

Description

The System lacks an easy way to jump into either the sidebar nor the main content, commonly referred to as “bypass link” or “skip link”.

As the sidebar can get very long, it can be really hard to navigate the system just by keyboard.

A bypass link should link to the following places:

  1. The sidebar
  2. The page navigation (if shown)
  3. The main content

Reproduction Steps

Open any page and press the tab-key. Instead of a bypass link, the focus is moved to the next entry in the header.

Impact

Adding a Bypass Link will help to meet WCAG SC 2.4.1

Recommended Solution

Add a bypass link just below the opening <body>-tag which links to</body>

  1. The sidebar
  2. The page navigation (if shown)
  3. The main content

The sidebar already has an id: “sidebar” and can therefore be easily targeted.
The page navigation and main content are wrapped inside a div wiht the id: “main”. Since the page navigation can get very long, I recommend to not target “main”, but instead add 2 new id’s.

Definition of done

  1. When pressing the tab-key the first thing after loading the page is a set of skip links.
  2. When choosing a link, focus is moved to the chosen container.
  3. The page navigation is only offered as link target, if it is rendered and visible.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Add a Bypass Link to meet WCAG SC 2.4.1 Resolves: #109474 Releases: main

History 3