Repository navigation
Conversation
rteyssandier
force-pushed
the
feat/accessibility-talkback-remote
branch
from
October 30, 2026 19:32
5de6443 to
b14f533
Compare
rteyssandier
marked this pull request as ready for review
October 30, 2026 22:15
rteyssandier
force-pushed
the
feat/accessibility-talkback-remote
branch
from
November 2, 2026 08:22
78d2b1e to
63ff9a3
Compare
This branch has not been deployed
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
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.
Description
Replaces the accessibility focus bar of the desktop app with a floating TalkBack remote, and adds an "activate" action (the TalkBack double tap).
Desktop
AccessibilityRemote: a card that floats over the Accessibility screen. It shows the focused element (class, title, bounds, position) and has these buttons:ActivateAccessibilityFocusedNodeUseCase, wired through the repository and the to-device data source.AccessibilityFocusedNodeCardis removed).Protocol / SDK
Activatein bothProtocol.kt, documented inprotocol/accessibility.md.ACTION_CLICKon a View, or through the Compose accessibility node provider), then replies withFocusedNode. Other platforms reply with an emptyFocusedNode.Checks
:accessibility:jvmTest,:accessibility-no-op:compileKotlinJvm,:accessibility:compileAndroidMain:composeApp:compileKotlinDesktop,:domain:allTests,:data:core:allTests,:mcp:allTests,ktlintCheck/gemini review