Search Issue Tracker
By Design
Votes
0
Found in
2023.3.0b1
Issue ID
UUM-59722
Regression
No
[Screen reader] Adding elements the focus jumps to the top of the UI Hierarchy
How to reproduce:
- Download and open [https://github.cds.internal.unity3d.com/julia-perdigueiro/a11y-screen-reader-sample]
- Enter Play Mode
- Open Accessibility Hierarchy
- Click Add Node
Expected result: Screen reader returns focus to Add Node button
Actual result: Focus jumps to the top of the Hierarchy
Reproduced with: 2023.3.0b1 Iphone 12 mini
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note:
The test app is recreating all the accessibility nodes when new ones are added, therefore the focus moves back to the top of the screen. We'll be updating the behavior soon to refresh the hierarchy instead of recreating it each time something changes, but that's also on the test app side, not exactly with the Unity code.