-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessibility / a11y TalkBack descriptions #79
Comments
The problem is that this library renders the widget to an image, so there are no Android views to add I assume we can implement it in a similar way like the buttons, add an empty I'll take a look when I have some free time. |
Thanks for the response. Aha - yeah that sounds like a great plan, FrameLayouts would very likely do the trick. |
First up, thanks for this really interesting library! It's a challenging problem and your solution is neat.
Do you have any thoughts on how widgets using this could be made accessible with TalkBack?
The ideal case would be that individual components could have
contentDescription
etc props.Failing that a reasonable fallback would be the ability to set a
contentDescription
on the widget root itself - that way a TalkBack user who taps anywhere on the widget could hear something like 'Music Widget. Currently playing all along the watchtower' etc.For reference, at present when I tap my 'hello world' widget in TalkBack it reads out:
Unlabelled, double-tap to activate labels available use tap with three fingers to view
Thanks!
The text was updated successfully, but these errors were encountered: