Issue Bug Closed

#107739Search field has no label (uses placeholder)

Christian Rath-Ulrich 10/17/25, 07:10 updated 10/10/26, 05:33

Description

*Problem description*
New page content can be added in the ‘Page’ area via a modal window. Within this modal window, there is a search field that has neither a programmatically determinable nor a visually visible label. Instead, the placeholder attribute is used as a substitute for the label.

*Recommended action*
The search field must be provided with a meaningful, permanently visible label. This label must be provided via a correctly assigned

*Target group*
Cognitive impairment

Internal reference: 5814

Reviews 2

Files 3

History 811

  1. Lina Wolf commented <span data-processor="relativetime" data-value="2025-10-23T07:49:55+00:00" > 10/23/25, 07:49 </span>

    While a placeholder is read by accessive Technology, it cannot be considerered a “Visible label”:

    https://www.digitala11y.com/anatomy-of-accessible-forms-placeholder-is-a-mirage/

    So we would need a visible label.

    Also according to Nielsen https://www.nngroup.com/articles/form-design-placeholders/ a placeholder generally does more harm then good even to non-handycapped users

  2. Benjamin Franzke commented and changed attached clipboard-202510300045-wjbn9.png attached clipboard-202510300046-shp6i.png <span data-processor="relativetime" data-value="2025-10-29T23:52:26+00:00" > 10/29/25, 23:52 </span>

    Per https://www.w3.org/WAI/tutorials/forms/labels/#hiding-label-text
    a label is actually not needed in any case, if the following statement
    applies:

    > The purpose of the text input field is evident from the context in
    > most situations.

    A well known icon can therefore be sufficient, example:
    clipboard-202510300045-wjbn9.png

    Why is a visual icon sufficient?
    The target group is not visual impairment, but cognitive impairment in this case.
    We already provide stable and readable context for screenreader users via the placeholder (which is used if a context-repitition is requested via a shortcut) and therefore “only” need to provide some additional permantent visual context that identifies the input as search input.

    @geborune maybe you can contact your a11y experts if they agree. Thanks!

    Google does the same, btw:
    clipboard-202510300046-shp6i.png

    I pushed a patch that would implement that approach:
    > 91352: [BUGFIX] Add visual context to new record wizard filter input | https://review.typo3.org/c/Packages/TYPO3.CMS/+/91352

  3. Christian Rath-Ulrich commented <span data-processor="relativetime" data-value="2025-11-13T15:55:55+00:00" > 11/13/25, 15:55 </span>

    Benjamin Franzke wrote in #note-6:
    > Per https://www.w3.org/WAI/tutorials/forms/labels/#hiding-label-text
    > a label is actually not needed in any case, if the following statement
    > applies:
    >
    > > The purpose of the text input field is evident from the context in
    > > most situations.
    >
    >
    >
    > A well known icon can therefore be sufficient, example:
    > !clipboard-202510300045-wjbn9.png!
    >
    > Why is a visual icon sufficient?
    > The target group is not visual impairment, but cognitive impairment in this case.
    > We already provide stable and readable context for screenreader users via the placeholder (which is used if a context-repitition is requested via a shortcut) and therefore “only” need to provide some additional permantent visual context that identifies the input as search input.
    >
    > @geborune maybe you can contact your a11y experts if they agree. Thanks!
    >
    > Google does the same, btw:
    > !clipboard-202510300046-shp6i.png!
    >
    > I pushed a patch that would implement that approach:
    > > 91352: [BUGFIX] Add visual context to new record wizard filter input | https://review.typo3.org/c/Packages/TYPO3.CMS/+/91352

    At first glance, this seems fine, but in practice it causes problems:
    • The placeholder disappears as soon as you start typing. Then it’s no longer clear what the field is actually for.
    • Screen readers rely on a real label, not the placeholder. Otherwise, the field is not announced correctly.
    • A visible label is also helpful for people without screen readers

    so your approch seems to be fine

  4. Georg Ringer commented and changed status Under Review Closed <span data-processor="relativetime" data-value="2026-10-10T05:33:32+00:00" > 10/10/26, 05:33 </span>

    closing issue, as solved with #108592

    if this is not fine to me, please contact me on slack to reopen the issue!