Hi All, We just released an app built using SAB, and a second one is in review. Everything seems to be going fine, but we get lots of accessibility warnings in the pre-launch report. We cannot figure out how to address them using SAB. Here are some examples:
Content labeling
“This item may not have a label readable by screen readers.”
“This item’s width is 46dp. Consider making the width of this touch target 48dp or larger.”
(looks the same as the item above, one of the bottom bar buttons)
@asa I don’t think you need to worry too much about these warnings. They are automated tests by Google and are probably useful for developers who built their own apps from scratch. But since you are using SAB, a software tool that creates the app for you, just ignore them. Unless these warnings make sense to you and you feel that the SAB developers should address some of them. Then you can report them as bugs or as feature requests.
The first of those errors involve blind users being able to navigate the app. For example, if they touch the highlighted button will it say “this is allows you to make the recording repeat”.
In an ideal world SAB would support that, but it’s probably an extremely small number of users in our minority language environments who can actually use blind features of Android. Not enough for the team to support it, much less for us to localize the explanations. (For that matter, most screen readers to text-to-speech. I don’t know if that sort of thing would actually work in minority languages or not.)
Thank you, @mjames. Yeah, Tibetan can be challenging when it comes to localization. Some of the issues (like tap targets that are too small) would be good updates across the board.
