rive-app / rive-app/rive-android
a11y: Support for Accessibility Settings
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 538
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
Description
<-- A clear and concise description of what the problem is. -->
I have looked into Rive docs and could not find a way to properly provide a11y description when using Compose (usually the AndroidView containing the Rive animation is skipped by Talkback) and it will also not respect animation speed set up in the system.
Expected behavior
<-- A clear and concise description of what you expected to happen. -->
- Properly support Talkback and ways to set content description or document that we should disable it.
- Respect the animation speeds, enabling/disabling set on the system.
Workaround
To work around the talkback issue I have wrapped the AndroidView containing the Rive Animation into a Box and set the semantics into it. Example:
Box(
modifier = modifier
.semantics { contentDescription = "description" },
contentAlignment = Alignment.Center,
) {
AndroidView(
modifier = Modifier.fillMaxSize(),
factory = {
RiveAnimationView.Builder(it)
.setResource(animationResource)
.build()
},
)
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the Compose integration that wraps RiveAnimationView.Builder in AndroidView, then inspect how the view interacts with Compose semantics and Android animation settings. Verify the result with TalkBack and system animation-speed and enable/disable settings; done means content descriptions are exposed and those settings are respected or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- accessibility, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100