PhilippC
Issues using app with TalkBack Screen Reader.
Hello,
KeePass2Android has multiple issues when trying to use it with TalkBack enabled. For the uninitiated, TalkBack is the default Screen Reader provided by Google to enable blind/visually impaired people, like myself, to use Android and apps without having to see the screen.
I will provide a list of issues that affect the experience or straight-up prevent the app from being usable. The app currently, for me, is unusable as I cannot get any further than adding a database. I cannot unlock it at all.
Issue 1: Text boxes are difficult or impossible to find on the database unlock screen. Seems to affect the password field the most. Speaking of the unlock DB screen, When you do find the password field, it is useless as the keyboard that is apparently there cannot be operated by me, nor does it provide any feedback on which skeys I am hovering my fingers over. This issue alone renders the app unusable.
Issue 2: Throughout the entire app, there are lots of buttons, tick boxes, radio buttons that are unlabelled. So the purpose of the element is unknown. Again, this is an issue that is prevalent throughout the entire app.
I've ended up grouping all issues into 2 categories rather than go through the app screen-by-screen, but as it stands, I cannot progress through the app because of the issues outlined in issue 1.
Swiping right/left and exploring the app by touch should reveal all issues anyway.
Thanks for providing the best KeePass app, in my opinion, despite these issues.
Hi, sorry for the trouble you encounter. To be honest, I am not very experienced with these kinds of requirements. Speaking about the keyboard for password entry: Is it possible that this come from requiring the use of the "secure keyboard mode" (which means that the keyboard should not save any entered information)?
Another screen reader user here, though I'm on Samsung's fork of Talkback so my experiences may be slightly different. I have enough vision that I can temporarily bypass or disable Talkback when using software that doesn't play well with it, so hopefully I can help.
Assuming you've got zero experience with screen readers, basically they intercept the standard touch gestures like tapping, dragging, swiping, etc. to allow people with low or no vision to find and interact with on-screen elements. This works well most of the time, but can require a bit of extra development effort when custom UI widgets are involved and obviously requires images and icons to have alt text.
The built-in KP2A keyboard is unusable while Talkback is enabled. It just doesn't respond to tapping or dragging, and keys are not selectable. This is not related to secure keyboard mode, it behaves like that when used as a regular keyboard in other apps and also when in KP2A database entry mode. Using a third party keyboard (Samsung Keyboard, Microsoft Swiftkey) to enter passwords into KP2A works correctly.
The password field used on the unlock screen is not selectable by Talkback. When swiping through the items on-screen, which is analogous to tabbing on desktop, the selection cursor goes directly from the "Password" label above the box to the "show password" toggle on its right. The toggle is unlabelled, so it is unclear whether the password is currently being shown if you can't physically see it yourself.
When I open the app and reach the unlock screen, the password entry field is active by default so my system keyboard appears automatically and I can type my password. If I dismiss the keyboard, I have to temporarily bypass Talkback then tap inside the password field to reactivate it.
The other unlabelled buttons I've run into thus far are for adding a new entry or group.
Hello, I am an active Talkback user/accessibility tester and I am ready to create more issues if needed regarding accessibility. Is it better to create separate issue for each problem? Unfortunately, KeePass2Android has a lot of accessibility issues as was mentioned in the issue description and fixing them will really help to use this password manager independently for blind/visually impaired users.
I think it's best to collect it here. I would have to tackle them all in one go anyway. Sorry for bad accessibility right now.