Bug 578816 - TreeViewerFocusCellManager with Screenreader: only first column read
Summary: TreeViewerFocusCellManager with Screenreader: only first column read
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.24   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-18 03:12 EST by Julia Reuss CLA
Modified: 2022-02-18 03:12 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julia Reuss CLA 2022-02-18 03:12:09 EST 
We use a TreeViewer with many columns (> 5) - therefore the keyboard navigation over its columns is enabled. We utilize the TreeViewerFocusCellManager to navigate through the columns of a single row with arrow keys left/right.

When navigating over a row the corresponding column cells are selected as expected - But when using typical screenreaders (e.g. Jaws/Narrator) only the first column of each row is read.
Symptom: independent of the selected column the screenreader only reads the first column cell (Jaws, Narrator), the selection frame of the screenreader remains on the first column entry of the row when using the arrow keys (Narrator).

Similar behavior also occurs in case of a TreeViewerEditor, but when starting to edit the cell the focus of the screenreaders is updated and the editable cell is read correctly. Key difference here seems to be the updateFocusCell​ Method.

Is a known issue? 
Is the usage of column navigation for TreeViewer in context of accessibility generally not supported?