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

RE: accessible css rollovers WAS whitespace, navigation links, styled divs

From: Andrew Johns <andrew.johns@jkd.co.uk>
Date: Fri, 9 Aug 2002 10:04:38 +0100
Message-ID: <FDFC0668A850D246BC4231715D94904E266C4C@uranus.jkd.co.uk>
To: <w3c-wai-ig@w3.org>

> On a similar theme Mr Meyer also has a way of creating pure css roll-overs
> that look great for the browsers that support it but I'm wondering how they
> will 'sound' in a screen-reader and look in a text-browser. They work thus:

> <a href="path/to/page.htm">link text<span>roll-over text</span></a>

> the <span> is set to display:none and then using a:hover it is set to
> display:block with fixed positioning. My first thought is that the roll-over
> text will get read out in screen-readers as part of the link text because it
> is contained within the <a> tags but I can't see another way of creating the
> same effect that would be accessible. Any ideas?



I've always assumed that the most accessible way of doing rollovers was to use css classes, which change onmouseover/onmouseout onblur/onfocus, which according to the guidelines is acceptable, as it'll work in browsers that support javascript and if it's turned off, it doesn't affect the navigation.

Is this the wrong method?

Kind Regards,

Andy
Received on Friday, 9 August 2002 05:04:41 GMT

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