[a11y] Accessibility/Android-Talkback: Login form problems

[strseb]

So! I've tried signing up only using talk back (no peeking!), found some issues, while playing around:

• I was able to focus invisible Elements (i.e the "change email button" while on the input email page)
• Input errors i.e "wrong password" are not selectable (therefore i wouldn't know)
• Input's placeholder or the header was not selectable (therefore I didn't know what I'm supposed to enter here)
• I was able to focus the global window (that is probably android specific)

┆Issue is synchronized with this Jira Bug ┆Reporter: Data Sync

[MattLichtenstein]

Did some testing on iOS using voiceover:

I was able to focus invisible Elements (i.e the "change email button" while on the input email page)

Doesn't happen on iOS

Input errors i.e "wrong password" are not selectable (therefore i wouldn't know)

These were selectable on iOS

Input's placeholder or the header was not selectable (therefore I didn't know what I'm supposed to enter here)

Headers were selectable, input placeholders were not

I was able to focus the global window (that is probably android specific)

Also reproducible on iOS

Some other issues I noticed from the limited testing I did on iOS:

• Some text components are not selectable:
  • "Enter your email address to continue using Mozilla VPN"
  • "By continuing, you agree to the Terms of Service and the Privacy Policy"
  • All three lines of text in the password requirements popover/tooltip
• Many buttons have two focusable components, the button and the underlying text, which seems redundant.
• Disabled buttons can be clicked using voiceover
• Terms of Service and Privacy Policy links are unfocuasble/unaccessible
• Various problems with inputs being focusable, and then later not being focusable

[data-sync-user]

➤ Santiago Andrigo commented:

Moving this to Medium on a ruthlessly utilitarian criteria of % of users impacted, and in recognizing that we haven’t fixed this in a long time. But we should fix this.

[data-sync-user]

➤ Vinoo Cherian commented:

• The invisible elements issue was fixed in https://mozilla-hub.atlassian.net/browse/VPN-5392 ( https://mozilla-hub.atlassian.net/browse/VPN-5392|smart-link )
  • All input placeholders except for Password are now read. Password field placeholders are not read because of a Qt bug, where Accessible.name ( http://Accessible.name ) is not being as the field’s name password masked fields. Also, the Password field is currently ignored for Accessibility – changing that will cause the screen reader to read the plain text password when the field gains focus. This is also a Qt bug. See https://bugreports.qt.io/browse/QTBUG-120097 ( https://bugreports.qt.io/browse/QTBUG-120097 ) for the Qt bug that tracks this.
  • On Android Press and Hold on the screen to get a entire screen to be read to you. Control labels and other static text fields are not accessible by swiping left or right.
  • The input errors are shown in a Tooltip, which doesn’t take focus, so it cannot be read. We may need to change the UI to make this accessible.

So, these remaining issues are blocked.

[data-sync-user]

➤ Santiago Andrigo commented:

Thanks Vinoo. Can you clarify the second sentence of the second bullet point? Not sure I follow.

[data-sync-user]

➤ Vinoo Cherian commented:

Santiago Andrigo Updated the investigation notes below.