Use semantic nodes as accessibility containers when they are not accessible#3038
Merged
Andrei Salavei (ASalavei) merged 3 commits intoMay 13, 2026
Conversation
…rd-access-coordinate # Conflicts: # compose/ui/ui/src/uikitInstrumentedTest/kotlin/androidx/compose/ui/test/AccessibilityTestNode.kt
Vladimir Mazunin (mazunin-v-jb)
approved these changes
May 11, 2026
|
|
||
| override val accessibilityContainerType: UIAccessibilityContainerType | ||
| get() = when { | ||
| semanticsNode.canBeAccessibilityElement() -> UIAccessibilityContainerTypeNone |
There was a problem hiding this comment.
Can be removed, I guess, since else handles this case
There was a problem hiding this comment.
No, the issue that traversal groups also can be accessibility focusable. For these elements we're creating 2 elements - container and semantics. Container must have UIAccessibilityContainerTypeSemanticGroup to support iOS navigation, but the semantics element should not in this case.
Vendula Švastalová (svastven)
approved these changes
May 12, 2026
Vlad Konstantinov (Kpotko)
added a commit
that referenced
this pull request
May 15, 2026
…y are not accessible (#3038) (#3043) Simplify accessibility tree hierarchy: use AccessibilityNode.Semantics also as containers when they are not accessible. Fixes https://youtrack.jetbrains.com/issue/CMP-10154/iOS-A11y.-Full-Keyboard-Access.-Element-selection-is-shifted ## Release Notes ### Fixes - iOS - Fix elements selection with Full Keyboard Access
Sajid Ali (sajidalidev)
pushed a commit
to sajidalidev/compose-multiplatform-core-tvos
that referenced
this pull request
May 18, 2026
…ssible (JetBrains#3038) Simplify accessibility tree hierarchy: use AccessibilityNode.Semantics also as containers when they are not accessible. Fixes https://youtrack.jetbrains.com/issue/CMP-10154/iOS-A11y.-Full-Keyboard-Access.-Element-selection-is-shifted ## Release Notes ### Fixes - iOS - Fix elements selection with Full Keyboard Access
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Simplify accessibility tree hierarchy: use AccessibilityNode.Semantics also as containers when they are not accessible.
Fixes https://youtrack.jetbrains.com/issue/CMP-10154/iOS-A11y.-Full-Keyboard-Access.-Element-selection-is-shifted
Release Notes
Fixes - iOS