<?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>Blog - Michael Herring Design &#187; Web</title>
	<atom:link href="http://michaelherringdesign.com/blog/category/web/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelherringdesign.com/blog</link>
	<description>Hectic Art</description>
	<lastBuildDate>Fri, 12 Mar 2010 02:34:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Hurting Web Accessibility: SEO Alt Tag Optimizer &amp; Font Resizer Tool</title>
		<link>http://michaelherringdesign.com/blog/2008/05/02/hurting-web-accessibility-seo-alt-tag-optimizer-font-resizer-tool/</link>
		<comments>http://michaelherringdesign.com/blog/2008/05/02/hurting-web-accessibility-seo-alt-tag-optimizer-font-resizer-tool/#comments</comments>
		<pubDate>Sat, 03 May 2008 02:13:14 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[Web]]></category>
		<category><![CDATA[Web Accessibility]]></category>

		<guid isPermaLink="false">http://michaelherringdesign.com/blog/?p=215</guid>
		<description><![CDATA[(Sigh)
I guess I&#8217;ll add a web development post to this mostly art-related blog.
Today, I ran across an excellent list of 100 killer web accessibility resources. Most of these resources are quite good for reference and learning material.
However, I take offense to the SEO Alt Tag (sic) Optimizer &#038; Font Resizer Tool link. I will not [...]]]></description>
			<content:encoded><![CDATA[<p>(Sigh)<br />
I guess I&#8217;ll add a web development post to this mostly art-related blog.</p>
<p>Today, I ran across an excellent list of <a href="http://whdb.com/2008/100-killer-web-accessibility-resources-blogs-forums-and-tutorials/">100 killer web accessibility resources</a>. Most of these resources are quite good for reference and learning material.</p>
<p>However, I take offense to the <strong><abbr title="Search Engine Optimization">SEO</abbr> Alt Tag (sic) Optimizer &#038; Font Resizer Tool</strong> link. I will not link to it here, but I will provide the <abbr title="Uniform Resource Locator">URL</abbr> for those interested:</p>
<p>http://www.indiana-loans.co.uk/wordpress-plugin-seo-alt-tag-optimzer-font-resizer-tool/</p>
<h3>Objections</h3>
<p>As an accessibility-aware web professional, I have some <strong>strong objections</strong> to this plugin:</p>
<p>Alt attributes should <strong>absolutely not</strong> be used solely for <abbr>SEO</abbr> purposes. They should be used to convey the purpose of the image or the function of the link surrounding the image. Please see <a href="http://www.webaim.org/techniques/alttext/">Appropriate Use of Alternative Text</a> for an excellent explanation of the proper usage of alt text.</p>
<p>Alt attribute usage seems quite simple at first (with the rule that every image must have an alt attribute), but text within the alt attribute and indeed, even the need for text within the attribute requires careful thought.</p>
<p>The <abbr>SEO</abbr> Alt Tag Optimizer &#038; Font Resizer Tool abuses alt text for the wrong intentions of possibly placing your site higher in search engine rankings by using inappropriate alt text.</p>
<h3>Accessibility Attribute Abuse</h3>
<p>Even though screen-reader users don&#8216;t need to use a font-size switcher, they do rely heavily on proper alt text for images. Consider this <abbr title="Hypertext Markup Language">HTML</abbr> snippet from the plugin creator&#8217;s page which uses the plugin:</p>
<p><code>[snip]<br />
&lt;img src="http://www.indiana-loans.co.uk/.../decrease-font-size.jpg" alt="<strong>Decrease font size for Post - SEO Alt Tag Optimizer &#038; Font Resizer Tool (WordPress plugin) - Uncategorised Topics - Indiana Loans Ltd</strong>" onclick="fnChangeFontSize(&#8216;body&#8216;,-1);" border="0" width="18" height="14" title="To reduce font size, please enable JavaScript and Trust this Site" <strong>longdesc="http://www.indiana-loans.co.uk/wordpress-plugin-font-resizer-tool-help-page/"</strong> /&gt;<br />
[snip]</code></p>
<p>There are 2 major problems with the above code (and some minor problems I won&#8217;t get into):</p>
<ol>
<li>The alt value of &#8220;<strong>Decrease font size for Post &#8211; SEO Alt Tag Optimizer &#038; Font Resizer Tool (WordPress plugin) &#8211; Uncategorised Topics &#8211; Indiana Loans Ltd</strong>&#8221; does not provide any information that is useful for a screen-reader user, which is what the alt attribute was created for. Instead, there is excessive marketing language and the useless information about reducing font size (remember, screen-reader software has no concept of font sizing).</li>
<li>There is a misuse of the <strong>longdesc</strong> attribute to point to a help page for the font-resizer plugin. The longdesc is meant to provide an equivalent to a very complicated image like a chart or graph. It is not meant to provide help text for an application or plugin.</li>
</ol>
<h3><abbr>URL</abbr> Problems</h3>
<p>Also, being nit-picky as usual, there are some problems within the <abbr>URL</abbr> of the plugin&#8217;s creator:</p>
<p>http://www.<strong>indiana-loans</strong>.co.uk/wordpress-plugin-seo-<strong>alt-tag</strong>-<strong>optimzer</strong>-font-resizer-tool/</p>
<ul>
<li>Who would trust a plugin from a url that contains &#8216;<strong>indiana-loans</strong>&#8217;? That&#8217;s pure keyword-stuffing, and not anything that would give any indication of a developer&#8217;s website. It appears to be a loan website.</li>
<li>Usage of the term &#8216;<strong>alt-tag</strong>&#8217; is seriously frowned upon by accessibility experts. It&#8217;s an <strong>alt attribute</strong>!</li>
<li>&#8216;<strong>optimzer</strong>&#8217; &#8211; misspellings (when not intentional) probably do not help with search engine optimization.</li>
</ul>
<p>Okay, I&#8217;m done. I ran across this link this afternoon and it just kinda pissed me off. I hate seeing Web accessibility techniques being abused for <abbr>SEO</abbr> purposes.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelherringdesign.com/blog/2008/05/02/hurting-web-accessibility-seo-alt-tag-optimizer-font-resizer-tool/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Bad Balance saga pt. 5 or so</title>
		<link>http://michaelherringdesign.com/blog/2003/09/27/the-bad-balance-saga-pt-5-or-so/</link>
		<comments>http://michaelherringdesign.com/blog/2003/09/27/the-bad-balance-saga-pt-5-or-so/#comments</comments>
		<pubDate>Sat, 27 Sep 2003 17:19:08 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://michaelherringdesign.com/blog/?p=281</guid>
		<description><![CDATA[Whut&#8212;I&#8217;ve just transferred the Bad Balance site to php, and it really wasn&#8217;t that difficult. As I was only using asp to do sequential image pages and includes. After 5 days, I&#8217;ve finally had enough time to fix it. And this is great and also wonderful.
]]></description>
			<content:encoded><![CDATA[<p>Whut&#8212;I&#8217;ve just transferred the <a href="http://www.michaelherringdesign.com/badbalance/">Bad Balance</a> site to php, and it really wasn&#8217;t that difficult. As I was only using asp to do sequential image pages and includes. After 5 days, I&#8217;ve finally had enough time to fix it. And this is great and also wonderful.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelherringdesign.com/blog/2003/09/27/the-bad-balance-saga-pt-5-or-so/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Transition Disaster</title>
		<link>http://michaelherringdesign.com/blog/2003/09/25/transition-disaster/</link>
		<comments>http://michaelherringdesign.com/blog/2003/09/25/transition-disaster/#comments</comments>
		<pubDate>Thu, 25 Sep 2003 18:54:59 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://michaelherringdesign.com/blog/?p=285</guid>
		<description><![CDATA[I&#8217;m in the middle of a bungled-up transition from a Windows host to an Apache host. I thought using Chilisoft ASP would be fine, but nobody can tell me how to correctly path my virtual includes, and every asp page has an ugly URL that comes with it.
I&#8217;d call this a learning experience.
Now I have [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m in the middle of a bungled-up transition from a Windows host to an Apache host. I thought using Chilisoft ASP would be fine, but nobody can tell me how to correctly path my virtual includes, and every asp page has an ugly URL that comes with it.</p>
<p>I&#8217;d call this a learning experience.</p>
<p>Now I have to recode 3 sites into php. The asp and php is not doing anything too fancy. I&#8217;m just using them for includes and if-else statements, etc. But still. And dang.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelherringdesign.com/blog/2003/09/25/transition-disaster/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Domain Names</title>
		<link>http://michaelherringdesign.com/blog/2002/10/12/domain-names/</link>
		<comments>http://michaelherringdesign.com/blog/2002/10/12/domain-names/#comments</comments>
		<pubDate>Sat, 12 Oct 2002 18:24:01 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://michaelherringdesign.com/blog/2002/10/12/domain-names/</guid>
		<description><![CDATA[I just remembered that if I put links on here and then click them, there&#8217;s the possibility of the webmaster of Hy-Vee, for example, to get at this site through the referer logs. Yeah, right.
I just learned that according to dictionary.com, &#8216;referer&#8217; is &#8220;a misspelling of &#8216;referrer&#8217; which somehow made it into the HTTP standard.&#8221;
Mmm-hmm, [...]]]></description>
			<content:encoded><![CDATA[<p>I just remembered that if I put links on here and then click them, there&#8217;s the possibility of the webmaster of <a href="http://www.hy-vee.com/">Hy-Vee</a>, for example, to get at this site through the referer logs. Yeah, right.</p>
<p>I just learned that according to dictionary.com, &#8216;referer&#8217; is &#8220;a misspelling of &#8216;referrer&#8217; which somehow made it into the HTTP standard.&#8221;</p>
<p>Mmm-hmm, I forgot who&#8217;s been doing this already, but there are many good domain names that are not yet reserved:</p>
<ul>
<li>misterawesome.com</li>
<li>ultra-awesome.com</li>
<li>super-mega-ultra.com</li>
<li>crazyill.com</li>
<li>and so forth</li>
</ul>
<p>Maybe because those domain names are so nice people think they&#8217;re weak. Or maybe everyone&#8217;s sick of domain names by now. At least <a href="http://www.stupidfresh.com/fresh/">Stupid Fresh</a> and <a href="http://www.crazyfresh.com/">Crazy Fresh</a> are upon in it. </p>
]]></content:encoded>
			<wfw:commentRss>http://michaelherringdesign.com/blog/2002/10/12/domain-names/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nobody Sees This</title>
		<link>http://michaelherringdesign.com/blog/2001/09/08/nobody-sees-this/</link>
		<comments>http://michaelherringdesign.com/blog/2001/09/08/nobody-sees-this/#comments</comments>
		<pubDate>Sun, 09 Sep 2001 00:33:11 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[Life]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Work]]></category>

		<guid isPermaLink="false">http://michaelherringdesign.com/blog/?p=266</guid>
		<description><![CDATA[I&#8217;ve been recently realizing that nobody sees this blog, so it is doing the job I hoped it would do. And that is to serve as a journal that has the possibility of being seen. For you see, the last time I wrote in any kind of a journal, it was hell to read through [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been recently realizing that nobody sees this blog, so it is doing the job I hoped it would do. And that is to serve as a journal that has the <em>possibility</em> of being seen. For you see, the last time I wrote in any kind of a journal, it was hell to read through because I was writing as if it would never be seen by anyone. And for me, that creates shitty writing.</p>
<p>And my spider seems to have died after sucking all the blood out of some huge insect. Maybe the blood was poisoned or the spider ate too damn much.</p>
<p>My internship just turned into a full time Webmaster position. So now I am an entry-level webmaster. Shit. Who ever heard of an <em>entry level</em> webmaster? This job is doomed.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelherringdesign.com/blog/2001/09/08/nobody-sees-this/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
