Skip to content

a11y — Investigate issues with screen readers on Windows and macOS #756

Open
@rock3r

Description

When testing screen reader support in the standalone sample app on Windows (NVDA screen reader) and macOS (using VoiceOver), these issues were identified by the IJ UI team.

These need to be looked into further, and then we determine:

  • It's a Jewel issue (e.g., wrong Role) -> File a bug and fix in Jewel
  • It's a CMP issue -> File a CMP bug
  • It's a missing API (e.g., missing Role) -> File a Jetpack Compose bug

The expected output of this task is a comprehensive list of filed/fixed issues.

Radio buttons

Checkboxes

Dropdowns and combo boxes

Trees/SLC

  • Tree items are not announced when using up/down arrows
  • When focus is on the tree, Tab key should move focus to the next component instead of the next tree node

Sliders

  • Slider doesn't announce value change when using left/right arrows
    Notes: Keyboard manipulation works on both stepped and continuous slider. Only the stepped slider emits sound cues when manipulated via keyboard.

Tabs

  • Tab key shouldn't move focus between individual tabs, and instead move focus to the next component
  • Left/right arrows are not moving focus between tabs
  • Initial focus goes to the close button, in editor tabs
  • No focus indication for editor tabs

Seb's note: I'm clarifying what the expected behavior is for editor tabs, since they're not focusable in Swing. I think at a minimum the close button, if it exists, should not be focusable, but tbd.

Text field/area

Banners

  • Close button and actions don't have an accessible name

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions