Re: content: url() is bad

> how *would* this be more or less compatible with a screenreader?

Isn't this addressed by CSS3 generated content <URL:  
http://www.w3.org/TR/css3-content/#inserting3 >:

content: url(1), url(2), url(3), "contents";

Where "contents" is the fallback text that is displayed if the URIs fail  
to be rendered.

c


-- 
[Quote]
I was the shadow of the waxwing slain
By the false azure in the windowpane;
~~~ John Francis Shade