Re: some questions: : working on re-authentication

employer ID is much different than your  SIN.   

And giving your SIN to your employer (who already has it) or your School  is MUCH different than giving it out to ever website that asks for a log in. 

Gregg


> On Dec 21, 2017, at 9:59 AM, lisa.seeman <lisa.seeman@zoho.com> wrote:
> 
> I will add identification number back in
> However this does mean that it  would be better to support automatic entry rather then "not block it"
> 
> Can you explain the problem again with asking people to support automatic entry for the exception.
> 
> All the best
> 
> Lisa Seeman
> 
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter <https://twitter.com/SeemanLisa>
> 
> 
> 
> 
> ---- On Thu, 21 Dec 2017 16:36:44 +0200 Michael Gower<michael.gower@ca.ibm.com <mailto:michael.gower@ca.ibm.com>> wrote ---- 
> I think you have to have "identification number" in there somewhere. There are a ton of processes in every enterprise I've worked in, as well as government, that require me to enter an employee ID or SIN as my primary identifier. Most banks use a bank card number as a determinant in a 2-factor process.
> 
> Michael Gower
> IBM Accessibility
> Research
> 
> 1803 Douglas Street, Victoria, BC  V8T 5C3
> gowerm@ca.ibm.com <mailto:gowerm@ca.ibm.com>
> voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034
> 
> 
> 
> From:        Alastair Campbell <acampbell@nomensa.com <mailto:acampbell@nomensa.com>>
> To:        "lisa.seeman" <lisa.seeman@zoho.com <mailto:lisa.seeman@zoho.com>>
> Cc:        WCAG <w3c-wai-gl@w3.org <mailto:w3c-wai-gl@w3.org>>, John Foliot <john.foliot@deque.com <mailto:john.foliot@deque.com>>
> Date:        2017-12-21 04:18 AM
> Subject:        Re: some questions: : working on re-authentication
> 
> 
> Hi Lisa,
>  
> (John – question for you below.)
>  
> For this:
> - authentication process can rely on the user or user-agent entering personal identification information such as name, username, password, and email address if the web content consistently supports automatic entry.
>  
> > Automatic entry of user information can not work because autocomplete and the name is not set . It is not quite blocking the user agent rather they are not supported.
>  
>  
> If the username/password (or other) inputs pass 1.3.1. (info & relationships) and 4.1.2 (role/name/value) then user-agents currently support automatic entry unless the site actively blocks it.
>  
> Also, there would also be overlap with the new SC that requires the autofill attributes, which I think includes username and current-password? (JF– have they been kept in the list?)
> Therefore, I would like to revert that change to avoid overlap with other SCs.
>  
>  
> > Also if transcribe follows the dictionary definition we can just clarify what we mean in the understanding section. Is that Ok?
>  
> I think that would be best.
>  
> Cheers,
>  
> -Alastair
>  
> 
> 
> 
> 
>