- From: Eric Carlson <eric.carlson@apple.com>
- Date: Wed, 25 Nov 2009 13:49:40 -0800
- To: Philip Jägenstedt <philipj@opera.com>
- Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
On Nov 25, 2009, at 12:02 PM, Philip Jägenstedt wrote: > On Wed, 25 Nov 2009 18:43:39 +0100, Eric Carlson <eric.carlson@apple.com > > wrote: > >> >> I think <overlay> should be used for internal subtitle and/or >> closed caption tracks as well. Further, I think that we will want >> them to "just work" so a UA should create an <overlay> element if >> the markup doesn't have one and it finds that a file has internal >> captions/subtitles: >> >> <video src='my-captioned-movie'> </video> >> > > Yes, that sounds good. One issue is how to style such an implicit > <overlay>. Should one actually include an <overlay> in the markup > and somehow indicate that it can/should be used to render in-band > subtitles from the resource? > > <video src="my-captioned-movie"> > <caption style="font-weight:bold" magic-attribute></caption> > </video> > > Not awesome. Perhaps a new CSS pseudo-selector could be used? Other > ideas? > Actually I was imagining that *all* subtitles and captions, in-band and external alike, would be rendered into an <overlay>. If the markup doesn't includes an <overlay> element the UA would actually insert one into the DOM, as is done now for other missing elements (eg. tbody, etc). This way the default style could be specified in the user agent style sheet and the author could override as they wish. Speaking of author overrides, another issue we need to deal with is authors that wish to handle captions themselves. Posting an event when a new caption needs to be displayed seems logical enough, but how do we provide access to the caption data in JavaScript? eric
Received on Wednesday, 25 November 2009 21:50:21 UTC