PhilippC / PhilippC/keepass2android
[BUG] Accessibility when entering passwords using a screen reader
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
Checks
- I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
When I type my password using the screen reader, the input doesn't appear.
When I double-tap, the input should appear, but it doesn't work.
I'm using TalkBack and Android 14.
Describe what you expected to happen:
The keyboard should be displayed so I can type my password.
This it at master password
What version of Keepass2Android are you using?
1.14-r4
Which version of Android are you on?
14
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Reproduce the issue on the master-password screen using TalkBack on Android 14 with Keepass2Android 1.14-r4, first checking whether double-tapping the password input displays the keyboard. Done means the keyboard appears and the password can be entered through the screen reader. No source file or test is identified in the report, so the affected UI entry point must be located first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- accessibility, mobile, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100