-
Hello, I'm encountering an issue with the accessibility of TabPanel content when using Android's Talk Back feature. Specifically, when the content of a TabPanel consists only text, Talk Back seems unable to focus and read the content. However, if the TabPanel includes interactive components (such as links or input fields) alongside the text, Talk Back is able to focus on and read the content without issue. I'm wondering if this behavior is a bug or needs some accessibility options or attributes to be enabled for text-only TabPanel content to be accessible with Talk Back. You can reproduce at the following URL: Any guidance or recommendations on how to ensure that all content within a TabPanel, regardless of whether it includes interactive elements, is accessible with Talk Back would be greatly appreciated. Thank you for your time and assistance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Hey, thanks for bringing this up! This definitely seems like a bug so would you mind creating an issue for this so we can keep track of it? I verified it myself and also tried TalkBack on this WAI example where it also did not announce the content of the TabPanel. It might be a TalkBack bug but regardless, it would be good to find a workaround and investigate a bit further. |
Beta Was this translation helpful? Give feedback.
Hey, thanks for bringing this up! This definitely seems like a bug so would you mind creating an issue for this so we can keep track of it? I verified it myself and also tried TalkBack on this WAI example where it also did not announce the content of the TabPanel. It might be a TalkBack bug but regardless, it would be good to find a workaround and investigate a bit further.