> So. Use <abbr>? Or, use <code>? >From what I could tell, your content looks like sample code, and only needs a code element. However, in case I am missing something (quite common for me), here is an overall approach...
STEP 1 The first aim is to ignore devices and mark up content based on its meaning. This means using the most appropriate element for the purpose. If the content is a code sample, then it should be marked up with the <code> element. If it is an abbreviation of some sort then it should be marked up with the appropriate abbreviation element [1]. Abbreviation: <abbr title="association">assoc.</abbr> Initialism: <abbr title="Cascading Style Sheets">CSS</abbr> Acronym: <acronym title="Radio Detecting And Ranging">radar</acronym> STEP 2 Once you have decided the basic markup, you can then deal with devices and how they interpret markup. If they do not interpret the markup as intended you can choose to apply work-arounds if needed. For example, as mentioned by Pat, Internet Explorer 5 and 6 for Windows do not support the <abbr> element. Some authors choose to wrap a span inside the element so that their styles will be applied in these browsers [2]. Another example of poor device support is that many screen readers do not support the title attribute [3], so the titles within abbreviations and acronyms are often ignored by screen readers. Some authors use a workaround when writing initialisms. So, "CSS" could be written as "C.S.S." to make sure that the content is not read out as a single, unintelligible word. Not sure that helps... Russ [1] http://www.maxdesign.com.au/presentation/abbreviations/ [2] http://www.sovavsiti.cz/css/abbr.html [3] http://www.sf.id.au/ozewai/ ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
