Using the css
Remember my genuine menu that I used previously to show that the Web Standards method of using nested unordered lists for navigation menus allows screenreader users to understand the hierarchy of nested menus?
onmouseover with using the css
:hover pseudoclass on the link.
Since doing the test and posting it (I’ve been on my holidays; it was very nice, thank you) an interesting commenter on Derek Featherstone’s site wrote,
JAWS and others seem to be well intentioned but what I have noticed with the few blind and low vision students we have here is that they turn off as many features as possible … JAWS gives them too much information and it is distracting.
Even though my re-written
:hoverversion doesn’t kill the table layout or use lists, it doesn’t pollute the screenreader user’s ears with repeated useless utterances of “onmouseover” (listen to mp3 of CSS version).
Obviously, using an unordered list in a
Now this is hardly ground-breaking research for the Standards evangelists reading this – but it’s further real-world evidence that using semantic mark-up that seperates content and presentation definitely enhances acessibility.