#109003Filelist: Add visually hidden label "Checkbox" for file selection checkboxes
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
The label text is “Checkbox”, and it is correctly linked to the corresponding checkbox via for/id.
Screen readers announce the checkboxes with a programmatic name when they receive focus.
No visual changes or regressions in the Filelist module’s layout and behavior.
Tested with at least one common screen reader and browser combination to confirm that the labels are announced.
The implementation meets BITV / WCAG requirements for accessible labeling of form controls.
Acceptance criteria
Checkbox inputs in the Filelist module are each associated with a
The label text is exactly “Checkbox”.
The label uses a visually hidden / screen-reader-only CSS class so that:
It is not displayed visually, and
It is correctly announced by screen readers.
Screen reader testing (e.g. NVDA + Firefox or JAWS + Chrome) confirms that focusing a checkbox announces it with a label.
No regressions in file selection behavior or visual layout in the Filelist module.
Accessibility review confirms that the checkboxes are now properly labeled and conform to BITV / WCAG requirements.
Reviews 2
History 48
-
Garvin Hicking commented and changed category status
NewNeeds 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> -
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!
-
Garvin Hicking commented and changed status
Needs FeedbackNew <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 -
Gerrit Code Review pushed patch set 1 for main to change 97634 status
NewUnder Review <span data-processor="relativetime" data-value="2026-11-13T20:41:18+00:00" > 11/13/26, 20:41 </span> -
Gerrit Code Review pushed patch set 1 for 14.3 to change 97640 <span data-processor="relativetime" data-value="2026-11-14T08:51:45+00:00" > 11/14/26, 08:51 </span>
-
Gerrit Code Review pushed patch set 2 for 14.3 to change 97640 <span data-processor="relativetime" data-value="2026-11-14T09:38:40+00:00" > 11/14/26, 09:38 </span>
-
Gerrit Code Review pushed patch set 3 for 14.3 to change 97640 <span data-processor="relativetime" data-value="2026-11-14T11:04:50+00:00" > 11/14/26, 11:04 </span>
-
Benni Mack commented and changed status
Under ReviewResolved done0 %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.
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 :-)