ObjectPage: tabIndex=0 set on first ObjectPageSection even for single-section layout causing WCAG 2.1.1 keyboard accessibility violation
维护者通常 1 天内回复
评估
这个 Issue 还没有评估数据。
描述
Bug Description
When ObjectPage is used with a single ObjectPageSection, the component sets tabIndex=0 on that section after mount, making a non-interactive region focusable via the keyboard Tab key.
The library already handles the single section case — hasOnlySingleSection is calculated and used to hide the tab navigation bar. However, the tabIndex effect does not check hasOnlySingleSection and sets tabIndex=0 unconditionally. This is the roving tabindex pattern designed for navigating between multiple sections, which has no purpose when there is only one section.
This causes a WCAG 2.1.1 violation — a non-interactive
element appears as a wasted Tab stop in the keyboard tab order.Affected Component
ObjectPage, ObjectPageSection
Expected Behaviour
When there is only one ObjectPageSection, the section should not be added to the keyboard Tab order. The tabIndex should remain -1 since there are no other sections to navigate between.
Isolated Example
No response
Steps to Reproduce
- Render an ObjectPage with a single ObjectPageSection
- Open the page in a browser
- Open DevTools and inspect the element with data-component-name="ObjectPageSection"
- Press Tab to navigate through the page
- Observe that the element receives keyboard focus and has tabindex="0" set on it
Log Output, Stack Trace or Screenshots
No response
Priority
None
UI5 Web Components Version
2.27.2
Browser
Chrome
Operating System
No response
Additional Context
No response
Organization
SAP Labs
Declaration
- I’m not disclosing any internal or sensitive information.
- 主要语言
- TypeScript
- 星标
- 541
- 派生
- 114
- 平均合并
- 21 小时 26 分钟
- 30 天内合并 PR
- 82
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
UI5/webcomponents-react 的其他 Issue
-
难度 5/5 一周以上 新手友好度 20/100
UI5/webcomponents-react#8529 ·
维护者通常 1 天内回复
-
Design Pending SAP SF
难度 3/5 1-2 天 新手友好度 45/100
UI5/webcomponents-react#8158 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
a11y Design Pending
难度 3/5 1-2 天 新手友好度 35/100
UI5/webcomponents-react#7582 · 4 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 42/100
UI5/webcomponents-react#7546 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
UI5/webcomponents-react#6727 · 15 条评论 ·
维护者通常 1 天内回复
查看 UI5/webcomponents-react 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
lyswhut/lx-music-desktop#3026 ·
-
area: ci type: test
难度 2/5 1-3 小时 新手友好度 65/100
schlessera/brain-kit#2769 ·
维护者通常 1 天内回复
-
Read a vector index's quantization back on Neo4j 2026.10, which reports vector.quantization.type未关闭
难度 2/5 1-3 小时 新手友好度 78/100
liberation-data/drivine#231 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
alveusgg/alveusgg#2502 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复