WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXTERNAL]SC 2.2.2 Pause, Stop, Hide - meaning of "starts automatically"

for

From: Mark Magennis
Date: Mar 18, 2021 7:58AM

I don't want to harp on and on about this for too long, but to me the logical thing would have been not to even mention the "starts automatically" thing. But presumably someone thought about it and decided "we need that" on the basis that manual activated functions are different and should be allowed to distract the user. I can't see why though. There's no example in the Understanding document of something not being a failure because it was not automatic.

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Patrick H. Lauke
Sent: 18 March 2021 13:15
To: <EMAIL REMOVED>
Subject: Re: [WebAIM] [EXTERNAL] Re: SC 2.2.2 Pause, Stop, Hide - meaning of "starts automatically"

On 18/03/2021 12:54, Mark Magennis wrote:
>> I would assume the rationale is "well, if you find it distracting, just don't do it", and in part "it's not jumping at you/surprising you, you know what you're in for".
>
> That can't be the rationale. WCAG would not sanction an approach of "If a function causes the application to be inaccessible to some users then tell them not to use it". Or "They should have know that this might prevent them from doing any other work, so that's okay".

The likely simpler answer is: nobody thought of that scenario when the SC and its understanding docs were written up... (as we so often find when we start poking hard at SCs and it turns out that "nobody could have foreseen this...")

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke