- From: David MacDonald <david100@sympatico.ca>
- Date: Thu, 31 Aug 2017 17:03:04 -0400
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: w3c WAI List <w3c-wai-ig@w3.org>
- Message-ID: <CAAdDpDYKFEXmZcwoCbjkRr2q2Gk2Y0SfbZg4M7kihB2jvRUAAw@mail.gmail.com>
We wouldn't interpret it that way. Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd GitHub <https://github.com/DavidMacDonald> www.Can-Adapt.com <http://www.can-adapt.com/> * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html> On Thu, Aug 31, 2017 at 3:58 PM, Patrick H. Lauke <redux@splintered.co.uk> wrote: > On 31/08/2017 19:33, David MacDonald wrote: > >> I would say it meets both. >> > > Any thoughts on my "If so..." portion of the question? > > P > > Cheers, >> David MacDonald >> >> *Can**Adapt**Solutions Inc.* >> >> Tel: 613.235.4902 >> >> LinkedIn >> <http://www.linkedin.com/in/davidmacdonald100> >> >> twitter.com/davidmacd <http://twitter.com/davidmacd> >> >> GitHub <https://github.com/DavidMacDonald> >> >> www.Can-Adapt.com <http://www.can-adapt.com/> >> >> / Adapting the web to *all* users/ >> >> / Including those with disabilities/ >> >> If you are not the intended recipient, please review our privacy policy < >> http://www.davidmacd.com/disclaimer.html> >> >> On Thu, Aug 31, 2017 at 7:33 AM, Patrick H. Lauke <redux@splintered.co.uk >> <mailto:redux@splintered.co.uk>> wrote: >> >> 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 <http://www.splintered.co.uk> | >> https://github.com/patrickhlauke <https://github.com/patrickhlauke> >> http://flickr.com/photos/redux/ <http://flickr.com/photos/redux/> | >> http://redux.deviantart.com >> twitter: @patrick_h_lauke | skype: patrick_h_lauke >> >> >> > > -- > 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 21:03:28 UTC