Version
3.4.2
Source
F-Droid
Vault encryption
No
Device
Samsung Galaxy S20 5G Ultra
Android version
Android 14
ROM
Official Galaxy Firmware unrooted
Steps to reproduce
- Enable TalkBack on the Android device.
- Start Aegis and proceed through the initial setup wizard.
- Navigate through the first setup screen using TalkBack.
- Locate the navigation button used to continue to the next screen. TalkBack does not provide a meaningful accessible label for this button.
- Use TalkBack's custom-label feature to manually label this button "Next" in order to identify it.
- Continue to the following setup screen.
- Navigate to the button used to return to the previous screen. TalkBack also does not provide a meaningful accessible label for this button.
- Use TalkBack's custom-label feature to manually label this button "Back" in order to identify it.
What do you expect to happen?
TalkBack should announce the setup wizard's navigation controls with meaningful accessible names, such as "Next" and "Back", without requiring the user to create custom TalkBack labels.
As a blind TalkBack user, I should be able to navigate and complete the initial Aegis setup independently using the accessibility information supplied by the app.
TalkBack should announce the setup wizard's navigation controls with meaningful accessible names, such as "Next" and "Back", without requiring the user to create custom TalkBack labels.
As a blind TalkBack user, I should be able to navigate and complete the initial Aegis setup independently using the accessibility information supplied by the app.
What happens instead?
TalkBack encounters navigation buttons in the initial setup wizard without meaningful accessible labels. In my testing, the button for proceeding to the next screen was unlabeled, and on the following screen the button for returning to the previous screen was also unlabeled.
I was able to work around the problem by using TalkBack's custom-label feature and manually assigning the labels "Next" and "Back" to the respective buttons.
Without those manually created labels, these controls are difficult to identify when navigating the setup wizard with TalkBack. Providing appropriate accessible names for the controls would allow blind users to identify their purpose without this workaround.
Log
Email if additional information is needed.
Version
3.4.2
Source
F-Droid
Vault encryption
No
Device
Samsung Galaxy S20 5G Ultra
Android version
Android 14
ROM
Official Galaxy Firmware unrooted
Steps to reproduce
What do you expect to happen?
TalkBack should announce the setup wizard's navigation controls with meaningful accessible names, such as "Next" and "Back", without requiring the user to create custom TalkBack labels.
As a blind TalkBack user, I should be able to navigate and complete the initial Aegis setup independently using the accessibility information supplied by the app.
TalkBack should announce the setup wizard's navigation controls with meaningful accessible names, such as "Next" and "Back", without requiring the user to create custom TalkBack labels.
As a blind TalkBack user, I should be able to navigate and complete the initial Aegis setup independently using the accessibility information supplied by the app.
What happens instead?
TalkBack encounters navigation buttons in the initial setup wizard without meaningful accessible labels. In my testing, the button for proceeding to the next screen was unlabeled, and on the following screen the button for returning to the previous screen was also unlabeled.
I was able to work around the problem by using TalkBack's custom-label feature and manually assigning the labels "Next" and "Back" to the respective buttons.
Without those manually created labels, these controls are difficult to identify when navigating the setup wizard with TalkBack. Providing appropriate accessible names for the controls would allow blind users to identify their purpose without this workaround.
Log
Email if additional information is needed.