<?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: Is it time for social networks grow up?</title>
	<atom:link href="http://www.iheni.com/is-it-time-for-social-networks-grow-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.iheni.com/is-it-time-for-social-networks-grow-up/</link>
	<description></description>
	<lastBuildDate>Thu, 11 Mar 2010 06:11:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: iheni</title>
		<link>http://www.iheni.com/is-it-time-for-social-networks-grow-up/comment-page-1/#comment-3863</link>
		<dc:creator>iheni</dc:creator>
		<pubDate>Mon, 26 Jan 2009 07:42:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=666#comment-3863</guid>
		<description>Dave, it&#039;s refreshing to hear you actively ask for feedback and I hope it doesn&#039;t go unnoticed. Aside from having feedback as anecdotal evidence to back up your case for accessibility internally it is also invaluable when judging if the sites you are building with accessibility in mind are built in a way that users actually want. 

A couple of things that you could try is to invite a screen reader, voice input users or volunteers in to your office meet with the budget holders and actually use the site in front of them. This is always a sure fast way to make people sit up and listen. If this is tricky there are lots of videos out there that you could show people. Jon Gibbons has pulled together a good selection at http://lab.dotjay.co.uk/notes/assistive-technology/videos/.

Other things you can do is make sure that you have a clear feedback mechanism on your site and an email and actively ask people what they think. The only thing I would caution with that is to make sure you, or somebody, is available to manage the inbox - there&#039;s nothing worse that asking questions and providing comments and it going ignored.

