- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Thu, 15 Sep 2011 14:32:22 -0400
- To: "GAUSMAN, PAUL" <pg2483@att.com>
- Cc: Robert Pearson <robert.pearson@ami.ca>, "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
There is a multitrack API in HTML5 which allows you to synchronize separate audio and video resources to each other. Is that what you are after? Cheers, Silvia. On Thu, Sep 15, 2011 at 2:30 PM, GAUSMAN, PAUL <pg2483@att.com> wrote: > Everyone, > > > > Excuse me if I’m not using this email correctly. I’ll keep my comment short. > > > > It seems that something which HTML5 should provide, now that it includes > temporal media e.g. audio and video, is temporal controls, like mechanisms > to synchronize media across a page, across apps or across devices. I don’t > see a way to do this within HTML5 proper. > > > > Does anyone have any suggestions how this would be done using only HTML5? > > > > If I should submit this another way, please let me know and I’ll do that. > > > > Thanks! > > -Paul > > > > Paul Gausman, Multimedia Service Architect > > Ecosystem & Innovation > > AT&T Applications and Services Infrastructure > > 908-848-5435 > > "Don't text and drive!" > > > > From: public-web-and-tv-request@w3.org > [mailto:public-web-and-tv-request@w3.org] On Behalf Of Robert Pearson > Sent: Thursday, September 15, 2011 7:30 AM > To: Silvia Pfeiffer > Cc: public-web-and-tv@w3.org > Subject: Re: Web and TV Accessibility > > > > H Silvia, > > > > Certainly, I think all if the required structures have been considered and > in several cases, overall the accessibility of television will be enhanced > with HTML 5 over standard TV with things like extended audio description and > sign language tracks. > > > > Two questions come to mind. > > > > - Were there considerations for the protection and security of copyright > media content when displayed using HTML 5? > > - Quality Standards. This may have been beyond the realm of consideration > for the group, but while the structures are there, what standards would > indicate the quality of the audio description or closed captioning and would > they be different for TV on the web than for regular TV? An example, how > would 3d content be described or captioned for the web or other device if it > was originally created to be viewed on a 3d TV screen? > > > > I look forward to hearing your thoughts. > > > > Regards, > > Robert Pearson > > > > On 2011-09-15, at 1:32 AM, "Silvia Pfeiffer" <silviapfeiffer1@gmail.com> > wrote: > > Are you aware of the <track> element in HTML5 and all the different kinds of > timed text tracks it can provide to video? These include captions, > subtitles, descriptions, and chapters (as in: navigation), as well as > multitrack audio and video support (for audio descriptions and sign > language). Also, there was a media group in the accessibility task force of > HTML5 which specified a requirements list, see > http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Requirements . Is > there any requirement you have that is not yet considered? > > Regards, > Silvia. > > > > ________________________________ > > This email, including any attachments, is intended only for the person(s) to > whom it is addressed and may contain confidential and/or privileged > information. Any unauthorized distribution, disclosure or use is prohibited. > If you are not the intended recipient of this email, please contact the > sender and delete this email, including any attachments, immediately. Thank > you.
Received on Thursday, 15 September 2011 18:33:10 UTC