RE: Navigation
by "John Foliot - Another 4:00 AM Web Thing" <foliot(at)fouram.com>
|
Date: |
Thu, 24 Jan 2002 07:08:06 -0500 |
To: |
<andrew_kirkpatrick(at)wgbh.org>, <aware-techniques(at)hwg.org>, <info(at)mtbytes.com> |
In-Reply-To: |
awk |
|
todo: View
Thread,
Original
|
|
>2) I vote against the mouseovers if they are done at the expense of the
expanded list of links. JAWS 4.01
>now deals with mouseover links to some extent, but not everyone has that
version yet.
If you are going to use mouseOver and mouseOut JavaScript calls, remember to
use onFocus and onBlur as well, so that your "funtionality" is no longer
device dependant. For example:
<a href="./" onMouseOut="MM_swapImgRestore();"
onMouseOver="MM_swapImage('nav_consulting_r1_c1','','_resources/nav_consulti
ng_r1_c1_f2.gif',1);" onBlur="MM_swapImgRestore();"
onFocus="MM_swapImage('nav_consulting_r1_c1','','_resources/nav_consulting_r
1_c1_f2.gif',1);">
<img name="nav_consulting_r1_c1" src="_resources/nav_consulting_r1_c1.gif"
width="65" height="20" border="0" alt="Consulting"></a>
(Astute observers will note that this was originally generated by Fireworks,
and then modified with the inclusion of the onFocus and onBlur event
handlers.)
In this case, the JavaScript is used for decorative purposes... non-visual
and non JavaScript enabled browsers don't get to see the "flashing" button
caused by the roll-over, but they may still access the link. If you insist
on providing important information using JavaScript, remember to also use
the <NOSCRIPT></NOSCRIPT> tags (they work similar to <NOFRAMES>) to include
the important information. No, it may not loook "as nice", but it IS
accessible. In most instances, it is preferred to have mission critical
scripting on the server side as opposed to the client side... at least you
have some control over your machine.
JF
HWG: hwg-basics mailing list archives,
maintained by Webmasters @ IWA