<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for The Blog of Clint Andrew Hall</title>
	<atom:link href="http://www.clintandrewhall.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clintandrewhall.com/blog</link>
	<description>Welcome to my corner of the web, where I post my ponderings, pictures and pontifications.</description>
	<lastBuildDate>Fri, 23 Oct 2009 00:56:38 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Contact Form Experiment by Patrick Denny</title>
		<link>http://www.clintandrewhall.com/blog/2009/10/contact-form-experiment/comment-page-1/#comment-6032</link>
		<dc:creator>Patrick Denny</dc:creator>
		<pubDate>Fri, 23 Oct 2009 00:56:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.clintandrewhall.com/blog/?p=95#comment-6032</guid>
		<description>Hi there,
I&#039;m the original site owner. I appreciate the work you did on this, and will probably recode my form to include a variation of your solution on my site (I&#039;ll leave credit and a pointer back to this post in the HTML source when I&#039;m done).

However, I feel I must explain my initial design decisions, at least partially.

First off, yes. I did justify my decision to hide the  labels behind a &quot;know your target audience&quot; excuse, but - as your facebook friend mentioned - I knew my site visitors would be individuals looking for a web developer/designer, and expect to see graphic heavy content (it is a portfolio site). It was a decision I made only due to the fact that many other fairly prominent designers and developers had decided to use similar graphical text replacement techniques despite this short coming. 

That said, I used the screen media type so that mobile browsers (other than iPhone) got straight up html, with text labels intact, and the labels were hidden in a manner that made them accessible to screen readers. Also, while the page linked to by Smashing didn&#039;t have any other contact info, the form was originally for my contact page. That page does also list several other ways of contacting me - email, phone, snail mail, twitter - so that even if someone couldn&#039;t use the form for what ever reason, they would still have other options available to them. You see, accessibility isn&#039;t always about limiting yourself (or jumping through crazy hoops) so that everyone has the exact same access to an interface. Sometimes it&#039;s about offering a reasonable (if somewhat clunkier) alternative when non-accessible techniques are utilized.

However, I admit that the image is large and slow to load. I&#039;m still trying to find a way of compressing it that keeps its fidelity and alpha channel intact. I also think that I could have added title attributes to the form elements to allow someone a method of deducing the use of each field without the graphic available.

