Christian Heilmann wrote:
<snip>
>>@media aural {
>> a[href]:before { content: "link: " }
...
>>}
>
>
> Nice idea, and good in a theoretical sense, but in reality screen
> readers do say "link", so there is no real need for that.
</snip>...which they could do with an internal stylesheet, allowing the author to change it this to something else, should they desire, and the user to be able to decide which they prefer. It could also be used to add additional information to elements for which the assistive technologies do not have as good support for example:
q:before,
blockquote:before { content: "quote " }
q:after,
blockquote:after { content " end-quote" }>>2) Graphical replacement of text. > > > Is a "nice to have", but NEVER a "need to have".
...is the growing trend in the medium. Flash is nice to have, as are drop-down menus and hover effects on links. Regardless of whether or not a site needs it, designers are going to circumvent the web's inability to control fonts and text effects in a meaningful way. The presentational method is the most appropriate way, is it not?
>>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.
My error, the selector should have been a[href^="http://"]:after. That technique does not work in browsers that do not support padding on inline elements (such as IE 5/win), making the text unreadable. This technique is more appropriate because is does not rely on the implementation and interaction of multiple properties in order to work--it either does or does not.
--
Ryan Cannon Instructional Technology Web Design http://RyanCannon.com
______________________________________________________________________ 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/
