Issue Bug Resolved

#1088343-point menu in the file list not labeled reliably

Jennifer Geiß 02/03/26, 08:33 updated 10/24/26, 06:55

Description

Description

The label for the three-dot menu icon is provided exclusively via the title attribute. Since the title attribute is not reliably used by screen readers as an accessible name, the element does not have a robust, consistently exposed Accessible Name. As a result, the three-dot menu may not be recognized by screen reader users as a control with the function “More options”.

Reproduction steps

  1. Open the TYPO3 backend and navigate to the Filelist (Dateiliste).
  2. In the filelist, locate an entry/folder where the three-dot menu (context menu/more options) is displayed.
  3. Inspect the three-dot menu icon using the browser DevTools.
  4. Check how the accessible name for the icon is implemented:
  5. Confirm that the label is provided only via a title attribute.
  6. No aria-label, aria-labelledby or visually hidden text is present.
  7. Test with a screen reader (e.g. NVDA, JAWS, VoiceOver) to see how the icon is announced and whether its purpose (“More options”) is clearly conveyed.

Impact

  • Screen reader users may get no or only an unreliable/inconsistent name for the three-dot menu.
  • The purpose of the control (“More options”) is not robustly exposed, leading to usability issues or uncertainty.
  • This restricts the accessibility of navigation and interaction in the backend, especially for users who rely heavily on verbal labels.

Target group

  • Screen reader users
  • Users with visual impairments or blindness
  • TYPO3 backend editors relying on assistive technologies

Severity

Medium to high (control is difficult to understand without a robust accessible name; affects navigation/interaction with a frequently used menu).

Frequency

Occurs for every instance of the three-dot menu in the filelist (100 % of affected menus).

Definition of Done

  • The three-dot menu icon has a robust accessible name that clearly describes the purpose of the control (e.g. “More options”).
  • The accessible name is not provided exclusively through the title attribute.
  • Screen readers announce the element reliably with a meaningful label.
  • Manual testing with at least one screen reader (e.g. NVDA/JAWS/VoiceOver) has been carried out successfully.
  • Existing functionality and the visual appearance of the icon remain unchanged.

Suggestion

Add a descriptive aria-label to the element, e.g. aria-label=“Weitere Optionen” / “More options”.

Recommended solution

Add aria-label=“Weitere Optionen” (or “More options”) to the element of the three-dot menu.
Alternatively or additionally, insert visually hidden text such as html

Weitere Optionen
inside the link or button if a semantic text node is preferred.
Ensure the visually-hidden class is implemented according to common patterns (off-screen but readable for screen readers).

References / WCAG 2.2 Reference

  • WCAG 2.2 – 1.3.1 Info and Relationships: Controls must be clearly identifiable along with their purpose.
  • WCAG 2.2 – 2.5.3 Label in Name: The accessible name should reflect the visual purpose (“More options”).
  • WCAG 2.2 – 4.1.2 Name, Role, Value: Interactive elements require a programmatically determinable name (accessible name) that does not rely solely on title.

Reviews 2

Files 2

History 26

  1. Riccardo De Contardi commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-10-24T06:55:15+00:00" > 10/24/26, 06:55 </span>

    Applied in changeset commit:5b75cbdf6c6045d410d2c5f82ecf2408a3df761c.