- From: Ian Hickson <ianh@netscape.com>
- Date: Tue, 17 Oct 2000 16:11:15 -0700 (Pacific Daylight Time)
- To: Sean Palmer <wapdesign@wapdesign.org.uk>
- cc: www-style@w3.org
Sean Palmer wrote: > [...snip interesting proposals...] As I understand it, the problem is that a document contains a navigation bar, and the WAI guidelines say that this navigation bar should be made easy to skip so as not to bore aural browser users. Is this correct? Assuming that this is indeed the problem, then there are already at least five existing solutions: 1. In the content, include a "skip" link that points to just after the navigation bar. Then, in the CSS stylesheet, hide that link for visual browsers. 2. Aural browsers could implement a feature whereby saying "skip" automatically jumps to the end of the current (deepest) element, or jump to the end of the element that contains the end of the current sentence, or some such. 3. The content could be transformed using XSLT to include a skip link if the media is aural. 4. The navigation bar could be given using elements explicitly designed for this (<link> in HTML) so that the UA will be able to automatically handle the skipping of the navigation bar. 5. The navigation bar could be given using out-of-band data such as HTTP "Link" headers or an XLink file, and again handled specially by the UA. Given that there are already at least five solutions to this problem, some of which have been defined since the early 90s, some of which have only recently entered Candidate Recommendation stage, is there any reason to introduce a sixth solution at the draft stage? -- Ian Hickson )\ _. - ._.) fL Netscape, Standards Compliance QA /. `- ' ( `--' +1 650 937 6593 `- , ) - > ) \ irc.mozilla.org:Hixie _________________________ (.' \) (.' -' __________
Received on Tuesday, 17 October 2000 19:13:45 UTC