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: Schnabel, Stefan <stefan.schnabel@sap.com>
Date: Mon, 15 May 2017 07:15:44 +0000
To: Gregg C Vanderheiden <greggvan@umd.edu>
CC: Jason J White <jjwhite@ets.org>, David MacDonald <david100@sympatico.ca>, Katie Haritos-Shea <ryladog@gmail.com>, Andrew Kirkpatrick <akirkpat@adobe.com>, "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>
Message-ID: <ade927a1908143f0b5dac0d674f025dc@sap.com>

>>> This would be an enormous distraction for some people and make the page unusable.     It also violates another SC on animation.

You just doomed ebay.



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

A couple thoughts


On May 12, 2017, at 9:46 AM, Schnabel, Stefan <stefan.schnabel@sap.com<mailto:stefan.schnabel@sap.com>> wrote:

I would rather see an extension of this SC requiring a permanent display of time left as part of the UI or context.


This would be an enormous distraction for some people and make the page unusable.     It also violates another SC on animation.


making an optional one is possible — but in many cases the timeout is at the server end and the page does not know exactly when.   Also - if the timeout is caused by other events — the exact time is not know. (unless you have a real-time event exception in which case this is not a problem since they would not be subject to the SC.


G
Received on Monday, 15 May 2017 07:16:20 UTC

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