Issue Bug Closed

#108974Backend: Inputfields without label but with legend

Aphisit Chanathale 02/13/26, 10:49 updated 03/31/26, 08:11

Description

Some input fields in the TYPO3 backend do not have a label, only a legend. An example would be the Slugfield in the page properties. The ‘Slugfield’ in the page properties.
The slug field is just an example. There are probably more.

Steps to reproduce

Log in to the TYPO3 backend.
Open a record editing form where the “URL segment” can be configured (e.g. page properties or a record with a speaking URL/slug field).
Navigate to the section containing the URL segment field.
Use a screen reader (e.g. NVDA) to move focus to the URL segment input.

Current result

The URL segment text is output as a element.
The corresponding input field for the URL segment does not have an associated

Expected result

The URL segment input field has a clear, programmatically associated label that describes its purpose.
When the input receives focus, the screen reader announces a meaningful label such as “Enter URL segment” or similar wording.
The visual design remains unchanged or minimally affected by using a visually hidden text label.
Screen reader users can reliably understand that this input is used to enter or edit the URL segment.

Impact

Affects blind and visually impaired users who depend on screen readers to navigate backend forms.
Without a proper label, users may not understand what information is expected in the input field, which can lead to incorrect or incomplete URL segments.
This is an accessibility issue with respect to BITV / WCAG 2.1 criterion 3.3.2 (Labels or Instructions) and 1.3.1 (Info and Relationships), as form fields must have programmatically determinable labels.
Can negatively affect efficiency and reliability when creating or editing URLs in TYPO3.

Recommended solution

Add a visually hidden

Definition of done

The URL segment input field has an associated

Acceptance criteria

The URL segment input has a

Reviews 1