Issue Bug Closed

#108491Website language not announced to screen readers – Language selector lacks accessible labeling

Jennifer Geiß 12/16/25, 08:21 updated 03/17/26, 08:30

Description

Description

Context:

The currently selected website language is not reliably announced by screen readers. The flag within the selected option has an empty alt attribute, the active language in the options list is hidden from assistive tech (e.g., aria-hidden=“true”), and the control lacks a clear accessible name.
Problem: Screen reader users neither get a meaningful control name nor the status of the selected language. Relying on a flag alone is insufficient and leads to information loss.

Goal/Value:

Make the language switcher fully accessible: clear accessible name, semantically correct active option state, meaningful non-text labels. Enhances usability, reduces support load, and meets WCAG guidelines.

Target group

Users who rely on Screenreader

Scope

EN – Must:

Provide a clear accessible name to the language selector (e.g., aria-label=“Select language”).
Mark the active language structurally in the options list (e.g., role=“option” with aria-selected=“true”).
Do not hide r

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 1

History 4

  1. Jennifer Geiß commented <span data-processor="relativetime" data-value="2025-12-16T09:01:37+00:00" > 12/16/25, 09:01 </span>

    Must:

    Provide a clear accessible name to the language selector (e.g., aria-label=“Select language”).
    Mark the active language structurally in the options list (e.g., role=“option” with aria-selected=“true”).
    Do not hide relevant information via aria-hidden=“true” (flag or text of active option must not be hidden).
    Meaningful alternative text for non-text content if it conveys language identification (e.g., alt=“Deutsch”).
    Ensure full keyboard operability: focus, open/close, navigate, select.

    Should:

    Announce state changes on language selection (e.g., via a polite live-region or proper Name/Value updates so screen readers read the change).
    Do not rely on flags alone: always show textual language labels (e.g., “Deutsch”, “English”).

    Could:

    Use aria-current=“true” to denote the current language if the pattern is applicable.
    Localize accessible names depending on the UI language (e.g., “Sprache auswählen” vs. “Select language”).

    DoD:

    • Implementation per ARIA practices; full keyboard control; screen reader verification in NVDA + VoiceOver.
    • Unit/E2E tests for interaction and ARIA attributes.
    • Documentation in component catalog / README.
    • PO sign-off; WCAG checks 1.1.1, 4.1.2, 3.3.2, 2.1.1 passed.
  2. Riccardo De Contardi commented and changed status New Closed <span data-processor="relativetime" data-value="2026-03-17T08:30:28+00:00" > 03/17/26, 08:30 </span>

    I close this issue as a duplicate of #108465, please continue the discussion there.

    A relation has been created between the two issues to keep track of the information written here.

    If you think that this is the wrong decision please reopen it or ping me.

    Thank you.