Issue Bug New Orphaned

#107449WCAG: Navigation from module menu to workspace

Christian Rath-Ulrich 09/12/25, 08:54 updated 09/12/25, 08:54

Description

Here using the example of “My Dashboard”

The user navigates through the module menu and has selected “My Dashboard.”

The corresponding workspace for My Dashboard opens to the right.

It is not clear to the user that a workspace has opened and how they can navigate to it.

It is not easy to navigate to the workspace using the tab key, as the focus does not automatically jump to the selected area. Using the tab key first jumps to the search field.

A structuring element is missing. It is not clear what the workspace belongs to and where it begins and ends.

Solution idea

In principle, the “workspace” could be marked as a region.

Idea: Mark the horizontal menu, module menu (left-aligned), and workspace as regions.

Expected result

A screen reader outputs where the user is located and that a workspace has opened, corresponding to the selected module menu item from the main menu on the left. This is automatically selected and the focus is set accordingly.

It should be clear where the workspace begins and where it ends.

Additional information/comments

As soon as an element (e.g., within the menu or when creating a new page) is selected/activated, the focus must move to a clearly named (X) area.

“It wasn’t entirely clear to me where I actually was.”

Internal reference: ITZBUNDPHP-4977

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] WCAG: Navigation from module menu to workspace Resolves: #107449 Releases: main