- From: Katie Haritos-Shea <ryladog@gmail.com>
- Date: Fri, 5 May 2017 09:57:38 -0400
- To: "lisa.seeman" <lisa.seeman@zoho.com>
- Cc: Greg Lowney <gcl-0039@access-research.org>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <CAEy-OxER1bq4_yShjnDW+vKrjsCM_RF9-0zCJekdACOS+haTgg@mail.gmail.com>
I agree with Hreg and David! Katie Haritos-Shea 703-371-5545 On May 5, 2017 8:12 AM, "lisa.seeman" <lisa.seeman@zoho.com> wrote: > +1 > > ---- On Fri, 05 May 2017 08:26:41 +0300 *Greg > Lowney<gcl-0039@access-research.org <gcl-0039@access-research.org>>* > 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. > > Greg > > -------- Original Message -------- > Subject: Can you confirm if you want the sensitive data exception for > timeouts > From: lisa.seeman <lisa.seeman@zoho.com> <lisa.seeman@zoho.com> > To: W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org> <w3c-wai-gl@w3.org> > 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 <http://il.linkedin.com/in/lisaseeman/>, Twitter > <https://twitter.com/SeemanLisa> > > > > > >
Received on Friday, 5 May 2017 13:58:14 UTC