<?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 on: &#8220;Where&#8217;s my Googlebox?!&#8221; &#8211; adventures in search for silver surfers</title>
	<atom:link href="http://www.iheni.com/wheres-my-googlebox-adventures-in-search-for-silver-surfers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.iheni.com/wheres-my-googlebox-adventures-in-search-for-silver-surfers/</link>
	<description></description>
	<lastBuildDate>Mon, 09 Aug 2010 18:27:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Teaching Web Searching To People With Cognitive Disabilities &#171; Clear Helper</title>
		<link>http://www.iheni.com/wheres-my-googlebox-adventures-in-search-for-silver-surfers/comment-page-1/#comment-29450</link>
		<dc:creator>Teaching Web Searching To People With Cognitive Disabilities &#171; Clear Helper</dc:creator>
		<pubDate>Thu, 17 Jun 2010 02:59:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1943#comment-29450</guid>
		<description>[...] during my interviews with them. The same problem was described by Henny in her article, &#8220;&#8216;Where’s my Googlebox?!&#8217; – adventures in search for silver surfers&#8220;. It and its subsequent discussion inspired me to write this [...]</description>
		<content:encoded><![CDATA[<p>[...] during my interviews with them. The same problem was described by Henny in her article, &#8220;&#8216;Where’s my Googlebox?!&#8217; – adventures in search for silver surfers&#8220;. It and its subsequent discussion inspired me to write this [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The role of accessibility in the usability profession today &#8211; and tomorrow &#171; The &#8217;58 sound</title>
		<link>http://www.iheni.com/wheres-my-googlebox-adventures-in-search-for-silver-surfers/comment-page-1/#comment-28562</link>
		<dc:creator>The role of accessibility in the usability profession today &#8211; and tomorrow &#171; The &#8217;58 sound</dc:creator>
		<pubDate>Mon, 31 May 2010 08:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1943#comment-28562</guid>
		<description>[...] Gerontechnologist &#8211; perhaps my most left-field suggestion, I think accessibility specialists should recognise the particular benefits of involving older people in user centred design, for the added-value that they are likely to provide as participants in requirements gathering activities, and evaluators throughout the design lifecycle. Arguably accessibility guidelines focus on the more extreme end of impairment, at the expense of those with less severe, but multiple, impairments. Evaluating with disabled people is important, and rewarding, but recruitment and scheduling can sometimes be difficult. So the unpredictability of the presence of any age-related sensory, dexterity or cognitive impairments make recruitment of older participants for participatory design and usability testing a particularly attractive option, particularly if resources are tight (see Henny Swan&#8217;s comments on the value of testing a web browser with older people). [...]</description>
		<content:encoded><![CDATA[<p>[...] Gerontechnologist &#8211; perhaps my most left-field suggestion, I think accessibility specialists should recognise the particular benefits of involving older people in user centred design, for the added-value that they are likely to provide as participants in requirements gathering activities, and evaluators throughout the design lifecycle. Arguably accessibility guidelines focus on the more extreme end of impairment, at the expense of those with less severe, but multiple, impairments. Evaluating with disabled people is important, and rewarding, but recruitment and scheduling can sometimes be difficult. So the unpredictability of the presence of any age-related sensory, dexterity or cognitive impairments make recruitment of older participants for participatory design and usability testing a particularly attractive option, particularly if resources are tight (see Henny Swan&#8217;s comments on the value of testing a web browser with older people). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rosemary Gabel</title>
		<link>http://www.iheni.com/wheres-my-googlebox-adventures-in-search-for-silver-surfers/comment-page-1/#comment-24839</link>
		<dc:creator>Rosemary Gabel</dc:creator>
		<pubDate>Fri, 05 Mar 2010 15:58:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1943#comment-24839</guid>
		<description>Teaching beginners is my job, both the Seniors and the primary grade (K-6) children. One of my big frustrations has been trying to get them to use the keyboard.  Kinders do everything with a mouse (they&#039;re just learning their letters...) so the mouse habit is learned first.  Only after they start learning their touch typing (3rd grade) can I even begin to get them to use the Enter key.. even so, they will still reach for the mouse.  With the Seniors it is the same if they have NEVER learned touch typing.  
The children have the same trouble knowing in which box to type a search query. Unfortunately, the 20 min of instruction to know the difference between the browser and the web page, has not been given the priority it needs (by administrators, and teachers alike.)
They just need to &quot;get there fast!&quot;  So, hats off to the programmers who let the URL box be equally useful to Search.  Now they can use the tool, without having to understand it.  (The same as everyone who looks at an unfamiliar tool, and just uses trial and error to make it work.)  I wish it were a properly organized world, but then, I didn&#039;t build it!
Very few people want to take the time to learn.. they just want results. So the more clues given on the page, the better, like a grayed out word IN the box saying &quot;SEARCH&quot;.  Keep up the useability testing, and keep it intuitive..(not assumed!)</description>
		<content:encoded><![CDATA[<p>Teaching beginners is my job, both the Seniors and the primary grade (K-6) children. One of my big frustrations has been trying to get them to use the keyboard.  Kinders do everything with a mouse (they&#8217;re just learning their letters&#8230;) so the mouse habit is learned first.  Only after they start learning their touch typing (3rd grade) can I even begin to get them to use the Enter key.. even so, they will still reach for the mouse.  With the Seniors it is the same if they have NEVER learned touch typing.<br />
The children have the same trouble knowing in which box to type a search query. Unfortunately, the 20 min of instruction to know the difference between the browser and the web page, has not been given the priority it needs (by administrators, and teachers alike.)<br />
They just need to &#8220;get there fast!&#8221;  So, hats off to the programmers who let the URL box be equally useful to Search.  Now they can use the tool, without having to understand it.  (The same as everyone who looks at an unfamiliar tool, and just uses trial and error to make it work.)  I wish it were a properly organized world, but then, I didn&#8217;t build it!<br />
Very few people want to take the time to learn.. they just want results. So the more clues given on the page, the better, like a grayed out word IN the box saying &#8220;SEARCH&#8221;.  Keep up the useability testing, and keep it intuitive..(not assumed!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shilpa2</title>
		<link>http://www.iheni.com/wheres-my-googlebox-adventures-in-search-for-silver-surfers/comment-page-1/#comment-23995</link>
		<dc:creator>shilpa2</dc:creator>
		<pubDate>Mon, 15 Feb 2010 09:01:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1943#comment-23995</guid>
		<description>I also had a sense that having a URL address box populated with text put people off using it.”That’s been happening to me during usability testing as well, with a broad range of user types.

&lt;a href=&quot;http://www.mytwitteradder.com&quot; rel=&quot;nofollow&quot;&gt;get more twitter followers&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I also had a sense that having a URL address box populated with text put people off using it.”That’s been happening to me during usability testing as well, with a broad range of user types.</p>
<p><a href="http://www.mytwitteradder.com" rel="nofollow">get more twitter followers</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shilpa</title>
		<link>http://www.iheni.com/wheres-my-googlebox-adventures-in-search-for-silver-surfers/comment-page-1/#comment-23847</link>
		<dc:creator>shilpa</dc:creator>
		<pubDate>Thu, 11 Feb 2010 10:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1943#comment-23847</guid>
		<description>It&#039;s really superb. I thanks too post for this.

&lt;a href=&quot;http://www.duiattorneyorangecountyca.com&quot; rel=&quot;nofollow&quot;&gt;DUI Helps &lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>It&#8217;s really superb. I thanks too post for this.</p>
<p><a href="http://www.duiattorneyorangecountyca.com" rel="nofollow">DUI Helps </a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
