- From: Eric Carlson <eric.carlson@apple.com>
- Date: Tue, 12 Oct 2010 12:42:22 -0700
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
On Oct 8, 2010, at 12:19 PM, Silvia Pfeiffer wrote: > ... it was determined that these are artefacts of production of the caption file in relation to the video resource and that they should be fixed *before* publishing the caption file on a Web server, thus they would never need to be fixed on the Web page. > > One has to understand that the use case for captions on the Web is here different to the use case for offline. On the Web, the person that publishes the captions would publish them with relation to a particular video resource. Therefore, they can fix up the skew. Offline, the caption files are published as a collection and people that download a movie go looking for a caption file for that movie, then synchronise it through their player. This is not what would happen on the Web. Therefore, it is probably indeed unnecessary to have these parameters and this requirement. > > I would therefore recommend at this stage not to introduce these requirements. They may only add to the complexity of the solutions that we need to introduce and I don't see there being a need. If it later turns out that a lot of people have to fix up the timing of the media resource manually with JavaScript (which can always be used to fix this), then we can introduce it later. I would actually prefer if the publishers of caption files would use a convenience tool instead that doesn't put this burden on the Web browser. > I agree with Silvia, we don't want to encourage sloppy authoring practices. eric
Received on Tuesday, 12 October 2010 19:42:59 UTC