<?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: Application Opens Up Twitter To Disabled Users</title>
	<atom:link href="http://www.headstar.com/eablive/?feed=rss2&#038;p=321" rel="self" type="application/rss+xml" />
	<link>http://www.headstar.com/eablive/?p=321</link>
	<description>Access to technology for all</description>
	<lastBuildDate>Sun, 01 Apr 2018 16:32:15 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.0.1</generator>
	<item>
		<title>By: Jake</title>
		<link>http://www.headstar.com/eablive/?p=321&#038;cpage=1#comment-6131</link>
		<dc:creator><![CDATA[Jake]]></dc:creator>
		<pubDate>Tue, 07 Jun 2011 19:12:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=321#comment-6131</guid>
		<description><![CDATA[I use Accessible Twitter--now renamed Easy Chirp--all the time at my volunteer job and love it. It is 100% accessible with System Access, which is a screen reader I use. In addition, I&#039;ve tested Easy Chirp briefly with Non-Visual Desktop Access and it seems to work pretty well. Kudos to Dennis for doing a great job.]]></description>
		<content:encoded><![CDATA[<p>I use Accessible Twitter&#8211;now renamed Easy Chirp&#8211;all the time at my volunteer job and love it. It is 100% accessible with System Access, which is a screen reader I use. In addition, I&#8217;ve tested Easy Chirp briefly with Non-Visual Desktop Access and it seems to work pretty well. Kudos to Dennis for doing a great job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Accessible Twitter</title>
		<link>http://www.headstar.com/eablive/?p=321&#038;cpage=1#comment-5427</link>
		<dc:creator><![CDATA[Accessible Twitter]]></dc:creator>
		<pubDate>Wed, 26 Aug 2009 17:46:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=321#comment-5427</guid>
		<description><![CDATA[My response to Lucas&#039; comment:

-Accessible Twitter fixes these issues (and more) in Twitter.com: the navigation is inconsistent, doesn&#039;t display username of account signed in, the Favorite and Reply links are STILL not keyboard accessible, JavaScript is required, doesn&#039;t work in Lynx browser, may be illegible due to custom colors, code is not standards-compliant, etc.

-Tweets are marked up as blockquotes because they are blockquotes; this is proper semantic coding. The rendering of that code is up to the user-agent (browser).

-There more to do on Twitter than just post and read tweets; for example, Accessible Twitter provides a Trends page, a Popular Links page, and previews for images linked in tweets.]]></description>
		<content:encoded><![CDATA[<p>My response to Lucas&#8217; comment:</p>
<p>-Accessible Twitter fixes these issues (and more) in Twitter.com: the navigation is inconsistent, doesn&#8217;t display username of account signed in, the Favorite and Reply links are STILL not keyboard accessible, JavaScript is required, doesn&#8217;t work in Lynx browser, may be illegible due to custom colors, code is not standards-compliant, etc.</p>
<p>-Tweets are marked up as blockquotes because they are blockquotes; this is proper semantic coding. The rendering of that code is up to the user-agent (browser).</p>
<p>-There more to do on Twitter than just post and read tweets; for example, Accessible Twitter provides a Trends page, a Popular Links page, and previews for images linked in tweets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lucas</title>
		<link>http://www.headstar.com/eablive/?p=321&#038;cpage=1#comment-5425</link>
		<dc:creator><![CDATA[lucas]]></dc:creator>
		<pubDate>Wed, 19 Aug 2009 07:14:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=321#comment-5425</guid>
		<description><![CDATA[I am using twitter since 2 months ago. My first impression of the
service was interesting, and I didn&#039;t find anything so inaccessible.
When I saw the accessibletwitter i was curious to sse what they changed
in this version, and when I tryed it, it was uncomfortable. The fact is:
when you open your twitter page, what you wanna see is your friends&#039;
updates, and just it. There&#039;s just it to do on twitter.
sometimes, you have a lot of tweets to read, so, a good interface is all
you want to helps you in this case. On twitter, the first link will show
you the name of the person, the second link will show you the account
of the person (it&#039;s important to you send them direct messages, when you
put a @ then their nicks/account, and then your message), and then,
finally, their tweets. The accessible twitter turned this simple thing
in a strange apresentation of the message. All the tweets are marked
with a block quot, making you slow in the time you are reading the
tweets. The information where on twitter were organized in one line to
show you the hour when this tweets was posted, where the person was
posting it : like web, twitterfox(a addon for firefox to you make your
tweets), etc, are separated in a lot of lines, making, again, you slowly
in the time you are reading your tweets.
For me, I like the original twitter, and I will keep using that.]]></description>
		<content:encoded><![CDATA[<p>I am using twitter since 2 months ago. My first impression of the<br />
service was interesting, and I didn&#8217;t find anything so inaccessible.<br />
When I saw the accessibletwitter i was curious to sse what they changed<br />
in this version, and when I tryed it, it was uncomfortable. The fact is:<br />
when you open your twitter page, what you wanna see is your friends&#8217;<br />
updates, and just it. There&#8217;s just it to do on twitter.<br />
sometimes, you have a lot of tweets to read, so, a good interface is all<br />
you want to helps you in this case. On twitter, the first link will show<br />
you the name of the person, the second link will show you the account<br />
of the person (it&#8217;s important to you send them direct messages, when you<br />
put a @ then their nicks/account, and then your message), and then,<br />
finally, their tweets. The accessible twitter turned this simple thing<br />
in a strange apresentation of the message. All the tweets are marked<br />
with a block quot, making you slow in the time you are reading the<br />
tweets. The information where on twitter were organized in one line to<br />
show you the hour when this tweets was posted, where the person was<br />
posting it : like web, twitterfox(a addon for firefox to you make your<br />
tweets), etc, are separated in a lot of lines, making, again, you slowly<br />
in the time you are reading your tweets.<br />
For me, I like the original twitter, and I will keep using that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
