<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Accessible Synchronous Communication: Reloaded</title>
	<atom:link href="http://curbcut.net/accessibility/accessible-synchronous-communication-reloaded/feed/" rel="self" type="application/rss+xml" />
	<link>http://curbcut.net/accessibility/accessible-synchronous-communication-reloaded/</link>
	<description>open and accessible</description>
	<lastBuildDate>Mon, 14 Jun 2010 11:07:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Joe Clark</title>
		<link>http://curbcut.net/accessibility/accessible-synchronous-communication-reloaded/comment-page-1/#comment-42</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Sat, 22 May 2004 20:38:09 +0000</pubDate>
		<guid isPermaLink="false">http://curbcut.net/2004/03/accessible-synchronous-communication-reloaded/#comment-42</guid>
		<description>The projection was for the convenience of the panel host, who could see. He selected questions to answer. The other text on the screen, while of interest, was not necessary to further the panel discussion.

Also, no, chat mode is not easy to make accessible to screen-reader users.</description>
		<content:encoded><![CDATA[<p>The projection was for the convenience of the panel host, who could see. He selected questions to answer. The other text on the screen, while of interest, was not necessary to further the panel discussion.</p>
<p>Also, no, chat mode is not easy to make accessible to screen-reader users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Coburn</title>
		<link>http://curbcut.net/accessibility/accessible-synchronous-communication-reloaded/comment-page-1/#comment-41</link>
		<dc:creator>Jeff Coburn</dc:creator>
		<pubDate>Tue, 30 Mar 2004 17:48:34 +0000</pubDate>
		<guid isPermaLink="false">http://curbcut.net/2004/03/accessible-synchronous-communication-reloaded/#comment-41</guid>
		<description>It seems like it would be cool if everyone was using a rendezvous enabled computer. Until then it seems like the best solution might be to use an IRC channel. I&#039;m sure only a few flame wars would break out:)</description>
		<content:encoded><![CDATA[<p>It seems like it would be cool if everyone was using a rendezvous enabled computer. Until then it seems like the best solution might be to use an IRC channel. I’m sure only a few flame wars would break out:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chirstopher Phillips</title>
		<link>http://curbcut.net/accessibility/accessible-synchronous-communication-reloaded/comment-page-1/#comment-40</link>
		<dc:creator>Chirstopher Phillips</dc:creator>
		<pubDate>Tue, 30 Mar 2004 17:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://curbcut.net/2004/03/accessible-synchronous-communication-reloaded/#comment-40</guid>
		<description>Interesting conversation- the iChat conversation was n&#039;t available to Dr. Slatin, but neither was it available to any PC users in the audience. I think that at the very least, other panel members should be consulted- as long as good questions are read aloud before being answered, it still might work- especially if a transcript of the chat session was made available.

However, I love the idea of being able to chat during a session. While it can occassionaly distract  participants from teh presenter, it gives participants something to do when the presentation is boring and can facilitate more knowledge being shared among the audience than the  presenter has time to give (and knowledge that he may not know).</description>
		<content:encoded><![CDATA[<p>Interesting conversation– the iChat conversation was n’t available to Dr. Slatin, but neither was it available to any PC users in the audience. I think that at the very least, other panel members should be consulted– as long as good questions are read aloud before being answered, it still might work– especially if a transcript of the chat session was made available.</p>
<p>However, I love the idea of being able to chat during a session. While it can occassionaly distract  participants from teh presenter, it gives participants something to do when the presentation is boring and can facilitate more knowledge being shared among the audience than the  presenter has time to give (and knowledge that he may not know).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danielle</title>
		<link>http://curbcut.net/accessibility/accessible-synchronous-communication-reloaded/comment-page-1/#comment-39</link>
		<dc:creator>Danielle</dc:creator>
		<pubDate>Tue, 30 Mar 2004 17:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://curbcut.net/2004/03/accessible-synchronous-communication-reloaded/#comment-39</guid>
		<description>Logically chat should be a very accessible technology, no? Deaf people use it to replace quick conversations with people who don&#039;t use ASL. A screenreader can read the exchanges (I assume). Looks like the problem comes when you want to move a chat from two people&#039;s individual computers to a full-room display.</description>
		<content:encoded><![CDATA[<p>Logically chat should be a very accessible technology, no? Deaf people use it to replace quick conversations with people who don’t use ASL. A screenreader can read the exchanges (I assume). Looks like the problem comes when you want to move a chat from two people’s individual computers to a full-room display.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
