- From: Philip Jägenstedt <philipj@opera.com>
- Date: Wed, 06 Jul 2011 10:33:38 +0200
- To: public-html@w3.org
On Fri, 01 Jul 2011 16:29:23 +0200, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > Hi Paul, all, > > after analyzing this problem thoroughly, which I have documented [1], > I have come to the conclusion that there is no need for introduction > of any normative text into the specification to satisfy this use case. > > Right now, we have a linear navigation means through text tracks of > kind chapter. > > IMO the best means to provide hierarchical navigation, which is > particularly useful to vision-impaired users, is to make it possible > to provide navigation lists inside the cues that make up > kind="chapters" track. As such cues are handed to AT, their markup is > interpreted and made available to AT, including any associated lists. > > My only suggestion would be to potentially add a recommendation to the > specification underneath where "chapters" are introduced [2] > which essentially states that subnaviation within chapter cues should > be provided through list elements (ul,li) inside a chapter's cue. There are no list elements in WebVTT, are you suggesting they be added? To provide a chapter tree, would it not be better to have dedicated syntax for it? Perhaps: 00:00.000 --> 01:00.000 1. Foo 00:00.000 --> 00:30.000 1.1. Foo, Part 1 00:30.000 --> 01:00.000 1.2. Foo, Part 2 The spec would need to add some parsing for kind=chapters, to deduce the level of nesting from the leading x.y.z... I'm not convinced this should be added to the spec right away, some experimentation with chapters using JavaScript would be a good first step. -- Philip Jägenstedt Core Developer Opera Software
Received on Wednesday, 6 July 2011 08:34:12 UTC