"I don't think introducing TTML/SRT as a closed system and not exposing it to HTML in any way closes options for the future. And what's more it doesn't leave a legacy we might have to back out of. Right now I'm not seeing any need to expose the text outside of the TTML/SRT rendering engine into the real DOM. If by "Shadow DOM" (option 2) you mean making it available to AT, then I'm OK with that." Well said; I agree with this. The 'media engine' in IE9 is fully integrated in the browser, and we (in theory) could wire up captions into the DOM and fire onCaption events... but I don't think this should be done, as it seems very much like feature creep - What is the use case here? Thanks Frank IE9 From: public-html-a11y-request@w3.org [mailto:public-html-a11y-request@w3.org] On Behalf Of Geoff Freed Sent: Monday, April 05, 2010 5:44 AM To: Sean Hayes; Silvia Pfeiffer Cc: Laura Carlson; Eric Carlson; HTML Accessibility Task Force; Matt May; Philippe Le Hegaret Subject: Re: Requirements for external text alternatives for audio/video On 4/3/10 10:02 AM, "Sean Hayes" <Sean.Hayes@microsoft.com> wrote: Well I'm glad you are not intending to add hyperlinks now, that wasn't very clear from the discussion this far. At an appropriate time I'd love to be engaged in the discussion of the best way to go about that, either extending TTML in some future incarnation of the TTWG or another forum. GF: I'd also be interested in such a discussion whenever it occurs. Note that hyperlinking captions is not a new idea: RealText supports this capability and, if I'm not mistaken, so does SAMI. NCAM did some work with MIT in the late 1990s to show how captions could provide links to ancillary data-- students could click on a linked word in a captioned physics lecture to learn more about a concept being explained by the professor. Geoff WGBH/NCAM I don't think introducing TTML/SRT as a closed system and not exposing it to HTML in any way closes options for the future. And what's more it doesn't leave a legacy we might have to back out of. Right now I'm not seeing any need to expose the text outside of the TTML/SRT rendering engine into the real DOM. If by "Shadow DOM" (option 2) you mean making it available to AT, then I'm OK with that. -----Original Message----- From: Silvia Pfeiffer [mailto:silviapfeiffer1@gmail.com] Sent: Saturday, April 03, 2010 1:33 PM To: Sean Hayes Cc: Laura Carlson; Eric Carlson; Geoff Freed; HTML Accessibility Task Force; Matt May; Philippe Le Hegaret Subject: Re: Requirements for external text alternatives for audio/video
Received on Monday, 5 April 2010 16:48:46 UTC