palantir/blueprint

Blueprint table elements do not use correct roles

Open

#6,224 建立於 2023年6月14日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)TypeScript (20,263 star) (2,167 fork)batch import
Domain: accessibilityP1Package: tableType: enhancementhelp wanted

描述

You can use VoiceOver on Mac on https://blueprintjs.com/docs/#table/features to trivially see this - the elements don't correctly declare e.g. table, row, cell, etc. roles so that the screenreader is unable to correctly read each row. Instead, each cell gets read one at a time

貢獻者指南

技術棧
reacttypescript
領域
accessibilityfrontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
knowledge of ARIA rolesfamiliarity with Blueprint components
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
85
研究方向
Examine the Blueprint Table component source code (likely in `packages/table/src/`). The issue states that rows and cells lack correct `table`, `row`, and `cell` ARIA roles. Look at how `<Table>` renders its internal elements (e.g., in `tableBody.tsx` or similar) and add the necessary roles. Test the fix using VoiceOver on macOS to ensure each row is read correctly. Refer to the issue description and the Blueprint accessibility docs for guidance.