#110043Alternative text for controls in the page tree
Description
Steps to reproduce
Log in to the TYPO3 backend.
Open the Page module so that the page tree is visible.
Navigate through the page tree controls using keyboard and NVDA with Google Chrome (e.g. expand/collapse toggles, “three dots” menu button, date picker icon, and other icon-only buttons).
Observe how NVDA announces the controls and whether it finishes reading out the accessible name.
Current result
Various controls in and around the page tree are implemented as buttons with an aria-label (e.g. “three dots” button to open a context menu, date picker icon button, other icon-only controls).
Within these buttons/containers, there are elements that use aria-hidden=“true” to hide decorative content from assistive technologies.
In NVDA with Chrome, the presence of aria-hidden=“true” within the same control causes the output of the aria-label to be cut off or not announced correctly.
As a result, screen reader users do not always receive the full or expected alternative text for these controls and may not understand their purpose or function.
h2. Expected result
All interactive, icon-only controls in the page tree (e.g. “three dots” menu button, date picker trigger, other icon buttons and so on) expose a clear, complete, and reliably announced accessible name.
NVDA in Chrome (and other screen readers/browsers) announces the full label for these controls without being interrupted or truncated by aria-hidden content.
The accessible name is provided in a robust way that does not conflict with aria-hidden usage within the same button.
Icons that trigger actions or menus are understandable and distinguishable for screen reader users.
Impact
Affects blind and visually impaired users who rely on screen readers, especially NVDA users in Chrome.
Broken or truncated announcements of alternative text make it hard to understand the function of controls such as:
“Three dots” buttons that open context menus,
Icon-only date picker buttons,
Other icon-only interactive elements in the page tree.
Users may overlook available actions, misinterpret controls, or be unable to operate certain functions efficiently.
This undermines the usability and accessibility of the page tree navigation and related UI controls.
Recommended solution (for context)
Replace the use of aria-label on the buttons with an internal, visually hidden text node that acts as the accessible name:
Move the label text into a … inside each button.
Remove the aria-label attribute so that the button’s accessible name comes from the inner text, not ARIA.
Ensure that any decorative elements within the button that use aria-hidden=“true” do not interfere with the newly provided text label.
For existing examples, also translate the label text into the appropriate language (e.g. for the “three dots” menu button, use a clear label like “Open menu”; for the date picker, “Open date picker”, etc.).
Keep the visual appearance of the icon-based buttons unchanged while providing robust accessible names.
Definition of done
All relevant icon-only buttons/controls in the page tree and related UI (e.g. “three dots” context menu button, date picker icon button, similar controls) receive their accessible name from visible or visually hidden inner text instead of aria-label.
Each button contains a … (or equivalent) with a descriptive label, and aria-label is removed or no longer needed.
NVDA in Chrome announces the full, correct label for these controls without interruption or truncation, even when aria-hidden=“true” is present on decorative elements.
The label text is properly localized/translated where appropriate.
No visual regressions occur: all buttons and icons look and behave the same for sighted users.
Acceptance criteria
Relevant Icon-only buttons in and around the page tree (see screenhshots) (e.g. “three dots” menu button, date picker icon button, and similar controls) contain an inner … with a descriptive label, and do not rely on aria-label for their accessible name.
Decorative content inside these buttons may still use aria-hidden=“true”, but does not affect the announcement of the label.
NVDA with Chrome announces each control with a complete and meaningful name (e.g. “Open menu”, “Open date picker”), with no truncation or early termination.
Labels are correctly translated into the active backend language.
Visual layout and interaction of the buttons remain unchanged for mouse and keyboard users.
Accessibility review confirms that the alternative text for controls in the page tree is robust and works reliably across major screen readers and browsers.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 9
- image-2026-05-26-16-29-02-003.png
- image-2026-05-26-16-27-39-885.png
- image-2026-05-26-16-26-35-417.png
- image-2026-05-26-16-26-47-982.png
- image-2026-05-26-16-25-07-828.png
- image-2026-05-26-16-24-49-220.png
- image-2026-05-26-16-24-30-003.png
- image-2026-05-26-16-23-55-748.png
- image-2026-05-26-16-23-38-606.png
History 2
-
Christian Rath-Ulrich commented <span data-processor="relativetime" data-value="2026-10-21T15:12:52+00:00" > 10/21/26, 15:12 </span>
-
Oliver Bartsch commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-17T21:10:04+00:00" > 11/17/26, 21:10 </span>Hey,
thanks for the detailed report and the screenshots. None of the controls shown are from the page tree. They are the FormEngine datepicker and link-browser buttons and the context menu triggers (three-dots button and record icon) in the Page module.
I checked the markup in 14.3 and main. Each of these buttons has a non-empty, translated aria-label (“Open date picker”, “Open context menu”, “Link”), and the icon inside is marked aria-hidden=“true”. Under the accessible-name rules, aria-label takes priority over the button’s contents, so the hidden icon cannot cut the name short, and the same speech-viewer capture shows “Kontextmenü öffnen” read out in full several times. Christian retested with NVDA on TYPO3 15 and confirmed it is announced correctly, and nothing changed on these controls in between, so the single-letter announcements most likely came from that NVDA/Chrome version rather than from TYPO3.
I’m closing this issue. If you can still reproduce it on a current 14.3 with current NVDA and Chrome, please comment with the exact NVDA and browser versions and I’ll reopen it.
Thanks, Oli
this is solved in the current version retested in NVDA on TYPO3 15