<?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>Watson Web Design &#187; Blog</title>
	<atom:link href="http://www.bryanwatson.ca/category/blog/feed" rel="self" type="application/rss+xml" />
	<link>http://www.bryanwatson.ca</link>
	<description>Winnipeg Web Design &#38; Development</description>
	<lastBuildDate>Mon, 14 Feb 2011 22:36:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
		<item>
		<title>Clickable Checkbox Labels</title>
		<link>http://www.bryanwatson.ca/blog/clickable-checkbox-labels</link>
		<comments>http://www.bryanwatson.ca/blog/clickable-checkbox-labels#comments</comments>
		<pubDate>Sun, 19 Jul 2009 00:20:21 +0000</pubDate>
		<dc:creator>Bryan Watson</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://www.bryanwatson.ca/?p=496</guid>
		<description><![CDATA[View final code While designing a form for my client, I came across the need to render clickable text beside checkboxes for better usability. I had a difficult time finding an article that did not use Javascript in anyways. Then in my search, I came across the most obvious answer that lying right under my [...]]]></description>
			<content:encoded><![CDATA[<style type="text/css"><!--
 .checkbox input { cursor:pointer;  }
 .checkbox label:hover { cursor:pointer; color:#ffffcc; }
 --></style>
<p><a href="#final">View final code</a></p>
<p>While designing a form for my client, I came across the need to <strong>render clickable text beside checkboxes</strong> for better usability. I had a difficult time finding an article that did not use Javascript in anyways.</p>
<p>Then in my search, I came across the most obvious answer that lying right under my nose the whole time.</p>
<p><a href="http://www.w3schools.com/tags/tag_label.asp" target="_blank">The Label Tag, and the &#8216;for&#8217; attribute.</a></p>
<p>Most designers will start with the following:</p>
<pre class="brush: xml; title: ; notranslate">
&lt;fieldset&gt;
	&lt;legend&gt;Your dog's favorite foods:&lt;/legend&gt;

	&lt;input type=&quot;checkbox&quot; value=&quot;kibble&quot; /&gt;
	&lt;label&gt;Kibble&lt;/label&gt;

	&lt;input type=&quot;checkbox&quot; value=&quot;chow&quot; /&gt;
	&lt;label&gt;Chow&lt;/label&gt;

	&lt;input type=&quot;checkbox&quot; value=&quot;steak&quot; /&gt;
	&lt;label&gt;Steak&lt;/label&gt;
&lt;/fieldset&gt;
</pre>
<p>Which renders:</p>
<blockquote>
<fieldset>
<legend>Your dog&#8217;s favorite foods:</legend>
<input type="checkbox" value="kibble" /> <label>Kibble</label></p>
<input type="checkbox" value="chow" /> <label>Chow</label></p>
<input type="checkbox" value="steak" /> <label>Steak</label><br />
</fieldset>
</blockquote>
<div class="clear"></div>
<p>As you can see, you can click the checkboxes, but the text only serves as well&#8230; a label, and is not useful as an interface.</p>
<p><strong>Using the &#8216;for&#8217; and &#8216;id&#8217; attributes respectively, we can achieve &#8216;clickable&#8217; checkbox text.</strong></p>
<p>Now, we add the &#8216;id&#8217; attributes to the inputs, and the &#8216;for&#8217; attributes to the labels.</p>
<pre class="brush: xml; title: ; notranslate">
&lt;fieldset&gt;
	&lt;legend&gt;Your dog's favorite foods:&lt;/legend&gt;

	&lt;input type=&quot;checkbox&quot; value=&quot;kibble&quot; id=&quot;kibble&quot; /&gt;
	&lt;label for=&quot;kibble&quot;&gt;Kibble&lt;/label&gt;

	&lt;input type=&quot;checkbox&quot; value=&quot;chow&quot; id=&quot;chow&quot; /&gt;
	&lt;label for=&quot;chow&quot;&gt;Chow&lt;/label&gt;

	&lt;input type=&quot;checkbox&quot; value=&quot;steak&quot; id=&quot;steak&quot; /&gt;
	&lt;label for=&quot;steak&quot;&gt;Steak&lt;/label&gt;
&lt;/fieldset&gt;
</pre>
<p>Which renders:</p>
<blockquote>
<fieldset>
<legend>Your dog&#8217;s favorite foods:</legend>
<input id="kibble" type="checkbox" value="kibble" /> <label for="kibble">Kibble</label></p>
<input id="chow" type="checkbox" value="chow" /> <label for="chow">Chow</label></p>
<input id="steak" type="checkbox" value="steak" /> <label for="steak">Steak</label><br />
</fieldset>
</blockquote>
<div class="clear"></div>
<p>Great! Now we can click either the checkbox or the label, and they both check or uncheck the box! <strong>But.. we&#8217;re not done.</strong></p>
<p>The problem with the current setup is that the cursor does not change at all, and <strong>does not alert the user that &#8216;You can click me!&#8217;</strong></p>
<p>If we add some simple CSS, we can then create a enriched user interface.</p>
<p><a id="final" name="final"></a></p>
<p>First, lets give a class to this fieldset so we do not affect other inputs or labels.</p>
<pre class="brush: xml; title: ; notranslate">
&lt;fieldset class=&quot;checkbox&quot;&gt;
	&lt;legend&gt;Your dog's favorite foods:&lt;/legend&gt;

	&lt;input type=&quot;checkbox&quot; value=&quot;kibble&quot; id=&quot;kibble&quot; /&gt;
	&lt;label for=&quot;kibble&quot;&gt;Kibble&lt;/label&gt;

	&lt;input type=&quot;checkbox&quot; value=&quot;chow&quot; id=&quot;chow&quot; /&gt;
	&lt;label for=&quot;chow&quot;&gt;Chow&lt;/label&gt;

	&lt;input type=&quot;checkbox&quot; value=&quot;steak&quot; id=&quot;steak&quot; /&gt;
	&lt;label for=&quot;steak&quot;&gt;Steak&lt;/label&gt;
&lt;/fieldset&gt;
</pre>
<p>Now we can add some CSS.</p>
<pre class="brush: css; title: ; notranslate">
.checkbox input { cursor:pointer;  }
.checkbox label:hover { cursor:pointer; color:#ffffcc; }
</pre>
<p>What this declaration is doing is; When we hover or any inputs or labels within the fieldset with the class of &#8216;checkbox&#8217;, it changes the cursor to a pointer, and creates a roll-over color for the label.</p>
<p style="color:#990000;">*NOTE* Since you are using the :hover pseudo class, you can not use &#8216;inline-css&#8217; to style these elements.</p>
<p>Which renders:</p>
<blockquote>
<fieldset class="checkbox">
<legend>Your dog&#8217;s favorite foods:</legend>
<input id="kibble2" type="checkbox" value="kibble" /> <label for="kibble2">Kibble</label></p>
<input id="chow2" type="checkbox" value="chow" /> <label for="chow2">Chow</label></p>
<input id="steak2" type="checkbox" value="steak" /> <label for="steak2">Steak</label><br />
</fieldset>
</blockquote>
<div class="clear"></div>
<p style="color:#006600;">Success! We now have a clean, usable, and attractive interface. Plus, we&#8217;ve created valid xHTML and CSS without having to use any Javascript or other methods.</p>
<h2>Like the article? Leave a comment!</h2>
]]></content:encoded>
			<wfw:commentRss>http://www.bryanwatson.ca/blog/clickable-checkbox-labels/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IE Lost 11.4% Market Share</title>
		<link>http://www.bryanwatson.ca/blog/ie-lost-11-4-market-share</link>
		<comments>http://www.bryanwatson.ca/blog/ie-lost-11-4-market-share#comments</comments>
		<pubDate>Thu, 09 Jul 2009 04:56:24 +0000</pubDate>
		<dc:creator>Bryan Watson</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.bryanwatson.ca/?p=469</guid>
		<description><![CDATA[Good news on the horizon, Internet Explorer has lost 11.4% market share since March 2009. Since March, Internet Explorer Lost 11.4 Percent Share To Firefox, Safari, And Chrome Quoted from TechCrunch The new browser wars on on. More than a decade after Microsoft killed off Netscape with Internet Explorer, competition in the browser market has [...]]]></description>
			<content:encoded><![CDATA[<p>Good news on the horizon, <strong>Internet Explorer has lost 11.4% market share since March 2009</strong>.</p>
<h3><a href="http://www.techcrunch.com/2009/07/05/since-march-internet-explorer-lost-114-percent-share-to-firefox-safari-and-chrome/?awesm=tcrn.ch_5CP" target="_blank">Since March, Internet Explorer Lost 11.4 Percent Share To Firefox, Safari, And Chrome</a></h3>
<p><a href="http://www.techcrunch.com/2009/07/05/since-march-internet-explorer-lost-114-percent-share-to-firefox-safari-and-chrome/?awesm=tcrn.ch_5CP" target="_blank"><img src="http://www.bryanwatson.ca/wp-content/uploads/2009/07/StatCounterGlobal.jpg" alt="Browser Market Shares" title="Browser Market Shares" /></a></p>
<h3>Quoted from TechCrunch</h3>
<blockquote><p>The new browser wars on on. More than a decade after Microsoft killed off Netscape with Internet Explorer, competition in the browser market has never been stronger. Just last week, Mozilla released Firefox 3.5, which has now been downloaded nearly 14 million times. Earlier in June, Apple released Safari 4. In March, Microsoft introduced Internet Explorer 8, and Google came out with a speedier beta of its Chrome browser.</p>
<p>Some early data is coming in showing relative market share and how fast people are upgrading. If you look at the chart above from Statcounter, it indicates that since March Internet Explorer has lost 11.4 percent market share to other browsers. That is the combined market share of IE8, IE7, and IE6. Certainly IE8 (the light blue line) has been growing strong since its release last March, capturing 16.7 percent of the market as of July 4. Those strong gains make up for most of the drop in IE7’s market share from 49.1 percent in March to 30.1 percent yesterday, indicating that Microsoft is doing a good job of getting existing IE7 users to upgrade at a steady pace. And in mid-June, IE8 finally surpassed IE6, which still stubbornly holds a 7.6 percent share. Add those three up, (IE6+IE7+IE8), however, and IE all together holds only a 54.4 percent market share versus the 65.8 percent combined share in March, 2009.</p>
<p>In just over three months, Internet Explorer has seen its overall market share erode by 11.4 percent. Where did that go? It went to Firefox, Safari, and Chrome. Nearly 5 percent of that, or about half, went to Firefox 3.0, which currently has 27.6 percent market share. That doesn’t count last week’s upgrade. See the dotted line just below the light blue IE8 line? That is a combined set of “other” browsers and appears to include Firefox 3.5, Safari 4, and Chrome 2.0.</p>
<p>If you look at a 30-day version of that same chart, it shows Safari 4 with 4 percent market share and Chrome with 3 percent market share. It doesn’t yet break out Firefox 3.5, but if you assume that makes up the bulk of the remaining dotted line which jumped to nearly pass IE6 in the past week, you can figure out more or less which browsers are taking share from Microsoft. (I’ve used data from the most recent daily chart in this post, but embedded the monthly chart below which has data as of June 30).</p>
<p>As I said, this is early data from one source. Net Applications, another commonly cited source for browser market share, is currently reviewing its June numbers, but I have a feeling they will show similar trends. (This Wikipedia page shows other browser market share sources, most of them haven’t been updated since March). It is difficult to make any firm conclusions at this point, since market share is shifting so rapidly as every major (and minor) browser tries to convince users to upgrade.</p>
<p>But we are in the midst of a major upgrade cycle simultaneously across IE, FireFox, and Safari (with the Chrome wild card thrown in). When all is said and done, we might see a major shake-up in market share and almost definitely will see leadership pass from IE7 to another browser. The question is will that be IE8 or Firefox? Whichever one wins, the good news is that IE6 is finally dying.</p></blockquote>
<p>Personally, I believe once the more modern technology becomes more commercially available for businesses, we will finally be able to attend the funeral of IE6.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bryanwatson.ca/blog/ie-lost-11-4-market-share/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Giving Too Many Choices</title>
		<link>http://www.bryanwatson.ca/blog/giving-your-client-too-many-choices</link>
		<comments>http://www.bryanwatson.ca/blog/giving-your-client-too-many-choices#comments</comments>
		<pubDate>Tue, 23 Jun 2009 04:20:47 +0000</pubDate>
		<dc:creator>Bryan Watson</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.bryanwatson.ca/?p=450</guid>
		<description><![CDATA[While going through my logo design process, I wondered if there was any sort of scientific approach as to how many variations or choices you should present your client. I came across this interesting article written by Derek Sivers, explaining and giving some interesting facts on the subject of presenting choices to both customers and [...]]]></description>
			<content:encoded><![CDATA[<p>While going through my logo design process, I wondered if there was any sort of scientific approach as to how many variations or choices you should present your client.</p>
<p>I came across this interesting article written by <a href="http://sivers.org/" target="_blank">Derek Sivers</a>, explaining and giving some interesting facts on the subject of presenting choices to both customers and clients alike.</p>
<p>It&#8217;s quite a good read, and you can view the article here: <a href="http://sivers.org/jam" target="_blank">http://sivers.org/jam</a></p>
<h3>Quoted from Derk Sivers:</h3>
<blockquote><p>For 10 years, Columbia professor <a href="http://www.columbia.edu/%7Ess957/">Sheena Iyengar</a> has been studying choice.  For her research paper, “<a href="http://www.columbia.edu/%7Ess957/whenchoice.html">When Choice is Demotivating</a>”, they ran a great test:</p>
<p>They set up a free tasting booth in a grocery store, <strong>with six different jams.  40% of the customers stopped to taste.  30% of those bought some.</strong></p>
<p>A week later, they set up the same booth in the same store, but this time <strong>with twenty-four different jams.  60% of the customers stopped to taste.  But only 3% bought some!</strong></p>
<p>Both groups actually tasted an average of 1.5 jams. So the huge difference in buying can’t be blamed on the 24-jam customers being full.</p>
<p>Lessons learned:</p>
<ol>
<li>Having many choices seems appealing (40% vs 60% stopped to taste)</li>
<li>Having many choices makes them 10 times less likely to buy (30% vs 3% actually bought)</li>
</ol>
<p>Surgeon <a href="http://www.gawande.com/bio.htm">Atul Gawande</a> found that 65% of people surveyed said <em>if</em> they were to get cancer, they’d want to choose their own treatment.  Among people surveyed who really <em>do</em> have cancer, only 12% of patients want to choose their own treatment.</p>
<p>So, if you ask your customers if they want extensive choice, they will say they do – but they really don’t.</p>
<p>I recommend the book “<a href="http://sivers.org/book/ParadoxOfChoice">The Paradox of Choice</a>” if you’re interested in this.</p>
<h3>Where does this NOT apply?</h3>
<p>In “preference matching” contexts, <strong>where people come looking for something they already know and prefer</strong>, extensive selection increases the likelihood they’ll be successful in their search. (For example: a menu at a Chinese restaurant.)</p>
<p>Many tests have shown that <strong>when people are given some choice versus none</strong> (choosing between six possible activities versus being assigned an activity), having some choice increases motivation and enhances performance.</p>
<h3>How do we use this info?</h3>
<p>Online stores often offer too many choices on their front page. Lists of dozens of new arrivals, top sellers, sale items, and categories.</p>
<p>Artists showcasing their art (music, essays, photos) often present a giant list of everything they’ve done.</p>
<p>But all of us could come to these conclusions:</p>
<ul>
<li><strong>Only present 3 to 6 choices at a time</strong>. (No less than 3. No more than 6.)</li>
<li><strong>Only show your deep selection when people are searching for something specific</strong>.</li>
</ul>
<p>My favorite example of this is Firefox’s <a href="http://www.mozillazine.org/misc/about:config/">about:config</a> feature. Those hundreds of intimidating options are hidden from most people, but there for the few who need them.</p></blockquote>
<p>I found that these basic rules apply to almost any situation, whether it be prototyping, branding, product design, or even options for stages of web design.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bryanwatson.ca/blog/giving-your-client-too-many-choices/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

