E-mail List Archives
Thread: RE: Javascript Rollovers and accessibility
Number of posts in this thread: 2 (In chronological order)
From: julian.rickards@ndm.gov.on.ca
Date: Tue, Jan 21 2003 7:42AM
Subject: RE: Javascript Rollovers and accessibility
No previous message | Next message →
There are two forms of javascript rollovers as I have categorized them:
local and remote (my terms but I will explain them). What I call a local
rollover is where the mouse moves over an image and the image at the
position of the mouse changes to another image: for example from a red image
to a blue image. The effect is simply decorative and as long as there is no
additional information on the onMouseOver image that would be missed if
JavaScript was disabled, then this is fine. Remember, of course, to add alt
text to the image or title text to the link.
The other term I use is "remote" mouse overs and that is where moving the
mouse over one image affects another image - for example,
http://www.againsttheclock.com <http://www.againsttheclock.com>; , watch the
top graphic as you mouseOver the navbar links. In this case, the effect is
decorative too, both the top graphic and the navbar graphic. However, if you
go to http://www.mndm.gov.on.ca/mndm/mines/ims/pub/default_e.asp
<http://www.mndm.gov.on.ca/mndm/mines/ims/pub/default_e.asp>; , you will see
that the mouseover left navbar links provides additional information.
However, using the <noscript> tag, the additional information is provided to
the non-JavaScript users.
The basis of the WCAG guidelines that deal with client-side scripting is to
prevent a discrepancy of information between those people who have
JavaScript-enabled browsers and no disabilities (as defined by the audienced
affected by WCAG) and those who either have JavaScript disabled or are using
a non-JavaScript browser, those who are disabled (as defined by the WCAG) or
both. In most cases, rollovers are simply decorative and as such, they
provide no additional information and would be considered acceptable.
However, if any JavaScript does provide additional information, you must
ensure that other methods are also used to provide the information to
JavaScript-disabled users.
HTH,
Jules
-----Original Message-----
From: chet [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Tuesday, January 21, 2003 8:00 AM
To: = EMAIL ADDRESS REMOVED =
Subject: Javascript Rollovers and accessibility
Hi,
I read previous posts, but can't seem to get a clear answer to my question.
If i am using graphics as links and want a rollover effect on them (i.e they
swap images using javascript) - does this meet accessibility requirements?
Reading W3C & other guidelines I believe that using javascript for rollovers
(i.e visual effect only) does not require any additional accessibility
techniques (although i would use the <noscript> to let users with javascript
turned off that it is not conveying essential info).
I am not talking about drop down menu's that i understand aren't generally
accessible (if at all?).
Also, If anyone has used javascript rollovers and complied with
accessibility can i have a look as an example?
Thanks,
Chet (UK).
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/
From: Leo Smith
Date: Wed, Jan 22 2003 7:01AM
Subject: RE: Javascript Rollovers and accessibility
← Previous message | No next message
<snip>
> However, if you go to
> http://www.mndm.gov.on.ca/mndm/mines/ims/pub/default_e.asp
> <http://www.mndm.gov.on.ca/mndm/mines/ims/pub/default_e.asp>; , you
> will see that the mouseover left navbar links provides additional
> information. However, using the <noscript> tag, the additional
> information is provided to the non-JavaScript users.
</snip>
In the case mentioned above the additional information is not
presented to keyboard only users when tabbing through the links -
perhaps using onfocus and onblur for these disjointed rollovers
might solve that issue.
Best,
Leo.
Leo Smith
Web Designer/Developer
USM Office of Publications and Marketing
University of Southern Maine
207-780-4774
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/