Issue Feature Under Review Quiet

#110101Add skip links for keyboard users in TYPO3 backend

Aphisit Chanathale 06/25/26, 07:40 updated 10/23/26, 20:30

Description

Steps to reproduce

Log in to the TYPO3 backend.
Use only the keyboard (Tab / Shift+Tab, arrow keys) to navigate the backend interface.
Start from the very top of the page (browser address bar → page content).
Try to quickly reach:

  • The main navigation / page menu,
  • The site tree (if available in the current module),
  • The main content area (e.g. language selector and content form).

Current result

There are no skip links at the beginning of the backend page.
Keyboard users must tab through multiple controls and interface elements before reaching the main areas they want to interact with (e.g. main menu, site tree, main content).
There are no intermediate skip links before the page menu or before the site tree to jump directly to the next major section.
As a result, navigating the backend using only a keyboard is time‑consuming, repetitive, and hard to orient in, especially for frequent users and screen reader users.

Expected result

The TYPO3 backend provides skip links to allow keyboard users to jump quickly between main regions of the interface.
At the top of the page, a skip link (or a small group of skip links) is available and focusable, allowing quick navigation to:

  • The page/menu navigation,
  • The site tree (if present),
  • The main content area (e.g. top language selector / content).

Impact

Affects keyboard‑only users, screen reader users, and many users with motor or cognitive impairments who rely on efficient keyboard navigation.
Without skip links, users must repeatedly tab through the same interface elements on every page, which:

Reduces efficiency and increases fatigue,
Makes it harder to orient within the backend,
Can discourage or effectively block some users from managing content.
This impacts compliance with WCAG / BITV criteria related to keyboard accessibility and bypassing blocks of content, in particular WCAG 2.4.1 (Bypass Blocks).

Recommended solution (for context / implementation guidance)

Example: https://design-system.service.gov.uk/components/skip-link/

Add a skip link container at the very beginning of the <body> that becomes visible on keyboard focus.<br>Provide skip links to:</body>

The page/menu navigation,
The site tree (if present in the current view),
The main content area (e.g. language selector / main form).
Ensure these targets have corresponding landmarks or IDs to receive focus.

Use a common, visually recognizable style for skip links when they receive focus (e.g. visible outline, contrast, simple positioning).
Ensure skip links are implemented in a way that works consistently across major browsers and screen readers.

Definition of done

At the top of the backend page, focusable skip links exist that allow jumping to:

Page/menu navigation,
Site tree (if present),
Main content area.

Skip links are:

  • Reachable via keyboard,
  • Clearly visible on focus,
  • Correctly associated with their target sections (via IDs / landmarks).
  • Screen reader and keyboard testing confirm that the skip links work reliably and significantly improve navigation.
  • No visual regressions in the backend layout for mouse users.

Acceptance criteria

At the beginning of the <body>, there is a set of skip links that, when focused and activated, move focus to:</body>

Page/menu navigation,
Site tree (when available),
Main content area.
Skip links near main sections

Skip links are visible when focused and hidden otherwise (using a standard accessible pattern).
Targets of skip links (menu, site tree, main content) are focusable or handle focus correctly.
Keyboard‑only navigation is significantly simplified; users can quickly reach main sections without excessive tabbing.

Tested with at least one screen reader (e.g. NVDA + Chrome) and pure keyboard navigation to confirm that:

Skip links are announced,
They move focus to the intended sections,
They improve orientation and navigation.
Compliance

Accessibility review confirms that skip links contribute to meeting WCAG 2.4.1 (Bypass Blocks) and improve overall keyboard usability of the TYPO3 backend.

Reviews 1

History 110