>
> 1) Media-specific style sheets. Aural stylesheets would be impossible
> without :before, :after and the content property. This is mostly a
> theoretical argument, as only Opera 8 supports aural stylesheets, and I
> haven't been able to test how well. But the code:
>
> @media aural {
> a[href]:before { content: "link: " }
> acronym[title]:before,
> abbr[title]:before { content: attr(title) " or "; speak:normal }
> acronym, abbr { speak: spell-out }
> }
Nice idea, and good in a theoretical sense, but in reality screen
readers do say "link", so there is no real need for that. IMHO these
things are the job of the assistive technology, not you as the
developer. In a lot of really large project even alternative text is
considered a drag, I really don't see this becoming common practise.
> Is essential for a meaningful use of the aural medium.
>
> 2) Graphical replacement of text.
Is a "nice to have", but NEVER a "need to have".
>
> 3) Non-structural, non-behavioral graphical enhancements
> I could write a DOM javascript to insert an image after every link with
> http in its href attribute, or I could use CSS. I contend that this is
> presentation, not behavior, and therefore use:
>
> a[href^="http://";] { content:url("external.png") }
How about using a background image and padding for that? As the image
is just of visual use it doesn't need to be an element.
--
Chris Heilmann
Blog: http://www.wait-till-i.com
Writing: http://icant.co.uk/
Binaries: http://www.onlinetools.org/
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
