Description
On Android, when using a CarouselView that is scroll-only (users cannot select items, only swipe horizontally), TalkBack still announces “double tap to activate” when the carousel receives focus.
This is confusing for users when there is no action to perform — in this case the carousel is purely for scrolling.
I have attempted to use a custom handler for the CarouselView to modify its native "clickable" properties. However, nothing I have tried so far affects the double-tap behavior. I should be able to override or remove this message.
I have attached a repository to replicate this issue.
Steps to Reproduce
- Activate talkback
- On the home screen navigate to open carousel view
- Select the carouosel with talkback and navigate
- After reading out the actions "double tap to activate" will be read
Link to public reproduction project repository
https://github.com/Croppo/MauiReproductionApp
Version with bug
9.0.90 SR9
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
Description
On Android, when using a CarouselView that is scroll-only (users cannot select items, only swipe horizontally), TalkBack still announces “double tap to activate” when the carousel receives focus.
This is confusing for users when there is no action to perform — in this case the carousel is purely for scrolling.
I have attempted to use a custom handler for the CarouselView to modify its native "clickable" properties. However, nothing I have tried so far affects the double-tap behavior. I should be able to override or remove this message.
I have attached a repository to replicate this issue.
Steps to Reproduce
Link to public reproduction project repository
https://github.com/Croppo/MauiReproductionApp
Version with bug
9.0.90 SR9
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output