W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > June 2017

Re: Next steps for accessible authentication

From: lisa.seeman <lisa.seeman@zoho.com>
Date: Sun, 18 Jun 2017 21:37:55 +0300
To: "public-cognitive-a11y-tf" <public-cognitive-a11y-tf@w3.org>, "Andrew Kirkpatrick" <akirkpat@adobe.com>, "Joshue O Connor" <josh@interaccess.ie>, "Janina Sajka" <janina@rednote.net>
Cc: "Michael Cooper" <cooper@w3.org>, "Rochford, John" <john.rochford@umassmed.edu>, "Michael Pluke" <mike.pluke@castle-consult.com>
Message-Id: <15cbc7d6a95.11ddfce8574251.7755132343458429638@zoho.com>

        

        
            Josh, Andrew, JaninaDo you want me to set up a call with the web authentication group or is it better coming from you? Either way we should move on this as fast as possible.All the bestLisa SeemanLinkedIn, Twitter---- On Thu, 15 Jun 2017 19:17:30 +0300  lisa.seeman<lisa.seeman@zoho.com> wrote ----Next steps for accessible authentication1. We need to set up a review with the web authentication folks and check they are comfortable we are ncreating security problems. Who should set that up? (Options: John, Me, Andrew or Josh as wcag chairs or Janina as APA...)2. All the comments need to be addressed in github . see: https://github.com/w3c/wcag21/issues/23also we need to check the survey: https://www.w3.org/2002/09/wbs/35422/COGA_Auth/results (although we can disagree with them and try and convince them)3. We need an exception for when this is not possible with current legislative requirments4. Possible exception for coping up to four characters ? DO we see a user problem with this?All the bestLisa SeemanLinkedIn, Twitter
        
        

    
    
Received on Sunday, 18 June 2017 18:38:33 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 18 June 2017 18:38:34 UTC