[thelist] DOM Help

Christian Heilmann lists at onlinetools.org
Fri Feb 4 15:56:47 CST 2005

>>>> Another point to be aware of is that display:block and display:none 
>>>> are
>>>> very easy and understandable, but also hide content from assistive
>>>> technology:
>>>> http://css-discuss.incutio.com/?page=ScreenreaderVisibility
>>> What would you suggest otherwise? I checked your code to see what you
>>> were using, but you also use this CSS property.
>> That is explained in the article above, the idea is to move the 
>> element off the screen via absolute positioning.
>> For my example of clickable headlines I used it out of sheer 
>> lazyness, in newer scripts however I  tend to move stuff off-left.
> Perhaps a silly question, but why would it not be appropriate to hide 
> the content from assistive technology? You are hiding it from one 
> browser, why not hide it from all browsers? As long as you have a way 
> for all browsers to bring the content back again it would seem to make 
> the most sense to have the same content and the same behavior for all 
> browsers.

The idea of hiding elements is normally to hide them from visual 
browsers, but still keep them in the document for text browsers and 
assistive technology. To my knowledge, please correct me if I am wrong, 
I am keen to learn, all screen readers don't allow for dynamic changes 
of  the document after it was loaded, which would render any show/hide 
solution useless for these visitors.
In any case, dynamically shown and hidden elements have their place, but 
we should always be aware that they do come with a lot of issues:

More information about the thelist mailing list