on 2004-11-26 09:49 Jukka K. Korpela wrote:
> But even when "hidden"
> with CSS, the URLs causes problems e.g. to people using speech browsers
> that use the HTML source as such, instead of reading screen content
> (it's particularly boring to listen to long URLs).
We all know by now, though, that most of the commonly used screen
readers obey display: none, much to the chagrin of the first generation
of image replacement techniques.
> In principle, a better approach would be to use CSS to generate text that
> will appear in print but is not present as normal content. But this is
> feasible only when you don't need to consider IE, which does not support
> the constructs needed (mainly generated content).
Curtis Clark http://www.csupomona.edu/~jcclark/
Web Coordinator, Cal Poly Pomona +1 909 979 6371
Professor, Biological Sciences +1 909 869 4062
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/