[Popover] - allow its sparing usage for interactive content
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 35/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 停滯
- 技術堆疊
- react, typescript
研究方向
從 packages/react-core/src/components/Popover/Popover.tsx 開始,特別檢視第 456 行附近對 aria-describedby 的使用,並審閱 Popover 文件及連結的 ARIA 指南。確定互動內容的無障礙需求,並將完成定義為:Popover 支援所要求的使用情境,同時不會使其內容變得無法存取。
由索引模型根據 Issue 內容生成。
描述
Is this a new component or an extension of an existing one?
And extension/adjustment of Popover
Describe the feature
Allow interactive content for using it in scenarios where other components such as Modal, Menu, or Dropdown, don’t quite fit the use case.
As an example, see the screenshots below of rough prototypes for an interface that allows users quick access to available Wi-Fi networks and keyboard layout from a top toolbar.
One concern I have is that the Popover component internally uses the aria-describedby attribute, which I believe makes the interactive content inaccessible. From my limited understanding of accessibility, and after reviewing MDN's documentation, it seems that using aria-details might help.
The
aria-describedbyproperty is appropriate when the associated content contains plain text. If the content is extensive, contains useful semantics, or has a complex structure requiring user navigation, use aria-details instead.aria-detailsallows assistive technology users to visit the associated structured content and provides additional navigation commands, making it easier to understand the structure, or experience the information in smaller pieces.
Are there visuals for this feature? If applicable, please include examples for each state and for varying widths
See these rough prototypes
| Available Wi-Fi networks | Localization options |
|---|---|
Any other information?
Originally posted as a discussion in #11745, but later realized that a feature request issue might be a better place for it.
- 主要語言
- TypeScript
- 星號
- 862
- 分支
- 392
- 平均合併
- 4 天 8 小時
- 30 天內合併 PR
- 9
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
patternfly/patternfly-react 的其他 Issue
-
PF Team
難度 2/5 1-3 小時 新手友好度 68/100
patternfly/patternfly-react#12651 ·
-
難度 2/5 1-3 小時 新手友好度 78/100
patternfly/patternfly-react#12637 ·
-
PF Team
難度 2/5 1-3 小時 新手友好度 72/100
patternfly/patternfly-react#12617 · 1 則留言 ·
-
PF Team
難度 2/5 1-3 小時 新手友好度 68/100
patternfly/patternfly-react#12610 · 1 則留言 · 1 個 reaction ·
-
難度 2/5 1-3 小時 新手友好度 68/100
patternfly/patternfly-react#12600 ·
查看 patternfly/patternfly-react 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 74/100
-
security
難度 2/5 1-3 小時 新手友好度 72/100
IBM/node-sdk-core#373 ·
-
e2e-failure ready-to-code
難度 2/5 1-3 小時 新手友好度 86/100
-
bug
難度 2/5 1-3 小時 新手友好度 74/100
-
chore
難度 2/5 1-3 小時 新手友好度 88/100