Finally, a book that you may find handy is &quot;Just Ask: integrating accessibility throughout design&quot; by Shawn Henry (http://www.uiaccess.com/accessucd/about.html). This has some really great pointers about user testing and so on.

I admire your efforts and feel your pain, I know how tough it can be, good luck!</description>
		<content:encoded><![CDATA[<p>Dave, it&#8217;s refreshing to hear you actively ask for feedback and I hope it doesn&#8217;t go unnoticed. Aside from having feedback as anecdotal evidence to back up your case for accessibility internally it is also invaluable when judging if the sites you are building with accessibility in mind are built in a way that users actually want. </p>
<p>A couple of things that you could try is to invite a screen reader, voice input users or volunteers in to your office meet with the budget holders and actually use the site in front of them. This is always a sure fast way to make people sit up and listen. If this is tricky there are lots of videos out there that you could show people. Jon Gibbons has pulled together a good selection at <a href="http://lab.dotjay.co.uk/notes/assistive-technology/videos/" rel="nofollow">http://lab.dotjay.co.uk/notes/assistive-technology/videos/</a>.</p>
<p>Other things you can do is make sure that you have a clear feedback mechanism on your site and an email and actively ask people what they think. The only thing I would caution with that is to make sure you, or somebody, is available to manage the inbox &#8211; there&#8217;s nothing worse that asking questions and providing comments and it going ignored.</p>
<p>Finally, a book that you may find handy is &#8220;Just Ask: integrating accessibility throughout design&#8221; by Shawn Henry (<a href="http://www.uiaccess.com/accessucd/about.html" rel="nofollow">http://www.uiaccess.com/accessucd/about.html</a>). This has some really great pointers about user testing and so on.</p>
<p>I admire your efforts and feel your pain, I know how tough it can be, good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.iheni.com/is-it-time-for-social-networks-grow-up/comment-page-1/#comment-3827</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 23 Jan 2009 20:25:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=666#comment-3827</guid>
		<description>To expand on what Todd said: Doing nearly anything from a mobile device is tricky, even for people who are disability-challenged.

As a web developer who desperately wants to make sites more accessible but can&#039;t get support to spend time changing existing sites or training other staff, I implore users with disabilities to make themselves heard! If a site is coded such that it is not usable or conflicts with additional software/hardware that you require, please send a note to let them know. We have over 1500 employees and work with over 20k students, and no one has ever told us that we have accessibility problems. I just can&#039;t sell accessibility improvements to management as a priority until I have stakeholder feedback showing that there is a problem.</description>
		<content:encoded><![CDATA[<p>To expand on what Todd said: Doing nearly anything from a mobile device is tricky, even for people who are disability-challenged.</p>
<p>As a web developer who desperately wants to make sites more accessible but can&#8217;t get support to spend time changing existing sites or training other staff, I implore users with disabilities to make themselves heard! If a site is coded such that it is not usable or conflicts with additional software/hardware that you require, please send a note to let them know. We have over 1500 employees and work with over 20k students, and no one has ever told us that we have accessibility problems. I just can&#8217;t sell accessibility improvements to management as a priority until I have stakeholder feedback showing that there is a problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iheni</title>
		<link>http://www.iheni.com/is-it-time-for-social-networks-grow-up/comment-page-1/#comment-3801</link>
		<dc:creator>iheni</dc:creator>
		<pubDate>Thu, 22 Jan 2009 16:11:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=666#comment-3801</guid>
		<description>Todd - you raise some of the key challenges that people face with social networking over a mobile phone. Like you I agree that you need to manage the information overload and make it much more context sensitive and relevant. Hopefully we&#039;ll see some solutions for this in the future...let&#039;s face it we have to!

Interesting link by the way, will add it to my list above. Too bad you weren&#039;t at the workshop as I think your ideas would have gone down really well. There is a mailing list covering the future of social networking at you can subscribe to it by sending a message with &quot;subscribe&quot; in the subject to public-social-web-talk-request@w3.org . Be great if you were on there :)

If anyone else has any links to share let me know and I&#039;ll add them above.</description>
		<content:encoded><![CDATA[<p>Todd &#8211; you raise some of the key challenges that people face with social networking over a mobile phone. Like you I agree that you need to manage the information overload and make it much more context sensitive and relevant. Hopefully we&#8217;ll see some solutions for this in the future&#8230;let&#8217;s face it we have to!</p>
<p>Interesting link by the way, will add it to my list above. Too bad you weren&#8217;t at the workshop as I think your ideas would have gone down really well. There is a mailing list covering the future of social networking at you can subscribe to it by sending a message with &#8220;subscribe&#8221; in the subject to <a href="mailto:public-social-web-talk-request@w3.org">public-social-web-talk-request@w3.org</a> . Be great if you were on there <img src='http://www.iheni.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>If anyone else has any links to share let me know and I&#8217;ll add them above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://www.iheni.com/is-it-time-for-social-networks-grow-up/comment-page-1/#comment-3790</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Wed, 21 Jan 2009 13:48:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=666#comment-3790</guid>
		<description>My favorite topic.

Yes they need to grow-up, and I define &quot;grow-up&quot; as be more mature and stop acting like selfish children by letting us long suffering user have control over our data!

Use of social networks with a mobile phone is tricky, especially if you factor in activity streams from everyone you follow across dozens and dozens of sites. The slang term is &quot;drinking from the fire hose&quot;. Managing all that data on a tiny screen, often without a QWERTY keyboard is nearly impossible - here&#039;s all of us trying to find a solution:

http://www.readwriteweb.com/archives/do_you_want_this_activity_stre.php

Great post!</description>
		<content:encoded><![CDATA[<p>My favorite topic.</p>
<p>Yes they need to grow-up, and I define &#8220;grow-up&#8221; as be more mature and stop acting like selfish children by letting us long suffering user have control over our data!</p>
<p>Use of social networks with a mobile phone is tricky, especially if you factor in activity streams from everyone you follow across dozens and dozens of sites. The slang term is &#8220;drinking from the fire hose&#8221;. Managing all that data on a tiny screen, often without a QWERTY keyboard is nearly impossible &#8211; here&#8217;s all of us trying to find a solution:</p>
<p><a href="http://www.readwriteweb.com/archives/do_you_want_this_activity_stre.php" rel="nofollow">http://www.readwriteweb.com/archives/do_you_want_this_activity_stre.php</a></p>
<p>Great post!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
