Details
-
Bug
-
Resolution: Won't Do
-
P3: Somewhat important
-
None
-
5.9.6
Description
I have a TableView with default rowDelegate
overrriden. The new rowDelegate has accessibility enabled for the selected
row. Accessible.name is set to the focused row index.
I ran the following test with MS Narrator, Visual UI Automation Verify, and
NVDA. NVDA didn't seem to work reliably for some reason, but nevertheless I
was able to reproduce the same behavior with all 3 tools. Having said that I
found it easier to reproduce with MS Narrator (Windows 10):
1. Select only first row (row 0) by either tabbing into table/row or mouse
clicking into row.
Expected result: Row is read by screen reader or selected with UI
Automation Verify. This works fine.
2. Use the down arrow to move to the next row (row 1).
Expected result: Row is read by screen reader or selected with UI
Automation Verify.
Actual result: Row selection changes, but automation focus does not, hence
second row is not read.
3. Use mouse click or tab to move the automation focus to the next row (row
1).
Expected result: Row is read by screen reader or selected with UI
Automation Verify. This works fine.
4. Use the up arrow to move to the first row (row 0).
Expected result: Row is read by screen reader or selected with UI
Automation Verify. This works fine.
5. Use the down arrow to move selection to the next few rows.
Expected result: Each row is read by screen reader or selected with UI
Automation Verify.
Actual result: Only the rows previously selected through tab or mouse are
read. The others are not.
It seems that one has to traverse the whole table either with tabs or mouse
clicks before accessibility works with the up/down arrows.