W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2012

Keyboard & Youtube and Pause Stop Hide

From: Pierre Frederiksen <Pierre.Frederiksen@visionaustralia.org>
Date: Wed, 28 Mar 2012 16:09:46 +1100
To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <240E0CBEFB64614AB97EFCA9F39A508227BF8B824F@VAE2K7CCR.visionaustralia.org>
Hi

I would be great to hear your opinion on these two (finer?) points regarding WCAG 2.0 conformance:

2.1.1 Keyboard
Currently the standard Flash YouTube player is not keyboard accessible in Firefox, Chrome and Safari. Only Internet Explorer provides keyboard access to the content.
Does this mean that the standard YouTube player fails this Success Criteria or is this a question of browser capability and not the responsibility of content creators?
The Flash technique for providing keyboard access
www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100708/flash.html#FLASH17<http://www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100708/flash.html#FLASH17>
only works for Firefox

2.2.2 Pause, Stop, Hide
Consider a slide show that automatically changes the slide and does so continually until the user intervenes. The slideshow contains buttons that can be used to change to each of the slides (e.g. buttons 1,2,3,4,5)
Should an explicit pause button (either with the word Pause or with the pause symbol) be provided, or is it sufficient if the slideshow stops the automatic movement as soon as one of the slide selector buttons has been clicked?

The WCAG "Understanding" document states:

"For a mechanism to be considered "a mechanism for the user to pause," it must provide the user with a means to pause that does not tie up the user or the focus so that the page cannot be used. The word "pause" here is meant in the sense of a "pause button" although other mechanisms than a button can be used. Having an animation stop only so long as a user has focus on it (where it restarts as soon as the user moves the focus away) would not be considered a "mechanism for the user to pause" because it makes the page unusable in the process and would not meet this SC."


*         It states that 'other mechanisms" than a button can be used.

*         The reason that the focus solution is rejected is not that is doesn't have an explicit pause button, but that is unusable (because if you focus on other content the slideshow starts again).
So you would think that if the slideshow stops once one of the slide selector buttons has been pressed it is OK?

Thanks heaps
Cheers
Pierre



________________________________
Did you know Vision Australia provide a Web Accessibility consultancy, training and testing services to help organisations make their online services accessible to as wider user base as possible. To find out more visit www.visionaustralia.org.

ABN: 67 108 391 831 ACN: 108 391 831

Vision Australia is a partnership between people who are blind, sighted or have low vision. We are united by our passion that people who are blind or have low vision will have access to and fully participate in every part of life they choose.

This email (including its attachments) is confidential and may contain legally privileged material or personal information. If you are not a named addressee you must not use, disclose, copy, disseminate or print the email or any information in it. If you have received this email in error please notify us immediately and delete the email and any copies.

Vision Australia is not responsible for any changes made to a document other than those made by Vision Australia or for the effect of the changes to the document's meaning. Vision Australia accepts no liability for any damage caused by this email or its attachments due to viruses, interference, interception, corruption or unauthorised access.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
Received on Wednesday, 28 March 2012 05:10:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 March 2012 05:10:28 GMT