Skip to content

[ui5-li | ui5-list]: inner RadioButton announces 'Item Selection.' instead of option label in single-select mode (WCAG 4.1.2) #14273

Open

Description

@bennylalala

Bug Description

In single-select ui5-list mode (e.g. inside ui5-view-settings-dialog), each ui5-li renders an inner RadioButton via the selectionElement() function in ListItemTemplate.tsx. That RadioButton carries a hardcoded aria-label of "Item Selection." (from the i18n key ARIA_LABEL_LIST_ITEM_RADIO_BUTTON).

NVDA (and other screen readers that pierce the shadow DOM) focuses the inner div[role="radio"] inside the RadioButton shadow root and announces:

"Item Selection. radio button not checked"

The actual option label (e.g. "Ascending", "Completion Date", "Title") is never announced, because the inner radio button only carries the generic i18n string.


Root cause chain:

# packages/main/src/i18n/messagebundle_en.properties
ARIA_LABEL_LIST_ITEM_RADIO_BUTTON=Item Selection.
// packages/main/src/ListItem.ts  (line ~531)
ariaLabelRadioButton: ListItem.i18nBundle.getText(ARIA_LABEL_LIST_ITEM_RADIO_BUTTON),
// packages/main/src/ListItemTemplate.tsx  — selectionElement()
case this.modeSingleSelect:
  return (
    <RadioButton
      part="radio"
      disabled={this.isInactive}
      accessibleName={this._accInfo.ariaLabelRadioButton}   // ← "Item Selection."
      tabindex={-1}
      id={`${this._id}-singleSelectionElement`}
      class="ui5-li-singlesel-radiobtn"
      checked={this.selected}
      onChange={this.onSingleSelectionComponentPress}
    />
  );

The inner RadioButton's div[role="radio"] therefore gets aria-label="Item Selection.", which is what screen readers announce.

The outer <li> element already carries the correct ARIA semantics:

  • role="radio"
  • aria-checked
  • aria-posinset / aria-setsize
  • The option label is exposed via its text content / aria-labelledby

The inner RadioButton is purely decorative — it is redundant and its generic label conflicts with the accessible name on the host.


Affected Component

ui5-li / ui5-list (in SingleSelect / SingleSelectBegin / SingleSelectEnd mode)

Observed via ui5-view-settings-dialog (sort option list), which uses a single-select List internally.

Expected Behaviour

Screen readers should announce each option with its visible label (e.g. "Ascending radio button not checked"), not the generic string "Item Selection.".

Fix options (in order of preference):

  1. (Preferred — minimal, upstream) Add aria-hidden="true" on the inner RadioButton in selectionElement() when modeSingleSelect. The outer <li role="radio"> already provides all ARIA semantics; hiding the inner radio button removes the duplicate and the misleading announcement.

  2. (Alternative) Derive ariaLabelRadioButton from the list item's own accessible text (e.g. the item's text content or accessibleName prop) instead of the hardcoded i18n string — so the inner radio button, if not hidden, at least announces the correct label.

Isolated Example

Playground: https://ui5.github.io/webcomponents/components/fiori/ViewSettingsDialog/

Steps: Open the playground, click the sort/filter dialog, Tab to a sort option. NVDA will announce "Item Selection. radio button not checked" for each option instead of the option's label.

Steps to Reproduce

  1. Navigate to a page with a single-select ui5-list (e.g. the ViewSettingsDialog playground or any sort dialog)
  2. Tab to a list item in the single-select list
  3. Observe: screen reader announces "Item Selection. radio button not checked" — the option label is not announced

Expected: each option is announced with its visible label ("Ascending", "Descending", "Completion Date", etc.)

Log Output, Stack Trace or Screenshots

Source references confirmed in current main branch:

  • messagebundle_en.properties → ARIA_LABEL_LIST_ITEM_RADIO_BUTTON=Item Selection.
  • ListItem.ts → ariaLabelRadioButton: ListItem.i18nBundle.getText(ARIA_LABEL_LIST_ITEM_RADIO_BUTTON)
  • ListItemTemplate.tsx → selectionElement() passes accessibleName={this._accInfo.ariaLabelRadioButton} to inner RadioButton

Priority

High

Environment Info

UI5 Web Components Version

2.x (root cause in source confirmed against current main branch)

Browser

  • Chrome
  • Edge
  • Firefox
  • Safari

Operating System

macOS, Windows

Additional Info

Organization

SAP-SF

Activity

  1. self-assigned this
    on Nov 9, 2026
  2. kineticjs commented on Nov 9, 2026

    @kineticjs
    Contributor

    Hi @bennylalala,

    Thank you for sharing this issue. However, for Screen Reader Support, we recommend using JAWS (version 2024 and any later) + Chrome (latest). So far I wasn't able to reproduce the issue with JAWS. The option's visible label ("Ascending", "Descending", etc.) is announced in my testing:

    Image
  3. removed their assignment
    on Nov 9, 2026
  4. bennylalala commented on Nov 10, 2026

    @bennylalala
    Author

    @kineticjs We were able to reproduce the issue in JAWS as well. When opening the Form Field List (JAWS key + F5) on the ViewSettingsDialog demo page, every radio button option is announced identically as "Item Selection." — the actual option names (Name, Position, Company, Department) are completely lost. A JAWS user has no way to distinguish between the options.

    The same problem occurs in NVDA when navigating between radio buttons using the R key — each option is announced as "Item Selection." rather than its visible label.

    And I see a similar ticket https://jira.tools.sap/browse/SAPDESIGNSYSTEM-251 which team is working on to hide the checkbox from screen reader when it works as selection in List/Table..It should be applied tot the Radio.

    Image
  5. aleksandar-terziev commented on Nov 10, 2026

    @aleksandar-terziev
    Contributor

    Hi @UI5/ui5-team-ctr-pir,

    Can you take a look at this issue ?

    Regards,
    Aleksandar

  6. moved this from Issues to In Progress in Maintenance - Topic Pon Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions