Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.9.1
-
None
-
Android,
iOS/tvOS/watchOS,
Description
When pushing or popping Items to/from the stack, the resulting a11y order will differ between operating systems.
This table states which element will receive the screen reader's focus after StackView actions:
| OS | push | pop |
|---|---|---|
| iOS | Window.title [1] | pop button [2] |
| Android | depth text | depth text |
| macOS | dangling "old" push button [3] | dangling "old" pop button [3] |
| Windows (Tab Navigation) | "Unknown" [4] | "Unknown" [4] |
| Windows (NVDA) | dangling "old" push button | Stuck on "old" pop button |
Notes:
[1] Window.title is the last element in the a11y chain, users will have to traverse backwards to understand the new view.
[2] The "pop page (...)" button is focused but VoiceOver starts reading the old Accessible.name value before aborting and reading the new one.
[3] "Dangling" means VoiceOver will still read the Accessible.name value from the previous Stack Item. After moving to the next a11y item the order is confusing (new push button > new pop button), the top-most "depth text" is only reached when going backwards.
[4] The "Unknown" element is caused by QTBUG-134138.
At a first glance the behavior from Android makes most sense as TalkBack will start with the "depth text" which is the top-most Item of the view.