Expose long-press menu options as TalkBack custom actions
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 40/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- accessibility, mobile
Research direction
The issue names no files or classes, so start by finding where the home-screen item long-press menu is defined and how icons are rendered in the Kotlin source. Then check how the project already sets accessibility info on views. Done means that TalkBack's Actions menu lists the valid long-press actions for a selected icon, each one runs the same code path as the long-press menu, and the touch-and-hold menu still works.
Written by the indexing model from the issue text.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
When TalkBack is enabled, expose the actions available from an item's long-press menu as named accessibility custom actions for that home-screen item. A user should be able to focus an icon, choose Actions in the TalkBack menu, or choose the Actions reading control, and choose actions available for that item—such as app info, edit, remove, or uninstall where applicable—without performing a long-press gesture. Keep the existing touch-and-hold menu available, and only expose actions valid for the selected item.
Why do you want this feature?
Long-press gestures can be tedious for some TalkBack users, and the existing context-menu operations are not available as item actions through TalkBack's Actions menu. Providing equivalent, labeled accessibility actions would make home-screen management more accessible while preserving the current interaction for other users.
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 703
- Forks
- 85
- Avg merge
- 4d 39m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FossifyOrg/Launcher
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Launcher#453 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Launcher#447 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Launcher#446 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Launcher#456 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 3/5 1-2 days Newbie friendliness 64/100
FossifyOrg/Launcher#452 ·
Maintainers usually reply within 3 days
All issues in FossifyOrg/Launcher
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
partiql/partiql-lang-kotlin#1972 ·
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
enorm-labs/event-junkie#3027 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
libre-tube/LibreTube#8854 ·
Maintainers usually reply within 1 day