11391 2010-11-23 16:37:01 +0000 Provide examples of actual <track> usage, user agent implications 2012-01-13 20:29:37 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All CLOSED FIXED a11y, a11ytf, media P2 normal --- 11593 1 franko jfoliot cooper jfoliot laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking silviapfeiffer1 w3c public-html-bugzilla oldest_to_newest 42724 0 franko 2010-11-23 16:37:01 +0000 http://dev.w3.org/html5/spec/video.html#timed-track The specification should specify different kinds of actual content files (timed or untimed track files) that may be associated with a media resource: A textual representation of the content An audio representation of the content (See SL-1, SL-2 in [1]) A video representation of the content Non-synchronized alternatives that can be rendered as replacements for the original rendered content (DAC-5 in [1]) [1] http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Checklist SUGGEST: http://dev.w3.org/html5/spec/video.html#dom-track-src The src attribute points to an additional timed or untimed textual, audio or video representation of the media content that the user or user agent may display. The rendering of the alternative / replacement content is defined by the actual track format and the user agent; for example: Non-synchronized alternatives may be rendered as replacements for the original rendered content A additional video representation of the original content may be rendered over the original content, or positioning in all parts of the screen. (CC-5 in [1]) [1] http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Checklist 42741 1 franko 2010-11-24 02:27:45 +0000 Additionally, to satisfy... (DV-8) Allow the author to provide fade and pan controls to be accurately synchronized with the original soundtrack. (CN-2) The navigation track should provide for hierarchical structures with titles for the sections. ...from http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Checklist Suggested spec text: When a track is enabled (and depending on the type of track), the playback rate of a media element may be (temporarily) stopped, slowed down, or sped up to enable to user to understand the content. The user agent may also enable the user to navigate to time offsets in the original content. Additionally, user agents should ensure that the presentation of the time-based original content and track content should always be in sync. 44015 2 w3c 2011-01-10 19:40:55 +0000 Adding dependency on bug 11593 as that one addresses alternative @kind attribute values. 44153 3 w3c 2011-01-11 17:09:50 +0000 The bug-triage sub-team thinks this bug should be TF priority. It has been discussed at TPAC and is part of the media accessibility topic. 44172 4 w3c 2011-01-11 18:07:34 +0000 Assigning to John Foliot to push the issue in the media sub-group. 46854 5 cooper 2011-03-19 23:54:06 +0000 This is related to ISSUE-152 http://www.w3.org/html/wg/tracker/issues/152 53761 6 mike 2011-08-04 05:17:04 +0000 mass-move component to LC1 60197 7 mike 2011-11-20 15:09:43 +0000 See comment #4 from Martin: > Assigning to John Foliot to push the issue in the media sub-group. John, any progress on this yet? 60262 8 silviapfeiffer1 2011-11-20 21:36:27 +0000 The media a11y TF has helped created spec text to resolve basically all of the accessibility needs in the checklist. The issues that Frank pointed out have been taken care of - some of them in the way that Frank proposed, others differently. I think the onus is on Frank to state whether he still has any pending issues on this bug. 60267 9 mike 2011-11-21 00:11:03 +0000 (In reply to comment #8) > The media a11y TF has helped created spec text to resolve basically all of the > accessibility needs in the checklist. The issues that Frank pointed out have > been taken care of - some of them in the way that Frank proposed, others > differently. > > I think the onus is on Frank to state whether he still has any pending issues > on this bug. Frank is not Cc'ed on this bug. So if it's the case that we're waiting for a response from Frank, can somebody (John? Silvia?) please give Frank a heads-up that we are waiting for a response from him on this? 60268 10 mike 2011-11-21 00:12:23 +0000 (In reply to comment #9) > Frank is not Cc'ed on this bug. So if it's the case that we're waiting for a > response from Frank, can somebody (John? Silvia?) please give Frank a heads-up > that we are waiting for a response from him on this? um, er, only after I posted that comment did I realize that Frank's not in the Cc list because he's the reporter for the bug... So ignore my comment of course. Sorry for the noise. 60364 11 franko 2011-11-23 06:54:05 +0000 (In reply to comment #10) > (In reply to comment #9) > > Frank is not Cc'ed on this bug. So if it's the case that we're waiting for a > > response from Frank, can somebody (John? Silvia?) please give Frank a heads-up > > that we are waiting for a response from him on this? > > um, er, only after I posted that comment did I realize that Frank's not in the > Cc list because he's the reporter for the bug... > > So ignore my comment of course. Sorry for the noise. As John points out, we now have spec text that addressed the issues raised in this bug; we can resolve this bug as fixed. 60365 12 mike 2011-11-23 06:57:26 +0000 (In reply to comment #11 from Frank) > As John points out, we now have spec text that addressed the issues raised in > this bug; we can resolve this bug as fixed. Thanks -- moving this to resolved=fixed now