W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2008

[whatwg] Thoughts on video accessibility

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 10 Dec 2008 03:49:26 +1100
Message-ID: <2c0e02830812090849i51df5d17w14b9a47466e494f9@mail.gmail.com>
I heard some complaints about there not being any implementation of
the suggestions I made.

So here goes:

1. out-of-band
There is an example of using srt with ogg in a out-of-band approach here:
http://v2v.cc/~j/jquery.srt/
You will need Firefox3.1 to play it.
The syntax of what Jan implemented is different to what I proposed,
but I wanted to take it forward and make it more generic.

2. in-band
There is also a draft implementation of srt inside Ogg through the
OggText specification, but I it's not released yet. It is also not as
relevant to this group as the out-of-band example.

Cheers,
Silvia.



On Tue, Dec 9, 2008 at 7:33 PM, Robert O'Callahan <robert at ocallahan.org> wrote:
> On Tue, Dec 9, 2008 at 6:20 PM, Martin Atkins <mart at degeneration.co.uk>
> wrote:
>>
>> Silvia Pfeiffer wrote:
>>>
>>> I'm interested to hear people's opinions on these ideas. I agree with
>>> Ralph and think having a simple, explicit mechanism at the html level
>>> is worthwhile - and very open and explicit to a web author. Having a
>>> redirection through a ROE-type file on the server is more opaque, but
>>> maybe more consistent with existing similar approaches as taken by
>>> RealNetworks in rm files and WindowsMedia files in asx files.
>>>
>>
>> This (having a separate document that references other streams) is what I
>> was thinking of. I guess which is more natural depends on who is doing the
>> assembling. If it is the HTML author that takes the individual pieces and
>> links them together then doing it in the HTML is probably easiest.
>
>
> For what it's worth, loading an intermediate document of some new type which
> references other streams to be loaded adds a lot of complexity to the
> browser implementation. It creates new states that the decoder can be in,
> and introduces new failure modes. It creates new timing issues and possibly
> new security issues.
>
> Rob
> --
> "He was pierced for our transgressions, he was crushed for our iniquities;
> the punishment that brought us peace was upon him, and by his wounds we are
> healed. We all, like sheep, have gone astray, each of us has turned to his
> own way; and the LORD has laid on him the iniquity of us all." [Isaiah
> 53:5-6]
>
Received on Tuesday, 9 December 2008 08:49:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:46 UTC