- From: David MacDonald <david100@sympatico.ca>
- Date: Tue, 5 Sep 2017 20:36:58 -0400
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: w3c WAI List <w3c-wai-ig@w3.org>
- Message-ID: <CAAdDpDY-yR42=vwxOrcYwj2THNRjJJYPrgbLL+ux-JWFD5arnA@mail.gmail.com>
>Is that a pass for 2.2.1 or a fail (as there was no mechanism to pause/stop "before encountering it" since it's on the homepage)? 2.2.1 wasn't intended to be about moving content, such as a carousel... technically yes there is a time limit before the next slide comes up... but that was not the use case the SC was trying to address. It was more about taking a test or a filling in a form that had a time limit. The auto scroller is a better match for 2.2.2 and the pause button doesn't have to proceed it to pass 2.2.2. The primary intention for 2.2.2 was for people who become distracted by the movement and therefore can see it, and therefore the DOM order is not as critical for that person as it is for a user who can't see it. They can click on the pause button and stop being distracted. 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 5:10 PM, Patrick H. Lauke <redux@splintered.co.uk> wrote: > On 31/08/2017 22:03, David MacDonald wrote: > >> We wouldn't interpret it that way. >> > > While I appreciate your very economical answers...indulge me: what would > you not interpret that way? As in, more explicitly: you have an > auto-scroller on a site's homepage, it has a pause button. Is that a pass > for 2.2.1 or a fail (as there was no mechanism to pause/stop "before > encountering it" since it's on the homepage)? > > 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 3:58 PM, Patrick H. Lauke <redux@splintered.co.uk >> <mailto: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 <tel:613.235.4902> >> >> LinkedIn >> <http://www.linkedin.com/in/davidmacdonald100 >> <http://www.linkedin.com/in/davidmacdonald100>> >> >> twitter.com/davidmacd <http://twitter.com/davidmacd> >> <http://twitter.com/davidmacd> >> >> GitHub <https://github.com/DavidMacDonald >> <https://github.com/DavidMacDonald>> >> >> www.Can-Adapt.com <http://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 >> <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> >> <mailto: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> >> <http://www.splintered.co.uk> | >> https://github.com/patrickhlauke >> <https://github.com/patrickhlauke> >> <https://github.com/patrickhlauke >> <https://github.com/patrickhlauke>> >> http://flickr.com/photos/redux/ >> <http://flickr.com/photos/redux/> >> <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 <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 Wednesday, 6 September 2017 00:37:33 UTC