W3C home > Mailing lists > Public > public-html-a11y@w3.org > December 2010

Re: [Bug 11395] Use media queries to select appropriate <track> elements

From: David Singer <singer@apple.com>
Date: Thu, 2 Dec 2010 12:13:05 -0800
Cc: "bugzilla@jessica.w3.org" <bugzilla@jessica.w3.org>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
Message-Id: <94C86B50-2312-4568-B711-BC661413847F@apple.com>
To: Sean Hayes <Sean.Hayes@microsoft.com>
I don't think we're in a position to say "you cannot post videos in this class on public web pages".  we're not the www police.

we can certainly say it's ill-advised. and we should say how users and web sites can set things up so as inadvertent exposure happens.

On Dec 2, 2010, at 2:52 , Sean Hayes wrote:

> Flashing should be an outright prohibition and not a user preference, because those susceptible might not find out until after the damage is done.
> -----Original Message-----
> From: public-html-a11y-request@w3.org [mailto:public-html-a11y-request@w3.org] On Behalf Of bugzilla@jessica.w3.org
> Sent: 02 December 2010 03:43
> To: public-html-a11y@w3.org
> Subject: [Bug 11395] Use media queries to select appropriate <track> elements
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=11395
> Silvia Pfeiffer <silviapfeiffer1@gmail.com> changed:
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                 CC|                            |silviapfeiffer1@gmail.com
> --- Comment #4 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2010-12-02 03:42:34 UTC --- My understanding of DAC-2 was that we are going to provide a menu that displays all available tracks to the user to let the enable/disable the track display.
> On top of this, there will be user settings in browsers for the preferred tracks to be active by default. If the kind/lang combination of a track matches a user's preferences, the track will automatically be turned on.
> As for the "repetitive stimuation" issue - I guess what you are saying is that a video that e.g. provides strobelight, and can cause seizures, should be marked as such and not play for people who may have indicated such an anit-preference in their browser. Are there any other such use cases where videos are dangerous to certain user groups and must not be shown to them at all (apart from porn, I guess)? I don't really think media queries are the right solution for that (since it's not a property of the display media that we are filtering on, but a user preference). I think it might be better to introduce another attribute for such things, something like @indication which can indicate what audience to avoid (e.g. adult, strobe etc).
> Haven't made up my mind on this though, just thinking out loud...
> --
> Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
> ------- You are receiving this mail because: ------- You are on the CC list for the bug.

David Singer
Multimedia and Software Standards, Apple Inc.
Received on Thursday, 2 December 2010 20:18:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:49 UTC