- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Fri, 10 Mar 2006 23:19:12 +0000 (GMT)
- To: w3c-wai-ig@w3.org
> parent item? Do you have to listen through all the menu options > you've already heard in order to discover and hear the new sub-menu? In my view, authors shouldn't have been forced to write their own browsers for menus, but rather the menu should have been handled by a separate document referenced by a link element (it might even have used gopher, in which case one would have ended up with something like the proposed structure that could be put together by the browser. However that isn't going to happen now. > > As an alternative, I'm considering a series of linked lists instead > of one complex nested list. In the following example, the Products The basic problem with this is it violates the concept of a markup language, i.e. that you take a valid plain text document and decorate it. PDF does use this sort of structure, but whilst it is textual (it looks binary only because of compression) it isn't a markup up language.
Received on Friday, 10 March 2006 23:28:23 UTC