<?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: Standards.Next rocking cognition and accessibility</title>
	<atom:link href="http://www.iheni.com/standardsnext-cognition/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.iheni.com/standardsnext-cognition/</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: iheni</title>
		<link>http://www.iheni.com/standardsnext-cognition/comment-page-1/#comment-17275</link>
		<dc:creator>iheni</dc:creator>
		<pubDate>Wed, 30 Sep 2009 13:43:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1709#comment-17275</guid>
		<description>Hi Mark - thanks for letting me know, all fixed now :)</description>
		<content:encoded><![CDATA[<p>Hi Mark &#8211; thanks for letting me know, all fixed now <img src='http://www.iheni.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.iheni.com/standardsnext-cognition/comment-page-1/#comment-17271</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 30 Sep 2009 13:25:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1709#comment-17271</guid>
		<description>Hi Heni,

Great to hear from you at Accessibility 2.0. Was just reading up on Standards Next (missed the cognition and accessibility session) and noticed that your linkback to standards-next.org is missing a &quot;d&quot; , thought you&#039;d want to know.

Cheers

@copious</description>
		<content:encoded><![CDATA[<p>Hi Heni,</p>
<p>Great to hear from you at Accessibility 2.0. Was just reading up on Standards Next (missed the cognition and accessibility session) and noticed that your linkback to standards-next.org is missing a &#8220;d&#8221; , thought you&#8217;d want to know.</p>
<p>Cheers</p>
<p>@copious</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Standards.Next &#171; hi.antonia</title>
		<link>http://www.iheni.com/standardsnext-cognition/comment-page-1/#comment-17004</link>
		<dc:creator>Standards.Next &#171; hi.antonia</dc:creator>
		<pubDate>Sat, 26 Sep 2009 17:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1709#comment-17004</guid>
		<description>[...] Henny Swan [...]</description>
		<content:encoded><![CDATA[<p>[...] Henny Swan [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iheni</title>
		<link>http://www.iheni.com/standardsnext-cognition/comment-page-1/#comment-16814</link>
		<dc:creator>iheni</dc:creator>
		<pubDate>Wed, 23 Sep 2009 14:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1709#comment-16814</guid>
		<description>Hi Joe, thanks for stopping by. If I&#039;m reading your comment correctly I&#039;d say the big thing that came out from SN was that you can&#039;t assume a user understands “bigger text” and “smaller text”. This is in part because there is no standards way of conveying this information that users can get familiar with. From comments from people of the day this is because culturally the meaning of icons / text to convey standards commands is so difficult to pin down.
I think you&#039;re right in that the browser has a responsibility to support people finding these options and this is something Opera both does and is looking to improve.

Hi Gonzalo, I think we may have exchanged comments over at Jamie Knight&#039;s blog and yes, I wish we could have podcasted it too. This is something we&#039;ll be looking at for future meetups if possible but I hope for now some of the write ups have given you some idea of how the day went.

Prisca - the lightbox discussion was a good one. A few of the attendees  - Jim O&#039;Donnel, Mike Davis, Alastair Campbell, Ian Pouncy - have continued the conversation over twitter and at Accessibility 2.0 yesterday so maybe we&#039;ll see some nifty fixes on the horizon.</description>
		<content:encoded><![CDATA[<p>Hi Joe, thanks for stopping by. If I&#8217;m reading your comment correctly I&#8217;d say the big thing that came out from SN was that you can&#8217;t assume a user understands “bigger text” and “smaller text”. This is in part because there is no standards way of conveying this information that users can get familiar with. From comments from people of the day this is because culturally the meaning of icons / text to convey standards commands is so difficult to pin down.<br />
I think you&#8217;re right in that the browser has a responsibility to support people finding these options and this is something Opera both does and is looking to improve.</p>
<p>Hi Gonzalo, I think we may have exchanged comments over at Jamie Knight&#8217;s blog and yes, I wish we could have podcasted it too. This is something we&#8217;ll be looking at for future meetups if possible but I hope for now some of the write ups have given you some idea of how the day went.</p>
<p>Prisca &#8211; the lightbox discussion was a good one. A few of the attendees  &#8211; Jim O&#8217;Donnel, Mike Davis, Alastair Campbell, Ian Pouncy &#8211; have continued the conversation over twitter and at Accessibility 2.0 yesterday so maybe we&#8217;ll see some nifty fixes on the horizon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sdoca08 (Stephanie webofficer)</title>
		<link>http://www.iheni.com/standardsnext-cognition/comment-page-1/#comment-16751</link>
		<dc:creator>Sdoca08 (Stephanie webofficer)</dc:creator>
		<pubDate>Tue, 22 Sep 2009 12:43:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1709#comment-16751</guid>
		<description>&lt;strong&gt;Twitter Comment&lt;/strong&gt;
&lt;a href=&quot;http://twitter.com/Sdoca08&quot; title=&quot;Twitter Comment&quot; rel=&quot;nofollow&quot;&gt;
&lt;div class=&quot;ccimg1&quot; title=&quot;Sdoca08 (Stephanie webofficer)&quot; style=&quot;float:left;margin-right:10px;padding:0;width:60px;height:60px;&quot;&gt;
&lt;img name=&quot;cc_image&quot; title=&quot;Sdoca08 (Stephanie webofficer)&quot; style=&quot;float:left;margin-right:10px;padding:0;width:50px;height:50px;&quot; src=&quot;http://purl.org/net/spiurl/Sdoca08&quot;/&gt;
&lt;/div&gt;
&lt;/a&gt;
&quot;Screen readers are for just about anyone who might find it useful listening to web pages.&quot; Full article [link to post]&lt;br /&gt;&lt;br /&gt; - &lt;a href=&quot;http://chatcatcher.com&quot; rel=&quot;nofollow&quot;&gt;Posted using Chat Catcher&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p><strong>Twitter Comment</strong><br />
<a href="http://twitter.com/Sdoca08" title="Twitter Comment" rel="nofollow"></p>
<div class="ccimg1" title="Sdoca08 (Stephanie webofficer)" style="float:left;margin-right:10px;padding:0;width:60px;height:60px;">
<img name="cc_image" title="Sdoca08 (Stephanie webofficer)" style="float:left;margin-right:10px;padding:0;width:50px;height:50px;" src="http://purl.org/net/spiurl/Sdoca08"/>
</div>
<p></a><br />
&#8220;Screen readers are for just about anyone who might find it useful listening to web pages.&#8221; Full article [link to post]</p>
<p> &#8211; <a href="http://chatcatcher.com" rel="nofollow">Posted using Chat Catcher</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
