Samsung Keyboard Voice Input vs TalkBack — Serious Accessibility Conflict
(Topic created on:
18/02/2026 12:39 PM
)
573 Views
Labels:
D
Dick66
First Poster
last edited
18/02/2026 12:39 PM
I would like to report a compatibility issue between Samsung Keyboard voice input and the TalkBack screen reader.
When using voice input with Samsung Keyboard, there is a clear conflict with TalkBack’s speech output. Specifically, after TalkBack finishes speaking, I must wait approximately 4 seconds before voice input can be activated and used normally.
If I try to start voice input immediately after TalkBack stops speaking, the speech input is not properly recognized or executed.
This issue is not caused by user operation speed, but appears to be a compatibility problem between the two functions, which significantly affects usability and efficiency for accessibility users.
I have recorded a demonstration video that clearly reproduces the issue.
My main request is to have this investigated as a technical malfunction so the root cause can be identified and resolved, with the goal of improving the accessibility experience.
Dick
JordanS
Moderator
last edited
26/02/2026 11:01 AM
Recreating this issue with a fresh reproduction video, then submitting as an error report would be the best way to get this investigated by our Research and Development team.
Best to submit the report within 10 minutes of reproducing. Long press the Samsung Members app > Error report > Select your device and category > Write a full description of the behaviour > Attach your footage using the paperclip icon > Down at the bottom, select Attach System Log Data > Send > Keep the app open and the screen awake while the logs compile for sending.
0 likes
zaraaron
Explorer
last edited
29/09/2026 09:47 PM
This sounds like a genuine accessibility issue, especially with the delay happening consistently after TalkBack finishes speaking. The video should make it easier to reproduce and investigate. Hopefully Samsung can check the interaction between the keyboard voice input and TalkBack rather than treating it as a user setting issue.
0 likes