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

RE: Follow up from the meeting on Issue 14: timeouts

From: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Date: Fri, 12 May 2017 10:14:16 -0400
To: "'White, Jason J'" <jjwhite@ets.org>, "'Andrew Kirkpatrick'" <akirkpat@adobe.com>, "'Gregg C Vanderheiden'" <greggvan@umd.edu>, "'Schnabel, Stefan'" <stefan.schnabel@sap.com>
Cc: "'David MacDonald'" <david100@sympatico.ca>, "'w3c-waI-gl@w3. org'" <w3c-wai-gl@w3.org>
Message-ID: <430c01d2cb2a$0ad23920$2076ab60$@gmail.com>
As much as I don’t want to be a pain, I have to agree with this logic from Jason and Gregg.

 

Let’s just identify those exceptions, as easily as possible for this PWD, please. Copy the exception text from 2.2.1 if need be.

 

​​​​​* katie *

 

Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)

 

Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 |  <https://twitter.com/Ryladog> @ryladog

NOTE: The content of this email should be construed to always be an expression of my own personal independent opinion, unless I identify that I am speaking on behalf of Knowbility, as their AC Rep at the W3C - and - that my personal email never expresses the opinion of my employer, Deque Systems.

 

From: White, Jason J [mailto:jjwhite@ets.org] 
Sent: Friday, May 12, 2017 9:21 AM
To: Andrew Kirkpatrick <akirkpat@adobe.com>; Gregg C Vanderheiden <greggvan@umd.edu>; Schnabel, Stefan <stefan.schnabel@sap.com>
Cc: David MacDonald <david100@sympatico.ca>; Katie Haritos-Shea <ryladog@gmail.com>; w3c-waI-gl@w3. org <w3c-wai-gl@w3.org>
Subject: RE: Follow up from the meeting on Issue 14: timeouts

 

 

 

From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com] 
Sent: Friday, May 12, 2017 9:17 AM

Gregg,

The current language is:

For each time limit set by the content where user-entered data can be lost, the user is advised about the length of the time limit at the start of the process, unless any user-entered data is preserved for at least 24 hours after the limit is reached.

 

Real-time events such as running out of hotel rooms, or an auction closing out are not set by the content, so they would not apply. We can explain that in the Understanding document of course.

[Jason] 2.2.1 uses the phrase “time limit that is set by the content”. Real-time events and “essential” exceptions are then handled as exceptions (i.e., special cases). This treatment makes it clear that such cases are indeed instances of “time limits set by the content” as this phrase is used in WCAG, contrary to your assertion above.

If you want to exclude them from any proposal, it has to be done explicitly.

 

 

  _____  

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

 

Thank you for your compliance.

  _____  
Received on Friday, 12 May 2017 14:14:52 UTC

This archive was generated by hypermail 2.3.1 : Friday, 12 May 2017 14:14:53 UTC