W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2017

Re: Accessible Authentication and issue responses

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Sat, 23 Dec 2017 17:05:03 +0000
Cc: Michael Pluke <Mike.Pluke@castle-consult.com>, Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
Message-Id: <768A7620-D99C-49B3-9738-B92538BAD5A3@splintered.co.uk>
To: Alastair Campbell <acampbell@nomensa.com>
How would a user be able to use another browser-based or extension-based password manager or similar tool on a public terminal, for instance?


> On 23 Dec 2017, at 15:31, Alastair Campbell <acampbell@nomensa.com> wrote:
> From: Michael Pluke
> > It appears to pretty much debar all authentication processes that involve user information entry - as whatever they enter either has to be retrieved from the user’s memory or copied (tanscribed) from somewhere. Also I do not see how an authenticaton process can rely on every unspecified user agent being able to enter a user’s personal information (at present, surely, public terminals will certainly not have access to stored user intormation)?
> Hi Mike,
> It is asking for alternative methods, other than needing to remember/copy things manually. Look at any of the recent threads for example techniques.
> It leaves open the ability to use a browser-based / extension for managing usernames/passwords, and says ‘does not block’ them. The content is responsible for not blocking their use, we are not saying every user-agent has to know that information.
> Cheers,
> -Alastair

Received on Saturday, 23 December 2017 17:05:29 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:19 UTC