- From: <bugzilla@jessica.w3.org>
- Date: Tue, 11 Jan 2011 19:26:09 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11593 --- Comment #9 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-01-11 19:26:08 UTC --- (In reply to comment #0) > The current @kind attribute of <track> > (http://dev.w3.org/html5/spec/Overview.html#the-track-element) only allows for > the following kinds of content: > > Subtitles > Captions > Descriptions > Chapters > Metadata > > The Accessibility Task Force Media Sub-Team have identified the following types > of alternative content that should be made available to meet all User needs: > > Text-based: > Text video description "text video description" is identical to "description" - already covered > Extended text video descriptions This adds the pausing feature to "description", i.e. a means to make a description cue last longer than the available synchronized time with the video. IMO it's a feature that should be available to all "description" kinds of content, so doesn't need a new kind. > Captioning "Captioning" is identical to "Captions" - already covered > Enhanced captions/subtitles This has been a matter of discussion for a while and the answer has thus far been to use the "Metadata" type and run your own enhanced captions/subtitles. > Transcripts "Transcripts" are not provided in chunks in sync with the video, but as a block of text, so these do not need to be provided through @kind. Example uses of transcripts are shown here: - external linked resource: http://www.annodex.net/~silvia/a11y_bcp/demo1_transcript.html - scrolling transcript: http://www.annodex.net/~silvia/a11y_bcp/demo2_transcript.html > The enumerated list table should be extended to address these KINDS of > alternative content. Other than extended captions/subtitles, which can right now be satisfied through "Metadata", nothing is missing IMHO. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 11 January 2011 19:26:12 UTC