github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 11:44:41 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Android/iOS: Accessibility - File/Text controls unintuitive, "Text" accessible name incorrect #1457

New Issue
Closed
opened 2025-11-26 22:49:40 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-26 22:49:40 -06:00
Owner
Copy Link

Originally created by @patrickhlauke on GitHub (May 21, 2022).

Originally assigned to: @andrebispo5 on GitHub.

Steps To Reproduce

  1. Turn on VoiceOver/iOS, Talkback/Android
  2. Go to "Send" > "Add a Send"
  3. Go to the "File"/"Text" options

Expected Result

The currently selected option should announce as something like "pressed"/"selected" or similar.

Actual Result

The currently selected option is announced as a disabled/dimmed button, which is not immediately obvious as "this is what's actually enabled/selected".

Additionally, it appears that the accessible name for the "Text" button is incorrect: VoiceOver announces it as "left curly bracket Text right curly bracket, Button". Talkback annouces it as "Text, Button", but with TB's visible text output enabled, it can be seen that it's actually "{Text}, Button" ... only that TB chooses to silently ignore the curly brackets.

Screenshots or Videos

Currently selected option, announced by VoiceOver as a "dimmed" button

Currently selected option, announced by VoiceOver as a "dimmed" button

Focus on the "Text" control, with the VO output visible at the bottom "left curly bracket Text right curly bracket, Button"

Focus on the "Text" control, with the VO output visible at the bottom "left curly bracket Text right curly bracket, Button"

Additional Context

No response

Operating System

Android, iOS

Operating System Version

No response

Device

No response

Build Version

2.18.0 (4572)

Beta

  • Using a pre-release version of the application.
Originally created by @patrickhlauke on GitHub (May 21, 2022). Originally assigned to: @andrebispo5 on GitHub. ### Steps To Reproduce 1. Turn on VoiceOver/iOS, Talkback/Android 2. Go to "Send" > "Add a Send" 3. Go to the "File"/"Text" options ### Expected Result The currently selected option should announce as something like "pressed"/"selected" or similar. ### Actual Result The currently selected option is announced as a disabled/dimmed button, which is not immediately obvious as "this is what's actually enabled/selected". Additionally, it appears that the accessible name for the "Text" button is incorrect: VoiceOver announces it as "left curly bracket Text right curly bracket, Button". Talkback annouces it as "Text, Button", but with TB's visible text output enabled, it can be seen that it's actually "{Text}, Button" ... only that TB chooses to silently ignore the curly brackets. ### Screenshots or Videos Currently selected option, announced by VoiceOver as a "dimmed" button ![Currently selected option, announced by VoiceOver as a "dimmed" button](https://user-images.githubusercontent.com/895831/169663652-4086b4a8-5fb2-4e7b-9d0e-6eb6b85fc357.png) --- Focus on the "Text" control, with the VO output visible at the bottom "left curly bracket Text right curly bracket, Button" ![Focus on the "Text" control, with the VO output visible at the bottom "left curly bracket Text right curly bracket, Button"](https://user-images.githubusercontent.com/895831/169663696-2cb9bb47-83cf-4100-993a-292e62c7d55a.png) ### Additional Context _No response_ ### Operating System Android, iOS ### Operating System Version _No response_ ### Device _No response_ ### Build Version 2.18.0 (4572) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:49:40 -06:00
GiteaMirror commented 2025-11-26 22:49:40 -06:00
Author
Owner
Copy Link

@patrickhlauke commented on GitHub (May 21, 2022):

It might be easier/more intuitive to pick a more standard set of controls, like two radio buttons, instead

@patrickhlauke commented on GitHub (May 21, 2022): It might be easier/more intuitive to pick a more standard set of controls, like two radio buttons, instead
GiteaMirror commented 2025-11-26 22:49:41 -06:00
Author
Owner
Copy Link

@patrickhlauke commented on GitHub (May 25, 2022):

thanks @andrebispo5

@patrickhlauke commented on GitHub (May 25, 2022): thanks @andrebispo5
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1457
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?