Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭 适合新手
#14,232 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
72/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript

调研方向

在 Side Navigation 组件中搜索 aria-roledescription="Navigation List Tree",并阅读树项实现及其无障碍测试。从树项中移除自定义描述,然后运行相关的 Side Navigation 测试。当树项不再覆盖标准角色描述且测试通过时,即完成。

由索引模型根据 Issue 内容生成。

描述

bug Medium Prio TOPIC RD
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.
主要语言
TypeScript
星标
1.8k
派生
290
平均合并
3 天 12 小时
30 天内合并 PR
54

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

UI5/webcomponents 的其他 Issue

查看 UI5/webcomponents 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。