Talk:SC2-2-2-pause-stop-hide

Open issues

• Step 3: Else-statement should return "inapplicable". If there is no moving/scrolling/blinking content the test is not applicable.

Annika Nietzio (talk) 14:56, 11 February 2016 (UTC)

Ready for review

• In Understanding SC 2.2.2 the scope is defined as: "moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content". Couldn't moving, scrolling and blinking content be summarized from Step 3 downwards, as all criteria are applicable to it, even if not explicitely written in the techniques?

Frank Berker (talk) 07:52, 14 October 2015 (UTC)

Closed issues

• We can merge the questions of steps 5 and 6

Wilco Fiers (talk) 14:33, 14 October 2015 (UTC)

Step 4 - checking for keyboard accessibility of pause/stop/hide control.

I have seen a lot of cases where auto-updateing content can be stopped through mouse actions only. Though that would be failure of other success criteria, such as 2.1.1 (possibly 4.1.2/3.3.2 depending on the quality and labeling of the elements used to do this), I still wonder if this is not the best place to catch this potential issue, particularly the keyboard accessibility. I am not saying I am 100% sure that this is the appropriate spot, but a page containing auto-updating content can be a user blocker for e.g. users of screen readers, so making sure users can pause/stop/hide the content without requiring a mouse is a situation with high user impact. Since this approach would be very atypical of the auto WCAG strategy this may not be a good idea, but I wanted to bring it up for discussion.