W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2017

auto-updating/scrolling content and applicability of BOTH 2.2.1 and 2.2.2

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Thu, 31 Aug 2017 12:33:03 +0100
To: 'WAI Interest Group' <w3c-wai-ig@w3.org>
Message-ID: <a6c9cf8d-b290-0704-e6ab-798888e1f55a@splintered.co.uk>
Just a question/clarification:

2.2.1 Timing Adjustable is normatively concerned with time 
limits/time-outs - usually taken in the context of pages that 
automatically log you out after a certain time, tests with a countdown 
timer, time-outs that happen behind the scenes that mean that a form 
submission/proceeding to the next step fails after a certain period of time.

In the non-normative understanding document, examples are also given for 
auto-updating and auto-advancing/scrolling content.

2.2.2 Pause, Stop, Hide has normative text that specifically addresses 
scrolling and auto-updating content.

Now, does this mean that auto-updating/scrolling content is subject to 
BOTH 2.2.1 and 2.2.2? I guess the answer is yes (as the SCs serve subtly 
different purposes/audiences). If so, 2.2.1's normative text requires 
that a user be able to turn off (e.g. pause/stop) this 
auto-updating/scrolling "time limit before encountering it".  Would a 
pause/stop button that's present pass this, as it's arguably not "before 
encountering it" but rather that mechanism is present right there where 
the time limit based auto-updating/scrolling is happening?

Thanks,

P
-- 
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 31 August 2017 11:33:27 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 31 August 2017 11:33:29 UTC