Re: content: url() is bad

>> how *would* this be more or less compatible with a screenreader?
> 
> content: url(1), url(2), url(3), "contents";
> 
> Where "contents" is the fallback text that is displayed if the URIs 
> fail  to be rendered.

That is the part that should be changed. Since people think that 
'content:url(img);' takes care of everything and in a way, that makes 
sense. The content could not "replaced" so the property "doesn't" apply.

I proposed in private e-mail that "contents" should last in the list and 
that "none" should be specified if one wants to have that effect.

According to what Ian told me, such an approach will be in the next WD. 
(He also posted it on this list as a reply to Dave Shea.)


-- 
  Anne van Kesteren
  <http://annevankesteren.nl/>

Received on Monday, 12 April 2004 12:37:24 UTC