W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2001

Re: Tree Navigation - Javascript

From: Jim Ley <jim@jibbering.com>
Date: Wed, 5 Dec 2001 10:40:41 -0000
Message-ID: <005501c17d79$4e150600$ca969dc3@emedia.co.uk>
To: <w3c-wai-ig@w3.org>
"David Woolley":
> > http://www.learningdifficulty.org/develop/w3c-scripts.html#navigation
>
> Looking a little further, the problem is that everything fits on one
page,
> so it is not possible to move the viewport to indicate the new position
> in the document.  In any case, the menus run together on one line, so
even
> if there were enough space above and below them to allow the viewport
to
> be positioned, it wouldn't be possible to unambigously determine which
> menu had been reached.

You're describing the fallback content (ie no script popup menu) which in
that example is severely sub-optimal (just fragment links.), Someone used
it for http://www.rcslt.org/ with more sensible fallback, which may be
worth looking at it in a real situation. I have identified an error with
Konquerer (that doesn't deny accessibility, it's just a bit weird.) in
that it doesn't understand parentElement properly so you only get the
first menu item "popping up". (well I've not looked in detail as to
what's gone wrong, but it seems to interpret it differently to Mozilla
and IE and how I interpret it to mean.)

The menus running together etc. are all HTML issues, and as such I don't
worry about them in test scripts.  I'm still not happy it is fully
accessible, if it ever does become so, I'll definately write it up and
provide a url where its use can be explained, I wouldn't consider
recommending it to someone who doesn't understand script yet though.

Jim.
Received on Wednesday, 5 December 2001 05:41:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:58 GMT