I'm a user of the TalkBack screen reader on Android and have noticed quite a number of existing issues that prevent me from being able to use the site to the fullest extent possible. I would have submitted them as issues on GitHub, but when I clicked the link for the source, I got a 404
The biggest issue by far is that I cannot read the contents of posts at all. Talkback will focus on the element, but it reads nothing of the text. This prevented me from reading long posts such as the FAQ, etc
On the main page, the element at the top right that tells you where you are, by default the front page, and you can tap that to get the drop-down and go to like tech, stasher, monero, Bitcoin, etc., is not read by TalkBack
When on a page with the back button in the top left corner, the back button is not read by TalkBack
On the bottom bar, the search and notification buttons are not read aloud by TalkBack
I can't seem to get to the profile picture at the bottom right hand corner with Talkback at all
I've deployed some accessibility improvements. Could you test how the site works with TalkBack now and let me know if everything has been resolved or are there any issues remaining?
Thanks,
Okay, that's a major improvement.
The replies in the notifications section still read as unlabeled, instead of actually letting you read the text of them, and I'm unable to access the upvote button, but can access the downvote button.
Could you please test again and report back? deployed some more improvements to attempt to address the remaining issues you reported.
In my tests I can now access the upvote button, my talkback still can't read the notifications, but let me know if its any different for you.
This is correct. I can now access the upvote button.
I am still unable to access the notifications, however, they have went from saying "unlabeled" to "view in context"
Edit: Similar to the upvote button, I just realized I'm not able to access the boost button either if I wanted to boost the ranking of my own post
Good! a step in the right direction. I'll address the remaining soon.
Hey, we're investigating this now and trying to see what improvements we could make. So I need a little bit more information and if you want to reply to me on Twitter instead, feel free to do so.
Can you share what device, android version, and browser you're using?
Also, how do you navigate the screen? wiping through the elements, "read from top" or just clicking on the elements themselves?
With this info we'll be able to better diagnose what the fixes should be.
lets see,
Device: Oneplus Mord N200 5G
Android:16
Browser: fennec latest (155 i think it is)
navigation is mainly done by swiping from left to right or right to left to go forward or back a single element at a time. however, i will sometimes tap on an element directly with one finger to jump to and read it firectly and may or may not use swipe navigation from that point. Something that might help would be to look up the Web Content Accessibility Guidelines as that is a standard for dealing with this kind of stuff
excellent, thanks for the info and the resource. Looking into it and hope to have a patch out sometime in the next week.
Hi, thanks for reporting this issue here. I'm not familiar with TalkBack, so I'll have to look into that and then investigate this display issue. As for the GitHub, we haven't made the repo public yet. The plan is to open source it in the next couple of days. We just want to make sure that everything is stable first and the repo is cleaned up and well documented.
Adding this to my to-do list, i'll get to it as soon as I can.
deleted by author