- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Tue, 19 Apr 2011 20:00:38 +1000
- To: Philip Jägenstedt <philipj@opera.com>
- Cc: public-html-a11y@w3.org
On Tue, Apr 19, 2011 at 6:29 PM, Philip Jägenstedt <philipj@opera.com> wrote: > On Tue, 19 Apr 2011 03:44:33 +0200, Silvia Pfeiffer > <silviapfeiffer1@gmail.com> wrote: > >> NOTE: This could be enabled through encouraging publishers to us >> @autoplay, encouraging UAs to implement accessibility settings that >> allow to turn off all autoplay, and encouraging AT to implement a >> shortcut key to stop all autoplay on a Web page. > > Note that Opera already has a user preference for disabling autoplay, see > opera:config#Multimedia Nice one! > As for stopping all playing elements, that is not related to autoplay, since > to be effective it would also have to stop elements that were started by > scripts. Our assumption was that it was not possible to stop script created "autoplay". > Possible solutions here are: > > 1. Requiring explicit approval for all media playback, with the possibility > of remembering approval per domain. > > 2. Exposing a list of all media elements associated with a document to > scripts so that extensions could find and pause all media elements. > Currently this is not possible because elements can be created by scripts > and set to play without being inserted into a document, so e.g. > document.querySelector('audio,video') does not find them. These are both good ideas. Would it be possible to get them through plugins? Or do they need a JS API? Silvia.
Received on Tuesday, 19 April 2011 10:01:26 UTC