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
7000.0.0a27
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|https://github.com/Unity-Technologies/a11y-public-sample])
# Call [AssistiveSupport.notificationDispatcher.SendScreenChanged|https://docs.unity3d.com/6000.0/Documentation/ScriptReference/Accessibility.IAccessibilityNotificationDispatcher.SendScreenChanged.html] or [AssistiveSupport.notificationDispatcher.SendLayoutChanged|https://docs.unity3d.com/6000.0/Documentation/ScriptReference/Accessibility.IAccessibilityNotificationDispatcher.SendLayoutChanged.html] with a valid [AccessibilityNode|https://docs.unity3d.com/6000.0/Documentation/ScriptReference/Accessibility.AccessibilityNode.html] to focus right after resetting the [AssistiveSupport.activeHierarchy|https://docs.unity3d.com/ScriptReference/Accessibility.AssistiveSupport-activeHierarchy.html] (for example, when changing scenes)
# Subscribe to [AssistiveSupport.nodeFocusChanged|https://docs.unity3d.com/6000.0/Documentation/ScriptReference/Accessibility.AssistiveSupport-nodeFocusChanged.html]
# 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|https://docs.unity3d.com/6000.0/Documentation/ScriptReference/Accessibility.AssistiveSupport-nodeFocusChanged.html] 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|https://docs.unity3d.com/6000.0/Documentation/ScriptReference/Accessibility.AssistiveSupport-nodeFocusChanged.html] 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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment