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

Re: Can you confirm if you want the sensitive data exception for timeouts

From: lisa.seeman <lisa.seeman@zoho.com>
Date: Fri, 05 May 2017 15:10:47 +0300
To: Greg Lowney <gcl-0039@access-research.org>
Cc: "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>
Message-Id: <15bd8832848.ca412c1f132854.4004013364795159551@zoho.com>

---- On Fri, 05 May 2017 08:26:41 +0300 Greg Lowney&lt;gcl-0039@access-research.org&gt; wrote ---- 

  I brought up the case because I felt we should make an explicit decision about it, but my preference is to not include an exception in the SC, and instead to add wording to the Understanding document explaining the rationale as you stated it: if any data cannot be saved, whether to security or other reasons, they need to either warn about the timeout ahead of time or make the timeout period extremely long.
 Speaking of which, the Understanding document should also explain why we don't offer the alternative approach of prompting the user at the end of the timeout period with an option to extend. 
 -------- Original Message --------
 Subject: Can you confirm if you want the sensitive data exception for timeouts
 From: lisa.seeman &lt;lisa.seeman@zoho.com&gt;
 To: W3c-Wai-Gl-Request@W3. Org &lt;w3c-wai-gl@w3.org&gt;
 Date: 5/4/2017 7:57 PM
   Hi Folks 
 on yesterdays call people asked to we'll add the sensitive data exception so that we do not  force people to keep sensitive data
 However we don't force them to keep the data, it's just that if they don't they need to provide a warning about any timeout period.
 People need to know how long they have to fill out the form. I do not think that goes away just becuse the data is sensitive.
 Unfortunately the Que was closed and I could not comment, so I am not sure how to proceed here
 Do we want  the sensitive data exception? 
 Also can anyone suggest wording for sensitive data that will not create a huge loophole for everything?
 what I have so far is :
 sensitive information - information that can put users at risk
 issue on github is : https://github.com/w3c/wcag21/issues/14
 All the best
 Lisa Seeman
 LinkedIn, Twitter
Received on Friday, 5 May 2017 12:11:24 UTC

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