Re: Show/hide toggle to reveal masked password

The sighted person can see they have made it visible, which they probably
also intended to do, but they can also see that people around them can see
it, the non-sighted user is probably aware if people are around them but
not what attitude those people have towards information displayed on the
screen.

This makes me think you should have a aria hidden reveal password button,
and  a screenreader only reveal password button that says the password will
be read out when you click this (then they can put headphones on). Thus
clicking screenreader only password reveal, set focus on element with
password in it but do not 'show' password, after which there should be
button go back to password field.

or am I being too nitpicky.

On Tue, Jul 12, 2022 at 1:00 PM Janina Sajka <janina@rednote.net> wrote:

> Oh dear, can you perhaps explain why an individual who happens to be
> blind is more likely to do what you suggest than any other user?
>
> Marc Haunschild writes:
> > Much more important (in my opinion): can the password be revealed by
> accident in a way, that blind people do not realize, so that sighted people
> in the surrounding can see the password?
> >
> > There should be always a warning, when showing the password.
> >
> > --
> >
> > Mit freundlichen Grüßen
> >
> >
> > Marc Haunschild
> > Accessibility Consulting
> >
> > https://Accessibility.Consulting
> > Prüfstelle im BIK-BITV-Prüfverbund
> >
> > Sonnenhof 32
> > 53119 Bonn
> > Telefon: 0170 8 64 00 63
> > Email: Marc.Haunschild@Accessibility.Consulting
> >
> > > Am 11.07.2022 um 22:15 schrieb Patrick H. Lauke <
> redux@splintered.co.uk>:
> > >
> > > On 11/07/2022 15:59, Lisa Spirko wrote:
> > > [...]
> > >> Most password fields use masking characters, and without this toggle,
> screen readers read the masking characters (“star star star star…”), not
> the actual characters being typed. This seems to me to be a significant,
> severe accessibility issue because screen reader users are unable to
> confirm that the password they’re entering is correct.
> > >
> > > Noting that the experience is no different for a
> sighted/non-screen-reader user here too.
> > >
> > >> Essentially, this issue renders the entire system inaccessible
> because the screen reader user cannot even access it.
> > >
> > > And yet, screen reader users have been managing the same way that
> non-screen reader users have with these. Yes, having a show/hide toggle can
> be useful for all users, but not having one is not a showstopper for SR or
> non-SR users either.
> > >
> > > SC 3.3.7 Accessible Authentication in the upcoming WCAG 2.2 aims to
> partially address this by, at the very least, making sure that those
> password fields can be filled/work with password managers, or at least
> allow pasting. https://www.w3.org/TR/WCAG22/#accessible-authentication
> > >
> > > P
> > > --
> > > Patrick H. Lauke
> > >
> > > https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> > > https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> > > twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > >
> >
>
> --
>
> Janina Sajka (she/her/hers)
> https://linkedin.com/in/jsajka
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa
>
>
>