QuantumBadger / QuantumBadger/RedReader

Allow user customization of the order of accessibility actions and elements in the accessibility descriptions of posts and comments

Open
#987 0 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

While RedReader's current order of accessibility actions and post/comment description elements aims to create a reasonable standard, some users might have slightly different preferences (such as opting to hear the subreddit or domain before everything else, etc.), so making the order customizable would improve the UX for these users. Additionally, it should be possible to remove actions/elements.

A few thoughts:

  • I think we'll need to create a universal content description for posts/comments, without putting some elements into a title and others into a subtitle. One "accessibility string" containing all elements would allow for complete free user customization.
  • To maintain parity with current behaviour, assuming the user has not edited the post/comment description order, enabling concise mode should automatically move "embellishments" before the post title. We shouldn't do this though if the user has customized the order to avoid clobbering user prefs.

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

The issue names no files, tests, or entry points. Start by locating the existing accessibility descriptions for posts and comments, then define how users can reorder or remove elements while preserving customized preferences and the stated concise-mode behavior.

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
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.