Thank you for reaching out about VoiceView accessibility on Vega!
I’ve tested a solution for making non-focusable text and images readable by VoiceView, and I’m happy to share that wrapping non-focusable elements in a TouchableOpacity with activeOpacity={1} works effectively.
The Solution:
For any Text or Image component that you want VoiceView to read but don’t want to be interactive, wrap it in a TouchableOpacity with these properties:
I’ve attached a complete App.tsx (3.7 KB) file demonstrating this pattern with:
Header text that VoiceView reads
Instructional text at the bottom
Images with accessibility labels
I’ve tested this approach on Vega devices with VoiceView enabled and it’s working as expected.
Let me know if you have any questions or need further clarification!
Thank you your response.
I do not think this is the right solution.accessible makes it focusable and then you have to move DPAD around.I would like voice view to read those texts without pressing DPAD.As soon as the page loads, I wanna read specific text or image, without initial focus on that non focusable element.
I figured that out.This has a problem, if I am using aria-label property in any element in my react function and its receives focus, there is no guarantee that, AccessibilityInfo’s announcement will be done first. Thanks.
I’m the dev from the accessibility team. Thanks @amen for offering options for the 3p developers to explore. But using announcement API is not the optimal solution.@Rishabh_Ritweek For your usecase, you can set accessibility role “header” on the static text/image component. That way makes VoiceView automatically speaks it when the page loads.
Please find the guidance in KeplerScript Accessibility API reference: