palantir/blueprint

Blueprint table elements do not use correct roles

Open

#6224 opened on Jun 14, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
Domain: accessibilityP1Package: tableType: enhancementhelp wanted

Description

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

Contributor guide

Tech stack
reacttypescript
Domain
accessibilityfrontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
knowledge of ARIA rolesfamiliarity with Blueprint components
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
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.