TeamAmaze / TeamAmaze/AmazeFileManager

Improve the List View for TalkBack Users

Open
#4,166 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Accessibility Issue-Bug
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

Is your feature request related to a problem? Please describe.
While navigating the file list with TalkBack, users have to swipe thrice to get from one file or folder to another. For every file, TalkBack users hear the file name, "Select button", and the context menu for that file. This makes navigating the file list a bit slower and harder. Also, the context menu button has a wrong label, "Properties".

Describe the solution you'd like
Group the filename with the controls select and context menu (https://developer.android.com/guide/topics/ui/accessibility/principles#content-groups) and add the select and context menu buttons to accessibility actions (https://developer.android.com/guide/topics/ui/accessibility/principles#accessibility-actions) this will streamline navigation for TalkBack Users.
Rename the "Properties" (context menu) button to "Show file actions" (https://developer.android.com/guide/topics/ui/accessibility/principles#label-elements).

Describe alternatives you've considered
None

Additional context
None

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

Locate the Android file-list item UI and inspect how each filename, select control, and context-menu control is exposed to TalkBack. Group the item content, expose the controls as accessibility actions, and rename the context-menu label to "Show file actions"; verify that TalkBack reaches each file with fewer swipes and announces the new label.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
accessibility, frontend, mobile
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.