QuantumBadger / QuantumBadger/RedReader

Screen reader accessibility suggestion, easier post navigation

Open
#1,002 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
2.7k
Forks
527
Avg merge
20d 10h
Merged PRs (30d)
3

Description

Hi there
I will describe how I preferably like to scroll posts so we could figure a solution for it.
IT would be great if each post was in one line, so swiping left or right with talkback would then scroll to the next/previous post, then, entering the post title would enter the post content/comments section, regardless of it being a text post or a media post.
The first part of my suggestion would be prefer by every screen reader user, but the second one could be not, even though I personally feel like it would be the best option. I generally would love to enter a post first to read its text content if it exist and if not inside the post I would click on the url/media if it is there and could scroll down to comments if wanted.

Now I realize you could go to appearance and untick "show comments button", which makes posts and post information into one line but I couldn't then enter the post comments if it is a url or media, only if it is a text based post, I could then enter it, see the posts and comments.
Then I realized you could go to behavior and tick the "post title opens comments" which is exactly what I wanted! but it makes posts into two lines again, one being the title and one being post information

Could we have an option of posts being in one line and entering them would enter the post content/comments itself?
Alternatively, a button in accessibility actions menu to view comments on posts, this would be awesome as well, though a caveat is that text posts do not need this but media posts do, so we have to act based on the post flare if the subreddit is organized.
Option 1 is very appealing to me personally and comfortable. I could enter a post and then view the media/url if I wanted.

Once again thanks for this app I've moved from IOS to Android after 10 years and this is one of the most accessible apps I have encountered so far.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the post display behavior controlled by “show comments button” and “post title opens comments,” along with the accessibility actions menu. Compare the two proposed interaction options for text, URL, and media posts, then define a consistent behavior and verify that screen-reader navigation reaches post content and comments as intended.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
accessibility, mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.