Again,
Thanks. I like the solution you came up with.</description>
		<content:encoded><![CDATA[<p>Hi there,<br />
I&#8217;m the original site owner. I appreciate the work you did on this, and will probably recode my form to include a variation of your solution on my site (I&#8217;ll leave credit and a pointer back to this post in the HTML source when I&#8217;m done).</p>
<p>However, I feel I must explain my initial design decisions, at least partially.</p>
<p>First off, yes. I did justify my decision to hide the  labels behind a &#8220;know your target audience&#8221; excuse, but &#8211; as your facebook friend mentioned &#8211; I knew my site visitors would be individuals looking for a web developer/designer, and expect to see graphic heavy content (it is a portfolio site). It was a decision I made only due to the fact that many other fairly prominent designers and developers had decided to use similar graphical text replacement techniques despite this short coming. </p>
<p>That said, I used the screen media type so that mobile browsers (other than iPhone) got straight up html, with text labels intact, and the labels were hidden in a manner that made them accessible to screen readers. Also, while the page linked to by Smashing didn&#8217;t have any other contact info, the form was originally for my contact page. That page does also list several other ways of contacting me &#8211; email, phone, snail mail, twitter &#8211; so that even if someone couldn&#8217;t use the form for what ever reason, they would still have other options available to them. You see, accessibility isn&#8217;t always about limiting yourself (or jumping through crazy hoops) so that everyone has the exact same access to an interface. Sometimes it&#8217;s about offering a reasonable (if somewhat clunkier) alternative when non-accessible techniques are utilized.</p>
<p>However, I admit that the image is large and slow to load. I&#8217;m still trying to find a way of compressing it that keeps its fidelity and alpha channel intact. I also think that I could have added title attributes to the form elements to allow someone a method of deducing the use of each field without the graphic available.</p>
<p>Again,<br />
Thanks. I like the solution you came up with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Contact Form Experiment by Mike</title>
		<link>http://www.clintandrewhall.com/blog/2009/10/contact-form-experiment/comment-page-1/#comment-6031</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 22 Oct 2009 21:49:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.clintandrewhall.com/blog/?p=95#comment-6031</guid>
		<description>Well presented Clint. I strongly agree with the semantic and accessible approach.  At first I did it because it was right; now I  do it because it performs better, its easier to read, easier to maintain, and easier to style.</description>
		<content:encoded><![CDATA[<p>Well presented Clint. I strongly agree with the semantic and accessible approach.  At first I did it because it was right; now I  do it because it performs better, its easier to read, easier to maintain, and easier to style.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Run Safari 3 and Safari 4 beta on the same Mac by Clint</title>
		<link>http://www.clintandrewhall.com/blog/2009/03/run-safari-3-and-safari-4-beta-on-the-same-mac/comment-page-1/#comment-5240</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Tue, 14 Jul 2009 20:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.clintandrewhall.com/blog/?p=63#comment-5240</guid>
		<description>Phil,

I don&#039;t think so... but YMMV.</description>
		<content:encoded><![CDATA[<p>Phil,</p>
<p>I don&#8217;t think so&#8230; but YMMV.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Run Safari 3 and Safari 4 beta on the same Mac by Phil</title>
		<link>http://www.clintandrewhall.com/blog/2009/03/run-safari-3-and-safari-4-beta-on-the-same-mac/comment-page-1/#comment-5228</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Sun, 12 Jul 2009 20:17:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.clintandrewhall.com/blog/?p=63#comment-5228</guid>
		<description>Will your standalone work on a G4 running Tiger or is it only for Intel and /or Leopard?</description>
		<content:encoded><![CDATA[<p>Will your standalone work on a G4 running Tiger or is it only for Intel and /or Leopard?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PSD2HTML: Terrible Pricing for Web Development by XHTML Candy</title>
		<link>http://www.clintandrewhall.com/blog/2008/01/a-terrible-pricing-model-for-web-development/comment-page-1/#comment-4277</link>
		<dc:creator>XHTML Candy</dc:creator>
		<pubDate>Sat, 25 Apr 2009 16:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.clintandrewhall.com/blog/2008/01/insane-stupid-pricing-model-for-web-development/#comment-4277</guid>
		<description>We here at xhtml candy totally agree to that. That is why we don&#039;t add additional price for anything that is must for a website to work properly. We provide everything within total cost. We never charge extra for cross browser compatibility, commented xhtml and css, load speed optimization etc.</description>
		<content:encoded><![CDATA[<p>We here at xhtml candy totally agree to that. That is why we don&#8217;t add additional price for anything that is must for a website to work properly. We provide everything within total cost. We never charge extra for cross browser compatibility, commented xhtml and css, load speed optimization etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on An Open Letter to a Car Thief by matt sosa</title>
		<link>http://www.clintandrewhall.com/blog/2008/01/an-open-letter-to-a-car-thief/comment-page-1/#comment-3581</link>
		<dc:creator>matt sosa</dc:creator>
		<pubDate>Sun, 05 Apr 2009 05:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.clintandrewhall.com/blog/2008/01/an-open-letter-to-a-car-thief/#comment-3581</guid>
		<description>We got broken in back in October-- same story:  can these assholes even use what they took?  Like you said:  wait till I&#039;m home, knock on the door and save us both the hassle.</description>
		<content:encoded><![CDATA[<p>We got broken in back in October&#8211; same story:  can these assholes even use what they took?  Like you said:  wait till I&#8217;m home, knock on the door and save us both the hassle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating Elements in JavaScript, (any good?) by Jim</title>
		<link>http://www.clintandrewhall.com/blog/2009/03/creating-elements-in-javascript-any-good/comment-page-1/#comment-3502</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Thu, 26 Mar 2009 01:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.clintandrewhall.com/blog/?p=76#comment-3502</guid>
		<description>I like your post. However, I don&#039;t see why you wouldn&#039;t consider using a js framework...after all if you were you wouldn&#039;t need to worry about the best way to do this since it would take care of it for you.

Cheers,
jim</description>
		<content:encoded><![CDATA[<p>I like your post. However, I don&#8217;t see why you wouldn&#8217;t consider using a js framework&#8230;after all if you were you wouldn&#8217;t need to worry about the best way to do this since it would take care of it for you.</p>
<p>Cheers,<br />
jim</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Run Safari 3 and Safari 4 beta on the same Mac by Harry</title>
		<link>http://www.clintandrewhall.com/blog/2009/03/run-safari-3-and-safari-4-beta-on-the-same-mac/comment-page-1/#comment-3496</link>
		<dc:creator>Harry</dc:creator>
		<pubDate>Tue, 24 Mar 2009 22:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.clintandrewhall.com/blog/?p=63#comment-3496</guid>
		<description>The standalone version works. Thanks for doing that. To make it easier, it would be great if you named it Safari3.app instead of Safari.app. Saves a step.</description>
		<content:encoded><![CDATA[<p>The standalone version works. Thanks for doing that. To make it easier, it would be great if you named it Safari3.app instead of Safari.app. Saves a step.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Run Safari 3 and Safari 4 beta on the same Mac by Harry</title>
		<link>http://www.clintandrewhall.com/blog/2009/03/run-safari-3-and-safari-4-beta-on-the-same-mac/comment-page-1/#comment-3495</link>
		<dc:creator>Harry</dc:creator>
		<pubDate>Tue, 24 Mar 2009 22:18:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.clintandrewhall.com/blog/?p=63#comment-3495</guid>
		<description>Didn&#039;t work for me.

1. Have Safari 3 running on Leopard.
2. Start from your instructions.
3. Click Safari icon in dock to start.
4. Icon disappears; Safari doesn&#039;t start.

I had to re-install Safari.</description>
		<content:encoded><![CDATA[<p>Didn&#8217;t work for me.</p>
<p>1. Have Safari 3 running on Leopard.<br />
2. Start from your instructions.<br />
3. Click Safari icon in dock to start.<br />
4. Icon disappears; Safari doesn&#8217;t start.</p>
<p>I had to re-install Safari.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Run Safari 3 and Safari 4 beta on the same Mac by Clint</title>
		<link>http://www.clintandrewhall.com/blog/2009/03/run-safari-3-and-safari-4-beta-on-the-same-mac/comment-page-1/#comment-3494</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Tue, 24 Mar 2009 22:07:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.clintandrewhall.com/blog/?p=63#comment-3494</guid>
		<description>Not sure what step I missed writing down... see the updated post; I&#039;ve posted an archive containing the Safari 3 app I created.</description>
		<content:encoded><![CDATA[<p>Not sure what step I missed writing down&#8230; see the updated post; I&#8217;ve posted an archive containing the Safari 3 app I created.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
