<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SEO Web Design Blog &#187; Web Standards</title>
	<atom:link href="http://www.newshoemedia.com/blog/category/web-design/web-standards/feed" rel="self" type="application/rss+xml" />
	<link>http://www.newshoemedia.com/blog</link>
	<description>SEO and Search Engine Friendly Web Design</description>
	<lastBuildDate>Tue, 20 Oct 2009 19:52:29 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Be Specific: Using Semantic XHTML for Search Engines</title>
		<link>http://www.newshoemedia.com/blog/seo/be-specific-using-semantic-xhtml-for-search-engines</link>
		<comments>http://www.newshoemedia.com/blog/seo/be-specific-using-semantic-xhtml-for-search-engines#comments</comments>
		<pubDate>Fri, 30 Jan 2009 22:28:21 +0000</pubDate>
		<dc:creator>Claye Stokes</dc:creator>
				<category><![CDATA[SEO]]></category>
		<category><![CDATA[Tutorial]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Code]]></category>
		<category><![CDATA[semantics]]></category>
		<category><![CDATA[xhtml]]></category>

		<guid isPermaLink="false">http://www.newshoemedia.com/blog/?p=159</guid>
		<description><![CDATA[Using the &#60;acronym&#62;, &#60;abbr&#62;, and &#60;address&#62; tags to improve readability for disabled users, web crawlers, and search engines.
You want to make your website as informative as possible, right? For search engines, users &#8211; everybody. Help search engines, disabled (blind) users, and any users who may not understand the meaning of your acronym or abbreviation by [...]]]></description>
			<content:encoded><![CDATA[<p><em>Using the <code>&lt;acronym&gt;</code>, <code>&lt;abbr&gt;</code>, and <code>&lt;address&gt;</code> tags to improve readability for disabled users, web crawlers, and search engines.</em></p>
<p>You want to make your website as informative as possible, right? For search engines, users &#8211; everybody. Help search engines, disabled (blind) users, and any users who may not understand the meaning of your acronym or abbreviation by using semantic <abbr title="Extensible HyperText Markup Language">XHTML</abbr> tags like the <code>&lt;acronym&gt;</code>, <code>&lt;abbr&gt;</code>, and <code>&lt;address&gt;</code> tags in context. <span id="more-159"></span></p>
<p>If your website, for example, is about Medical Transcriptions, but you refer to them on the website only using the medical jargon <acronym title="Medical Transcriptions">MT</acronym>, search engines and users looking at small snippets of text may confuse the acronym &#8220;MT&#8221; for Media Temple (<acronym title="Media Temple">MT</acronym>), or the abbreviation for Montana (<abbr title="Montana">MT</abbr>), so use the <code>&lt;acronym&gt;</code> tag to specify what you are referring to. The more specific you can be, the more likely you are to rank for those relevant terms, and as a result, your users content to be more informative and useful. </p>
<p>To see it in action, hover your mouse over this: <abbr title="Extensible HyperText Markup Language">XHTML</abbr>. You&#8217;ll see a tool tip with the written-out version: E<strong>x</strong>tensible <strong>H</strong>yper<strong>T</strong>ext <strong>M</strong>arkup <strong>L</strong>anguage. If users or search engines don&#8217;t already know what the acronym stands for, then the <em>title</em> attribute (see below) will inform them, and text-to-speech engines will be able to see that the full term that the acronym represents as well. </p>
<p>Finally, using the <code>&lt;address&gt;</code> tag is getting increased attention lately, especially for local businesses and websites that users would search for with Google Local Search, Maps, YellowPages.com, Yelp.com, etc. The <code>&lt;address&gt;</code> tag helps to isolate the address from the rest of the copy on your website, making your website more relevant to local or geo targeted search queries, such as &#8220;san diego pizza&#8221; or &#8220;pizza 94023&#8243; (searching by zip code).</p>
<h2>Code Examples</h2>
<p>How to use the  <code>&lt;acronym&gt;</code> tag:</p>
<ol class="code">
<li><code>&lt;acronym title="National Aeronautics and Space Administration"&gt;NASA&lt;/acronym&gt;</code></li>
<li><code>&lt;acronym title="Search Engine Optimization"&gt;SEO&lt;/acronym&gt;</code></li>
<li><code>&lt;acronym title="Medical Transcription"&gt;MT&lt;/acronym&gt;</code></li>
</ol>
<p>How to use the  <code>&lt;abbr&gt;</code> tag:</p>
<ol class="code">
<li><code>&lt;abbr title="Utah"&gt;UT&lt;/abbr&gt;</code></li>
<li><code>&lt;abbr title="Corporation"&gt;Corp&lt;/abbr&gt;</code>.</li>
</ol>
<p>How to use the  <code>&lt;address&gt;</code> tag:</p>
<ol class="code">
<li><code>&lt;address&gt;</code></li>
<li><code class="indent2">Address:14 East Anywhere Drive&lt;br /&gt;</code></li>
<li><code class="indent2">City, &lt;abbr title="State"&gt;ST&lt;/state&gt; 55555</code></li>
<li><code>&lt;/acronym&gt;</code></li>
</ol>
<p>When it comes to distinguising between acronyms, initialisms, and abbreviations, the following guides are very useful. When it comes to implementing the <code>&lt;acronym&gt;</code> and <code>&lt;abbr&gt;</code> tags, the <acronym title="World Wide Web Consortium">W3C</acronym> appears to suggest that <code>&lt;acronym&gt;</code> should be used for acronyms and initialisms, and <code>&lt;abbr&gt;</code> is used for abbreviated and shortened words (Inc., Gov., etc.).</p>
<ul>
<li><a href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#text-abbr">The W3C guide for Acronyms and Abbreviations</a></li>
<li>Grammar Girl <a href="http://grammar.quickanddirtytips.com/acronyms-grammar.aspx">Abbreviations, Acronyms, and Initialisms</a></li>
<li>This article sorts out the confusion over the correct use of abbreviations and acronyms: <a href="http://juicystudio.com/article/abbreviations-acronyms.php">http://juicystudio.com/article/abbreviations-acronyms.php</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.newshoemedia.com/blog/seo/be-specific-using-semantic-xhtml-for-search-engines/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>I&#8217;m leaving IE6 in the dust</title>
		<link>http://www.newshoemedia.com/blog/web-design/im-leaving-ie6-in-the-dust</link>
		<comments>http://www.newshoemedia.com/blog/web-design/im-leaving-ie6-in-the-dust#comments</comments>
		<pubDate>Wed, 14 Jan 2009 19:42:38 +0000</pubDate>
		<dc:creator>Claye Stokes</dc:creator>
				<category><![CDATA[Resources]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[ie]]></category>
		<category><![CDATA[ie hacks]]></category>
		<category><![CDATA[ie6]]></category>

		<guid isPermaLink="false">http://www.newshoemedia.com/blog/?p=111</guid>
		<description><![CDATA[If you visit my site using IE6, you will see this big annoying badge right on top of my logo:
Why?
IE6 does not support web standards, meaning that not only does it do a bad job of displaying websites correctly,  it is the bane of every web designer who has to stoop to the level of [...]]]></description>
			<content:encoded><![CDATA[<p>If you visit my site using IE6, you will see this big annoying badge right on top of my logo:</p>
<h2><img class="aligncenter" title="IE6 does not support web standards" src="http://www.newshoemedia.com/images/ie6-badge.png" alt="" width="519" height="119" />Why?</h2>
<p>IE6 does not support web standards, meaning that not only does it do a bad job of displaying websites correctly,  it is the bane of every web designer who has to stoop to the level of implementing IE6 hacks to fix its bugs.</p>
<p>I can&#8217;t stop making websites that support IE6 for <strong>my </strong><strong>clients</strong>, because their websites have to work for everyone that comes along, regardless of their browser.</p>
<p>My website, on the other hand, can (hopefully) educate my visitors who are less experienced on the web, and help them to upgrade to a better, faster, more user-friendly, and free browser like <a href="http://www.google.com/chrome">Google&#8217;s Chrome</a> (if you&#8217;re still using IE6, do yourself a huge favor and just click on that link right now), <a href="http://www.opera.com/">Opera</a>, or <a href="http://www.mozilla.com/en-US/firefox/">Firefox</a>. I mention them in that order because if you&#8217;re still on IE6, you won&#8217;t understand the benefits or need the addons of Firefox, and Chrome is the fastest, most lightweight browser and probably the best solution for an older/antiquated computer.</p>
<p>If you look closely, you&#8217;ll notice that I&#8217;m still using a few IE hacks like the <a href="http://www.twinhelix.com/css/iepngfix/">IE png fix</a> to give transparent PNG support, as well as a hack to get my navigation menu to work in IE6. I don&#8217;t want to leave IE6 users completely hanging, but they will have to endure the big ugly badge in my header.</p>
<p>If you are interested in doing the same thing for your website, feel free to use my code and image &#8211; I&#8217;ll be happy if you do. Both were inspired by <a href="http://elliotjaystocks.com/blog/">Elliot Jay Stocks</a> (to give credit where credit is due). You will also probably want to joing the <a href="http://iedeathmarch.org/">IE Death March</a> &#8211; an initiative to end IE6 support by March of this year. I mean, IE6 is <em>older than the Ipod</em> &#8211; it&#8217;s time to move on.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.newshoemedia.com/blog/web-design/im-leaving-ie6-in-the-dust/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
