Skip to content

[Feature Request][Side Navigation][A11Y]: Enhance user experience navigating components tree items #14232

Open

Description

@MaksymZahreba

Feature Request Description

Tree items in Side navigation have a custom aria-roledescription="Navigation List Tree" that is unnecessary and makes user experience worse.
Explanation for the change:
The custom aria-roledescription="Navigation List Tree" overrides how the role is announced. Screen readers announce the custom string instead of the standard “tree view”, so users don’t get the familiar cue that this is a tree widget.
This goes against the WAI-ARIA 1.2 authoring guidance for aria-roledescription: authors should use it only to clarify the purpose of an element whose role doesn’t convey it, and not to rename a well-known interactive role.
It is also unclear whether this value is localized. If it remains a hardcoded English string, it would be announced in English on non-English pages, which adds a further risk for users of localized versions.
As a result, the role is not communicated to assistive technology users in a recognizable way, which affects 4.1.2 Name, Role, Value (Level A).
Help links:
Understanding Success Criterion 4.1.2: Name, Role, Value | WAI | W3C
https://www.w3.org/TR/wai-aria-1.2/#aria-roledescription

Proposed Solution

Remove custom aria-roledescription="Navigation List Tree" from tree items

Proposed Alternatives

No response

Organization

SAP UDEx

Additional Context

No response

Priority

Low

Privacy Policy

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

Activity

  1. GDamyanov commented on Oct 30, 2026

    @GDamyanov
    Contributor

    Hello @UI5/ui5-team-ctr-rod,

    Could you check this issue. It is a valid accessibility concern in packages/fiori/src/SideNavigation.ts. The aria-roledescription="Navigation List Tree" is applied via ariaRoleDescNavigationList to the tree
    list elements in SideNavigationTemplate.tsx (lines 23, 40, 61, 69). According to WAI-ARIA spec, aria-roledescription should only be used to clarify roles that don't convey their purpose clearly — tree and treeitem are well-understood roles, so overriding them adds no value and can confuse screen reader users.

    Thanks & Kind Regards,
    Georgi

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