[List]: LIST_ROLE_DESCRIPTION ("List with interactive items. To move to the content press F2.") is announced by screen readers even when all list items are type="Inactive"

[IvyYang01]

Describe the bug

In [List.js|vscode-webview://11oe405gl734q74e6irajak825tlct3qm689s3j7pi5lpuc1u3d3/node_modules/@ui5/webcomponents/dist/List.js], the ariaDescriptionText getter unconditionally appends LIST_ROLE_DESCRIPTION whenever accessibleRole === "List" (the default), with no check on the interactivity of the items:

{{get ariaDescriptionText() {
const parts = [];
if (this.accessibleRole === ListAccessibleRole.List)

{ parts.push(this.defaultAriaDescriptionText); // always added }
...
}

get defaultAriaDescriptionText()

{ return List_1.i18nBundle.getText(LIST_ROLE_DESCRIPTION); // "List with interactive items. To move to the content press F2." }
}}

Suggested fix: Conditionally apply LIST_ROLE_DESCRIPTION only when at least one item has type="Active" or type="Navigation":

{{get ariaDescriptionText() {
const parts = [];
if (this.accessibleRole === ListAccessibleRole.List && this._hasActiveItems)

{ parts.push(this.defaultAriaDescriptionText); }
...
}}}

Isolated Example

No response

Reproduction steps

...

Expected Behaviour

When all ListItemStandard children have type="Inactive" (or type="Detail"), the list contains no interactive items. The LIST_ROLE_DESCRIPTION should not be added to aria-description in this case, as it misleads non-sighted users into expecting interactive behavior and pressing F2 unnecessarily.

Screenshots or Videos

No response

UI5 Web Components for React Version

2.22.1

UI5 Web Components Version

2.22.0

Browser

Chrome

Operating System

No response

Additional Context

No response

Relevant log output

Organization

No response

Declaration

• I’m not disclosing any internal or sensitive information.

[Lukas742]

Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.

[MapTo0]

Hello Colleagues!

This makes sense maybe but should be checked with the ACC expert on the team.
Please have a look.

sample

I guess changing the AccessibleRole from application side would solve the issue but I am leaving the final solution to you.

Best Regards!
Martin

[kgogov]

Hi @IvyYang01, thanks for the detailed report!

This has actually already been addressed by #13489 (commit f27c1ff) which introduced a _hasInteractiveItems guard on LIST_ROLE_DESCRIPTION — the F2 aria-description is now only announced when the list actually contains interior tabbable content.

The final implementation is slightly stricter than the fix you proposed. It considers a list "interactive" only when:

• selectionMode="Delete" (per-row delete button is tabbable), or
• any item is type="Detail" (the detail button is tabbable), or
• any item is a ui5-li-custom (may contain arbitrary tabbable slot content)

type="Active" and type="Navigation" are intentionally not treated as interactive here, because the announcement specifically says "To move to the content, press F2". F2 in ListItem enters interior tabbable descendants — Active/Navigation rows have none (the row itself is activated with Enter/Space, and arrow keys navigate between rows), so pressing F2 on them does nothing. Announcing the F2 hint for those would still be misleading.

Verified locally against the cases from your report:

List content	aria-description announced?
All type="Inactive"	no ✅
All type="Active"	no ✅
All type="Navigation"	no ✅
Any type="Detail"	yes ✅
selection-mode="Delete"	yes ✅
ui5-li-custom with tabbable content	yes ✅

The fix is on main and included from v2.24.0-rc.3 onwards; it will land in the next stable 2.24.0 release. Closing this as a duplicate of #13347 — please reopen if you still see the behavior on ≥ 2.24.0.

[github-actions]

This issue has been closed. To reopen, just leave a comment!