W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2002

Re: Browser Issues

From: Jim Ley <jim@jibbering.com>
Date: Wed, 27 Feb 2002 13:17:48 -0000
Message-ID: <046101c1bf91$2913a140$ca969dc3@emedia.co.uk>
To: "WAI \(E-mail\)" <w3c-wai-ig@w3.org>
"RUST Randal" <RRust@COVANSYS.com>
> >> Which makes me breathe a sigh of relief.  I know that there are
> >accessible
> >> ways to use Javascript,
> >
> >You do?  Would you care to expand on them, people with that knowledge
> >seem extremely thin on the ground and
> >http://www.learningdifficulty.org/develop/w3c-scripts.html is always
> >looking for examples.
> > An accessible use of Javascript:

Unfortunately not... (see below) - However your example is different to
what was said in the quoted text in yout post - your example degrades
without javascript, so javascript is _not_ required for access to the
content.

> example:  <a href="new.htm" onclick="window.open('new.htm');" return
> false">text</a>

This has recently been discussed in www-validator (perhaps not the best
place) and there are a number of scenarios where it fails (returning
false cancels the navigation even if the window doesn't open -
http://lists.w3.org/Archives/Public/www-validator/2002Feb/0121.html has
more discussion and a solution (which has only potential script errors in
various browsers including Mozilla as a concern)

> Take a look at this for more information:
> http://www.webreference.com/new/020221.html

Yes, all very trivial - like all examples of "accessible scripting", but
still somewhat useful (although demonstrating techniques which are
better, but still don't work across current browsers.) - window.open is
also of course in no standard.  Some non-trivial examples - some which
actually reflect the ways script is used by inaccessible sites would be
nice to see.

Jim.
Received on Wednesday, 27 February 2002 08:19:55 GMT

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