Accessibility issues for users with disabilities (Android) #a11y

[rscano]

Hi, I went through the app on Android with the screen reader enabled and found these issues (i've tested with italian language, version 2026.04-2(22)):

Welcome (and general issues)

1. All the welcome information after the first tab is not perceivable with the screen reader.

2. All elements that visually appear as headings do not have the proper heading semantics.

3. It is not possible to use the screen in landscape orientation (specific requirement of WCAG 2 and EN 301 549).

4. All icons have inadequate alternative text. For example, the app logo icon inside is read as “Normal logo icon”.

5. In the general navigation, with "Consent", "Security" and "Verification", the selected item is not announced as active, so it's not clear which step you're currently on.### "Security" Tab

6. The most critical issue is in the "Security" tab. The screen reader user does not perceive the individual input fields. Instead, they only perceive the "Confirm" button (disabled) and then a keyboard. Simply selecting a value from the numeric keypad automatically fills each individual field (this information is not announced to the screen reader).

7. Still in the "Security" tab, once the 6 PIN digits have been entered, the user is automatically taken to the PIN confirmation step, but without adequate notifications to the screen reader. The "Confirm" button itself is automatically selected and activated.

8. If the PINs do not match, a text message appears that is not announced to the screen reader.

9. In case of biometric authorization failure, the error message is not announced to the screen reader.

"Verification" Tab

1. All options are missing the button role.
2. Selecting "National eID / National idP" opens a new window without informing the user. That demo procedure also has major accessibility shortcomings.
3. In the document verification procedure, the progress of downloading the additional content for facial recognition is not announced to the screen reader. Similarly, the focus is not moved to the "Start" button after the download is complete.
4. In the document capture process, the flash on/off toggle is not handled natively, making it impossible for the screen reader user to know whether the flash is currently active or not.
5. During photo capture, rotating the smartphone to landscape mode closes the window.
6. With large text sizes, part of the instructions is hidden below the photo capture block.
7. When selecting the QR-Code scanning option, the system does not notify the screen reader about the correct positioning of the smartphone. In case of error, it returns to the previous page, where the close button has alternative text in English instead of the user’s language.

"Settings" menu

1. The link to delete the credentials does not have link semantics.

Main layout / screen after configuration.

1. The entire block with the remaining accesses and the related graphical elements is read in a disjointed and incoherent way.
2. The QR scanning block has the same problem already described earlier in the "Verification" section.

[manecke]

Thank you for the very detailed report. We'll work through the specific points raised here (heading semantics, screen reader announcements for PIN errors, button/link roles, landscape support, and the others) as part of that effort.

[rscano]

Perfect. As future implementations, i suggest to develop directly with accessibility in mind, without adding it after ;)