Re: Timeouts and WebauthN

Agree.  That is how I think the original drafters would have called it - based on the discussions back then. 
gregg

———————————
Professor, University of Maryland, College Park
Director , Trace R&D Center, UMD

> On Jul 15, 2021, at 10:06 AM, Jonathan Avila <jon.avila@levelaccess.com> wrote:
> 
> If there is no loss of data and no loss of your place in a process then it seems to be consistent with extending time meeting the criteria.
>  
> Jonathan
>  
> From: Alastair Campbell <acampbell@nomensa.com <mailto:acampbell@nomensa.com>> 
> Sent: Thursday, July 15, 2021 5:04 AM
> To: Jonathan Avila <jon.avila@levelaccess.com <mailto:jon.avila@levelaccess.com>>
> Cc: WCAG list (w3c-wai-gl@w3.org <mailto:w3c-wai-gl@w3.org>) <w3c-wai-gl@w3.org <mailto:w3c-wai-gl@w3.org>>
> Subject: RE: Timeouts and WebauthN
>  
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>  
> Hi Jon,
>  
> > An extension of time means you do not lose any data.  Restarting the auth process may require that you re-enter your user name or authentication details again.
>  
> Except that in this case (WebauthN) you don’t have any details to input. You press the button, it hands off to your device, and if your device provides the authentication you’re in. If not, you start again by hitting the button.
>  
> There is no data to loose. (This is after it is setup, you would have more info if you are registering in the first place.)
>  
> How is that different from a key press to extend?
>  
> Cheers,
>  
> -Alastair