Search Issue Tracker
Fixed
Fixed in 6000.0.50f1, 6000.1.5f1, 6000.2.0b4, 6000.3.0a1, 7000.0.0a27
Votes
1
Found in
6000.2.0a9
Issue ID
UUM-103808
Regression
No
[Android] AssistiveSupport.nodeFocusChanged is not called after SendScreenChanged or SendLayoutChanged
Steps to reproduce:
- Open a project that uses the Accessibility module (such as Unity-Technologies/a11y-public-sample)
- Call AssistiveSupport.notificationDispatcher.SendScreenChanged or AssistiveSupport.notificationDispatcher.SendLayoutChanged with a valid AccessibilityNode to focus right after resetting the AssistiveSupport.activeHierarchy (for example, when changing scenes)
- Subscribe to AssistiveSupport.nodeFocusChanged
- Build & run on an Android device
- Observe the result of the aforementioned call
Actual results: The screen reader announces the node passed in the call, but does not draw its focus indicator around it; AssistiveSupport.nodeFocusChanged is not called for the newly focused node.
Expected results: The screen reader announces the node passed in the call and draws its focus indicator around it; AssistiveSupport.nodeFocusChanged is called for the newly focused node.
Reproducible with versions: Unity 6000.2.0a9
Tested on (OS): Android 14
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Progress indicator in Meta Quest Build Profile configuration is barely visible
- Slightly transparent objects disappear completely in Web Player when using RenderGraph
- Visual Scripting Components are hidden behind a throbber when Multiplayer Play Mode is running with at least one local instance
- Video Player does not throw an error when playing a video with unsupported encoding settings
- Errors indicating that TMP Extras were not Imported logged when opening the Render Pipeline Converter Window while in Play Mode
Add comment