Controls improperly labeled for screen reader accessibility

[dangero2000]

What happened?

I'm visually impaired and use the TalkBack screen reader. Many buttons have no content labels, and it's guess work finding out what everything does. Examples include the search and cast buttons, as well as other buttons in the creators tab. To fix this, you can use the android:contentDescription attribute. For buttons that change status when tapped, like the video player's play/pause button, you can use the View#setContentDescription(CharSequence contentDescription) attribute. I'm not a developer. I got this information from the Android Accessibility Help page. I also used Google's Accessibility Scanner application, which will scan the app for issues and report them to you. That's how I found the help article. You can find Accessibility Scanner on the Play Store, and it's pretty easy to use. Android Accessibility Content Labels Help Page: https://support.google.com/accessibility/android/answer/7158690?hl=en#zippy=%2Cview Accessibility Scanner on Google Play Store: https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.auditor&hl=en_US

Grayjay Version

253

What plugins are you seeing the problem on?

All

Plugin Version

12

When do you experience the issue?

• [ ] While logged in
• [ ] While logged out
• [X] N/A

Relevant log output

No response

[dangero2000]

A few updates:

• Shortly after submitting my issue, I discovered this issue which was quite similar to mine. Unfortunately, it was given the enhancement and low priority labels. Accessibility is not an enhancement, nor should it be dubbed low priority. I am willing to pay an extra price of Futo's choosing for the app in order to incentivize razing priority for this issue from low to high.
• I made a topic about this on Futo's Zulip server as well.
• Someone posted another issue about keyboard shortcuts. While it is an important accessibility fix that should be addressed, I feel it is important to point out that making your app completely usable via a keyboard does not necessarily make it screen reader accessible. Screen readers for mobile devices are designed to work primarily with touch screens and not keyboards. That being said, it is still an important fix that should be considered.

[dangero2000]

I appreciate your response to my issue, and I apologize for any potential misunderstandings. That being said, I do believe that based on your description of the labels, the bug and high priority labels can apply here as well. After all, it could be said that the entire app is rendered unusable for people such as myself due to the present bugs. I would still be happy to pay extra money for this, as I am happy to support both Futo and the GrayJay app.