- From: <nir.dagan@econ.upf.es>
- Date: Fri, 6 Nov 1998 08:13:57 +0100
- TO: charlesn@srl.rmit.EDU.AU
- CC: asgilman@access.digex.net, w3c-wai-gl@w3.org
> The idea is that UAs allow browsing by structural divisions. The common > ones are headings, but HTML provides two elements to mark out otherwise > unknown tyes of division - SPAN and DIV. If we group links together in a > DIV (for example with CLASS="nav", TITLE="nav") then we would hope that > people can either go deeper or skip that DIV. I think that usually links that have something to do together are already grouped in some element like P or UL or TABLE, so there is no need for DIV here. > > if we standardise the CLASS then people can write a stylesheet to do what > they really want with the DIV - shift it to the end, repeat it > everywhere, etc. It means that UAs 'could' recognise it and do clever > things as well, although most of those are likely to be the sort of > things that properly implemented CSS would already provide. The use of LINK elements should do that. They are in the HEAD and the user agent/user should decide where and how to show them. If there is no particular "rel" to use, use title with the link description. Let: <LINK title="Skip navigation links" href="#start-reading-here"> be your first LINK, and you are done. Regards, Nir Dagan http://www.nirdagan.com
Received on Friday, 6 November 1998 02:14:11 UTC