- From: Janina Sajka <janina@rednote.net>
- Date: Tue, 15 Sep 2020 08:01:05 -0400
- To: Alastair Campbell <acampbell@nomensa.com>
- Cc: "public-cognitive-a11y-tf@w3.org" <public-cognitive-a11y-tf@w3.org>
I have several accounts that occasionally employ this validation strategy. In my experience it's most commonly triggered by my bringing up a new machine with new browsers. This includes my recently acquired new phone, but also a new PC this summer. I never use copy and paste on these, personally. I simply remember the 6 digits. That's me. I'm sure that's unreasonable for people with different disabilities. I would note, however, that I always have the option to recieve this code in my choice of media, usually a choice of SMS text, email, or voice telephone. I often take the latter as that allows me to position my browser in the input field as the call is being placed to me and simply type the code as I hear it on my speaker phone. Best, Janina Alastair Campbell writes: > Hi folks, > > An interesting question has come up about Accessible Authentication. > https://github.com/w3c/wcag/issues/1292 > > The crux of it seems to be: Is copy-pasting a code (e.g. a one-time access code) an issue? > > If that is a reliable method for the people this SC is aiming to help, we need to account for that. > > >From the experience of individuals in the group (directly or through observation), is copy-pasting a code (e.g. 6 digits) from one app to another a significant barrier? > > E.g. if you receive a 6 digit code via SMS, is pasting that into a website (or other app) an issue? > > Kind regards, > > -Alastair > > -- > > @alastc / www.nomensa.com<http://www.nomensa.com> > > -- Janina Sajka https://linkedin.com/in/jsajka Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
Received on Tuesday, 15 September 2020 12:01:26 UTC