I think the question is justified. It's the same as with the noscript tag. Depending on the javascript support, you'll see EITHER the contents of the script tag OR the contents of the noscript tag. Imagine you've got a highly interactive ajax application with drag and drop and everything else. I would like to place this "multimedia" (where multimedia doesn't necessary mean audio/video) content into a <view> tag and a more accessible version into a <noview> tag.

So it's not only about hiding extra accessibilty information from the screen, but also about hiding interactvie/... information from the screenreader/...

Zitat von Nicholas Shanks <[EMAIL PROTECTED]>:

Paul is right, you can just use:

@media (screen, print, handheld) { .foo { display: none; } }

Since no screenreader i know of supports aural media you can't yet do
it the other way around (default to none and show for aural)



On 17 Mar 2008, at 2:08 am, Nicholas C. Zakas wrote:

I know the topic has come up a few times, but I'm still wondering if HTML 5 should provide some sort of logic around content that should not be displayed by browsers but should be read by screen readers. Perhaps a "noview" boolean attribute on each element could be used to tell UAs not to render the content but to report it to screen readers? Or maybe a <noview/> element could be used to surround content that shouldn't be displayed but should be accessible to screen readers?

Any thoughts?

-Nicholas

Looking for last minute shopping deals? Find them fast with Yahoo!  Search.

? Nicholas Shanks.



Reply via email to