Issue Bug Under Review

#107447There are no landmarks/regions present beside the navigation (wasWCAG: Language change functionality)

Christian Rath-Ulrich 09/12/25, 08:40 updated 11/16/26, 12:41

Description

Description

It is hard for non visual users to effectively navigate to a certain section within the viewport aside from the toolbar or the iframe since there are no landmarks present.
This affects e.g. the language setting area or the widgets on the dashboard.
Example: when navigating within the iframe, navigation starts with “Layout”, Language Setting area is lost.

Reproduction steps

open Pages
navigate via Screenreader through iframe

Impact

Target group

visual

Severity

high

Frequency

very common

Definition of Done

WHEN I use a desktop screenreader (NVDA, JAWS, VoiceOver) AND
I use the tab key to enter the web browser window
I HEAR all main functional areas (main, header, etc,) are discoverable as landmarks or regions

Recommended solution

Either assign aria-regions to the big areas of focus, within the iframe and aside from it or alternatively use semantic html elements. Keep in mind role=region needs label to be identifiable.

Examples:

header (could be semantic element)
pagetree (aria-region)
language setting (aria-region)
Workspace/main (could be semantic element)

References / WCAG 2.2 Reference

2.4.1. Bypass Blocks

Prioritizing the removal of the issues found

must have

Screencast or Screenshot

e6396792-3e31-4af7-b8ab-dafcc3f80c45.png

—-

original message:

The user is on the “Page” module point. The vertical menu of the page hierarchies and the work area open to the right of it.

The language comparison functionality now appears above, displayed in a drop-down menu that is filled with the Layout selection by default.

Layout is specified proportionally as a frame, but “Language comparison” cannot be accessed via frames. There is no consistency here.

Via the navigation, the page effectively starts with “Layout” when the field is selected. It is unclear where the user is located and what the menu/function belongs to. Add heading desired. (H1). Layout and Language Comparison are somewhat lost.

Solution idea:

Add a structuring element to assign the functionality to the work area. Include the language change in a tab?

The Layout and Language Comparison fields must be output with the same attributes (frame?).

Expected result:

The user navigates from the page tree to the workspace and is given the option of displaying the page in English or French. The menu is located where expected and is integrated into the workspace.

internal reference: ITZBUNDPHP-4985

Reviews 1

Files 2

History 46

  1. Markus Timtner changed attached e6396792-3e31-4af7-b8ab-dafcc3f80c45.png subject WCAG: Language change functionality There are no landmarks/regions present beside the navigation (wasWCAG: Language change functionality) description TYPO3 Version 13 14 Tags accessibility accessibility,TAS2025 <span data-processor="relativetime" data-value="2025-10-30T06:59:56+00:00" > 10/30/25, 06:59 </span>