Hey, does your roadmap have Accessibility improvements or configurability on the roadmap?
We have a need to fulfill the requirements of European Accessibility Act (Directive (EU) 2019/882) and we have noticed that currently the Paywalls don’t seem to offer good support for accessibility.
Recently the ability to disable font scaling in Paywalls, did fix one of our issues. Otherwise we have been able to work around it by adjusting our paywall and doing small hacks and adjustments to them in order to improve the Accessibility.
So I was wondering if you have Accessibility improvements coming in the roadmap and when might these improvements be scheduled?
Solved
Accessibility configuration support in Paywalls?
Best answer by Tarek
Hey
This is Tarek from the RevenueCat Developer Support team, thanks for reaching out and for the thoughtful question. Happy to help here.
Accessibility is on our radar, and we're glad to hear the recent option to disable font scaling already solved one of your issues.
We don't currently have a public roadmap for accessibility improvements to share. So I can't promise specific features on specific dates. What I can do is share where things stand today and how we're approaching it.
A few things that are already in place for Paywalls:
- Paywalls are rendered natively on each platform, so they work with the system screen readers (VoiceOver on iOS and TalkBack on Android).
- You can set alt text on image components in the Paywall editor.
- The font scaling control you mentioned is part of this same effort to give you more accessibility configurability.
Of course we always strive to keep improving incrementally.
One thing worth keeping in mind is that a good portion of accessibility behavior, like screen readers and system font scaling, is handled at the OS and native layer, so part of meeting EAA requirements also depends on the host app and OS alongside the paywall itself.
One useful next step would be for you to share the specific accessibility gaps that are blocking you for EAA. Concrete examples (a component that isn't announced well, a label that reads incorrectly, missing configurability somewhere) let us file and prioritize them as targeted feature requests rather than a broad "accessibility" item.
Let me know if that makes sense and if there's anything else I can help with!
Have an excellent day.
Best regards,
+6Hey
This is Tarek from the RevenueCat Developer Support team, thanks for reaching out and for the thoughtful question. Happy to help here.
Accessibility is on our radar, and we're glad to hear the recent option to disable font scaling already solved one of your issues.
We don't currently have a public roadmap for accessibility improvements to share. So I can't promise specific features on specific dates. What I can do is share where things stand today and how we're approaching it.
A few things that are already in place for Paywalls:
- Paywalls are rendered natively on each platform, so they work with the system screen readers (VoiceOver on iOS and TalkBack on Android).
- You can set alt text on image components in the Paywall editor.
- The font scaling control you mentioned is part of this same effort to give you more accessibility configurability.
Of course we always strive to keep improving incrementally.
One thing worth keeping in mind is that a good portion of accessibility behavior, like screen readers and system font scaling, is handled at the OS and native layer, so part of meeting EAA requirements also depends on the host app and OS alongside the paywall itself.
One useful next step would be for you to share the specific accessibility gaps that are blocking you for EAA. Concrete examples (a component that isn't announced well, a label that reads incorrectly, missing configurability somewhere) let us file and prioritize them as targeted feature requests rather than a broad "accessibility" item.
Let me know if that makes sense and if there's anything else I can help with!
Have an excellent day.
Best regards,
Hey great to hear that you are aware of the issues. For now we have been able to play around most of the Accessibility issues with adjustments on our Paywall.
After adjusting our paywall with Accessibility in mind, we found at least these two components in RevenueCat SDK that would hopefully be improved
- Carousel component doesn’t seem to have any Keyboard control support.
- Icon component doesn’t have any content description, nor can you place any content description for it in the Paywall editor. So a button that is only an icon like X doesn’t get read out by talkback. For this there was a fix to add 1 font size text inside the same button.
+6Hey,
Thank you for this, I reported it immediately to our engineering team!
Best,
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.