<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:cc="http://web.resource.org/cc/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">

			<channel>
			<title>Building Blocks - Usability</title>
			<link>http://www.ajaxcf.com/blog/index.cfm</link>
			<description>tips for constructing next generation AJAX &amp; ColdFusion applications</description>
			<language>en-us</language>
			<pubDate>Thu, 09 Sep 2010 03:20:13 -0000</pubDate>
			<lastBuildDate>Wed, 13 Dec 2006 17:46:00 -0000</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>joe@ajaxcf.com</managingEditor>
			<webMaster>joe@ajaxcf.com</webMaster>
			<itunes:subtitle></itunes:subtitle>
			<itunes:summary></itunes:summary>
			<itunes:category text="Technology" />
			<itunes:category text="Technology">
				<itunes:category text="Podcasting" />
			</itunes:category>
			<itunes:category text="Technology">
				<itunes:category text="Tech News" />
			</itunes:category>
			<itunes:keywords></itunes:keywords>
			<itunes:author></itunes:author>
			<itunes:owner>
				<itunes:email>joe@ajaxcf.com</itunes:email>
				<itunes:name></itunes:name>
			</itunes:owner>
			
			<itunes:explicit>no</itunes:explicit>
			
			
			
			
			
			<item>
				<title>Why Do Developers Hate The &amp;lt;label&amp;gt; Tag?</title>
				<link>http://www.ajaxcf.com/blog/index.cfm/2006/12/13/Why-Do-Developers-Hate-The-ltlabelgt-Tag</link>
				<description>
				
				One of the most common usability faux pas I find all over the internet is the lack of developers linking up radio buttons with their labels.  Why should we be forced to click a tiny little circle when we should be able to click the actual text for that choice?

It&apos;s built into the HTML spec so why don&apos;t developers use it?  Even some of the biggest sites on the web are guilty of this one.  I just don&apos;t get it.. it&apos;s not exactly rocket science. 

Just give an ID to your radio button, like so:

&lt;code&gt;
&lt;input type=&quot;radio&quot; name=&quot;whatever&quot; id=&quot;selection1&quot; /&gt;
&lt;/code&gt;

then wrap the text that goes with that radio button in a label tag, as such:

&lt;code&gt;
&lt;label for=&quot;selection1&quot;&gt;selection 1&lt;/label&gt;
&lt;/code&gt;

Here&apos;s a full example with a few selections to choose from.. notice how you can just click the text to select the choice you&apos;d like:

&lt;input type=&quot;radio&quot; name=&quot;whatever&quot; id=&quot;selection1&quot; /&gt;
&lt;label for=&quot;selection1&quot;&gt;selection 1&lt;/label&gt;&lt;br /&gt;
&lt;input type=&quot;radio&quot; name=&quot;whatever&quot; id=&quot;selection2&quot; /&gt;
&lt;label for=&quot;selection2&quot;&gt;selection 2&lt;/label&gt;&lt;br /&gt;
&lt;input type=&quot;radio&quot; name=&quot;whatever&quot; id=&quot;selection3&quot; /&gt;
&lt;label for=&quot;selection3&quot;&gt;selection 3&lt;/label&gt;&lt;br /&gt;

The full code for that was:
&lt;code&gt;
&lt;input type=&quot;radio&quot; name=&quot;whatever&quot; id=&quot;selection1&quot; /&gt; &lt;label for=&quot;selection1&quot;&gt;selection 1&lt;/label&gt;&lt;br /&gt;
&lt;input type=&quot;radio&quot; name=&quot;whatever&quot; id=&quot;selection2&quot; /&gt; &lt;label for=&quot;selection2&quot;&gt;selection 2&lt;/label&gt;&lt;br /&gt;
&lt;input type=&quot;radio&quot; name=&quot;whatever&quot; id=&quot;selection3&quot; /&gt; &lt;label for=&quot;selection3&quot;&gt;selection 3&lt;/label&gt;&lt;br /&gt;
&lt;/code&gt;

With all of the attention being given to usability in this Web 2.0 world, let&apos;s make sure we&apos;ve got 1.0 covered first.
				
				</description>
						
				
				<category>Usability</category>				
				
				<pubDate>Wed, 13 Dec 2006 17:46:00 -0000</pubDate>
				<guid>http://www.ajaxcf.com/blog/index.cfm/2006/12/13/Why-Do-Developers-Hate-The-ltlabelgt-Tag</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>New Method: Transparent Messages</title>
				<link>http://www.ajaxcf.com/blog/index.cfm/2006/9/25/New-Method-Transparent-Messages</link>
				<description>
				
				&lt;img src=&quot;http://img65.imageshack.us/img65/8039/transmsgsig3.gif&quot; align=&quot;right&quot; border=&quot;0&quot; hspace=&quot;10&quot; /&gt;

Aza Raskin, over at &lt;a href=&quot;http://www.humanized.com&quot;&gt;Humanized&lt;/a&gt;, has come up with some code as a less-obtrusive alternative to Javascript alert boxes.

Javascript alerts are not the most elegant solution as they force the browser to stop in it&apos;s tracks until the user&apos;s clicks OK.  This can sometimes mislead a person into thinking the browser has crashed if the alert loses focus.

&lt;a href=&quot;http://www.humanized.com/weblog/2006/09/11/monolog_boxes_and_transparent_messages/#comments&quot;&gt;Transparent Messages&lt;/a&gt; were originally conceived by &lt;a href=&quot;http://www.jefraskin.com/&quot;&gt;Jef Raskin&lt;/a&gt;, one of the original designers of the Macintosh OS, as part of &lt;a href=&quot;http://rchi.raskincenter.org/aboutrchi/index.php&quot;&gt;Archy&lt;/a&gt;.  Archy is a project which aims to create a more &amp;quot;humane&amp;quot; interface betweem humans and computers.  

You can &lt;a href=&quot;http://www.humanized.com/js/TransparentMessage.js&quot;&gt;download the Javascript code here&lt;/a&gt;.
				
				</description>
						
				
				<category>Usability</category>				
				
				<pubDate>Mon, 25 Sep 2006 15:50:00 -0000</pubDate>
				<guid>http://www.ajaxcf.com/blog/index.cfm/2006/9/25/New-Method-Transparent-Messages</guid>
				
				
			</item>
			
		 	
			</channel></rss>