Issue Feature Resolved

#109003Filelist: Add visually hidden label "Checkbox" for file selection checkboxes

Aphisit Chanathale 02/18/26, 11:21 updated 11/14/26, 11:35

Description

Steps to reproduce

Log in to the TYPO3 backend.
Open the Filelist module.
Navigate to a storage (e.g. fileadmin/) so that the list of files and folders is displayed.
Move focus to the list of files and navigate to one of the checkboxes in the file list using only the keyboard and/or a screen reader (e.g. NVDA, JAWS, VoiceOver).

Current result

Each file/folder row in the Filelist module contains a checkbox input.
The checkbox input has no accessible label:
No associated

Expected result

Each checkbox in the Filelist module has a clear, programmatically determinable label.
When a checkbox receives focus, screen readers announce a meaningful name so that users understand that it is a selectable checkbox for the corresponding file/folder.
The accessible label is available without changing the visible design of the Filelist view.
Screen reader users can reliably identify and operate the checkboxes in the file list.

Impact

Affects blind and visually impaired users who rely on screen readers to operate the Filelist module.
Without an accessible label, users do not know what the checkbox controls, which can lead to accidental selection or deletion/moving of incorrect files.
This is an accessibility issue with respect to BITV / WCAG 2.1 criteria 1.3.1 (Info and Relationships) and 3.3.2 (Labels or Instructions), as interactive form controls must expose a programmatic name/label.
Reduces trust and efficiency for assistive technology users when managing files in the TYPO3 backend.
Recommended solution
For each checkbox input in the Filelist module, add an associated

Definition of done

Every checkbox in the Filelist module has an associated

Acceptance criteria

Checkbox inputs in the Filelist module are each associated with a

Reviews 2

History 48

  1. Garvin Hicking commented and changed category status New Needs Feedback target version Tags Usability accessibility gsb <span data-processor="relativetime" data-value="2026-02-18T19:45:52+00:00" > 02/18/26, 19:45 </span>

    Hi!

    Could you please use categories and tags for your report so we are better able to see them later? Your colleagues use them quite well, and that definitely would help, to line them up with the tags and categories they use.

    Also please only use “next patchlevel” in case you’re actively working on a patch for it.

    Thanks! I know we do not particularly advise this, but in case of the large volume of gsb issues we need to keep them in sync to not interfer with “the other” issues :-)

  2. Jennifer Geiß commented <span data-processor="relativetime" data-value="2026-03-27T15:39:30+00:00" > 03/27/26, 15:39 </span>

    Hey Garvin,

    sorry, we will take care to add categories and tags like we used to do.

    Could you change the status from “Needs Feedback” to “New” or something that suits better. I don’t have permission to do that.

    Thanks for your advice and support!

  3. Garvin Hicking commented and changed status Needs Feedback New <span data-processor="relativetime" data-value="2026-03-27T16:59:59+00:00" > 03/27/26, 16:59 </span>

    Hi Jennifer!

    Sure yes, I just set it to “new”. Thanks for getting to address these issues, I saw some work of yours already. I’m looking forward to trying to address them now that our stabilization phase for v14 is set to begin.

    Regards,
    Garvin

  4. Benni Mack commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-14T11:35:10+00:00" > 11/14/26, 11:35 </span>

    Applied in changeset commit:3f01f7a3d648d9a4d4a8046a6086a3e577e16738.