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

Re: CFC - Accessible Authentication and issue responses

From: Michael Pluke <Mike.Pluke@castle-consult.com>
Date: Sat, 23 Dec 2017 11:13:58 +0000
To: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
Message-ID: <64A5CC9BDCD67BA7.5ED2628E-9552-4377-ACA8-5A8783806CE3@mail.outlook.com>
The more I look at this the less I understand it!

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)?

On Fri, Dec 22, 2017 at 4:56 AM +0000, "Andrew Kirkpatrick" <akirkpat@adobe.com<mailto:akirkpat@adobe.com>> wrote:

Call For Consensus — ends Tuesday January 2nd at 11:45PM Boston time.

The Working Group has discussed a change to the note in the Accessible Authentication SC.

The specific changes are detailed in this pull request (https://github.com/w3c/wcag21/pull/646)  and can be viewed at http://rawgit.com/w3c/wcag21/accessible-authentication-update/guidelines/index.html#accessible-authentication.

Issue responses: https://www.w3.org/WAI/GL/wiki/2-2-6_Revision

 Call minutes: https://www.w3.org/2017/12/21-ag-minutes.html#item03

If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.


Andrew Kirkpatrick
Group Product Manager, Accessibility


Received on Saturday, 23 December 2017 11:14:28 UTC

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