E-mail List Archives
Thread: Re: Re: Javascript Rollovers and accessibility
Number of posts in this thread: 4 (In chronological order)
From: Lori K. Brown
Date: Tue, Jan 21 2003 6:56AM
Subject: Re: Re: Javascript Rollovers and accessibility
No previous message | Next message →
I don't get how javascript-based image rollovers impair
accessibility.
If the links are wrapped around images that have alt text, what does
it matter if visually impaired users don't have access to what is
(usually) principally a decorative effect? If all the actual content
is presented clearly and properly labeled, what is the problem?
Lori Kay Brown
User Interface Engineer
SiteScape, Inc.
E-mail: = EMAIL ADDRESS REMOVED =
-------- Original Message --------
==> From: "Mark Rew" < = EMAIL ADDRESS REMOVED = >
==> Date: Tue, 21 Jan 2003 08:11:01 -0500
My experience is that these rollovers are not accessible to someone
who does not use a mouse such as a screen reader user.
Either provide a set of separate links or a separate page without
rollovers. After accessibility problems, and other problems with
different browsers and equipment not being able to use the rollovers
my shop redesigned our pages so rollovers are not needed.
Mark Rew
----- Original Message ----- From: chet To:
= EMAIL ADDRESS REMOVED = Sent: Tuesday, January 21, 2003 7:59 AM
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: John Foliot - bytown internet
Date: Tue, Jan 21 2003 7:03AM
Subject: RE: Re: Javascript Rollovers and accessibility
← Previous message | Next message →
None.
>
From: tedge
Date: Tue, Jan 21 2003 7:17AM
Subject: RE: Re: Javascript Rollovers and accessibility
← Previous message | Next message →
Quote " 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 think IBM sums it up best:
If the nature of the script is to enhance the visual affects only, but
not to communicate additional necessary information, then no additional
accessibility techniques are required. For example, onMouseOver to
highlight the item by changing the background color or to produce purely
decorative effects such as highlighting an image or changing the color
of an element's text do not require additional accessibility techniques.
If the essential tasks of the web site can be accomplished with
scripting turned off or in a browser that doesn't support scripting,
then the scripting is consider non-essential (redundant) and does not
need to be directly accessible. Even though the user interface is
affected and processing occurs as a result of scripts, the scripts may
not be essential in using the function provided by the site. However,
this checkpoint does not prohibit the use of directly accessible
essential scripts nor does it require alternatives for directly
accessible essential scripts.
http://www-3.ibm.com/able/webscripts.html
I believe this is in agreement with section 508:
When pages utilize scripting languages to display content, or to create
interface elements, the information provided by the script shall be
identified with functional text that can be read by assistive
technology. 1194.22(l)
And with the WCAG:
6.3 Ensure that pages are usable when scripts, applets, or other
programmatic objects are turned off or not supported. If this is not
possible, provide equivalent information on an alternative accessible
page.
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/
From: Jon Gunderson
Date: Tue, Jan 21 2003 4:18PM
Subject: On-line course on designing universally accessible web resources
← Previous message | No next message
On line course on Designing Universally Accessible Web resources will start
on February 18th. The course is 16 sessions and is designed to help web
developers understand disability access issues, and accessible web design
for HTML, multimedia and PDF.
More information available at:
http://cita.rehab.uiuc.edu/courses/2003-02-REHAB711NC/index.html
If you have any questions please contact Jon Gunderson at = EMAIL ADDRESS REMOVED = .
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/