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

RE: Web Accessibility Examples

From: Dave J Woolley <david.woolley@bts.co.uk>
Date: Thu, 5 Oct 2000 19:58:04 +0100
Message-ID: <81E4A2BC03CED111845100104B62AFB5824AA0@stagecoach.bts.co.uk>
To: w3c-wai-ig@w3.org
> From:	Ball, Guy D [SMTP:Guy.Ball@unisys.com]
> 
> I'm working on an article on web accessibility for a national e-business
> publication and I need this group's help.  
> 
	[DJW:]  I'll try and reply on most points off list,
	but I'll mention one point here.

> Java roll-over, fly-out menu to help select where you want to go
	[DJW:]  
	I think you mean JavaScript, not Java.

	The main JavaScript problem these days is not roll-overs,
	and pop-ups are fairly rare.  The real problem is where
	it is used to create side effects to following a link.

	Almost always, in my view, this can be done in a way that
	degrades gracefully and is functionally indistinguishable to
	a script user, but this is rarely done.

	Most commonly, the link has <a href="javascript:....>.  Sometimes
	it uses onclick, with a functionless href (possibly javascript:,
	again.

	The result, in both cases, is an apparent link that is completely
	dead without javascript.

	I am pretty certain that the desired effect can always be
	achieved by making the actual link a normal href and using
	an onclick action that does what would have been in the
	javascript: URL, then returns false to stop the browser also
	trying to action the href (assuming that this would cause a
	problem).


-- 
--------------------------- DISCLAIMER ---------------------------------
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of BTS.
Received on Thursday, 5 October 2000 14:58:10 GMT

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