<?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"
	>
<channel>
	<title>Comments on: Let&#8217;s Hear from the Disabled</title>
	<atom:link href="http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/feed/" rel="self" type="application/rss+xml" />
	<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/</link>
	<description>Helping you learn more and do more with WordPress</description>
	<pubDate>Sun, 20 Jul 2008 11:16:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: Rahel</title>
		<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-890452</link>
		<dc:creator>Rahel</dc:creator>
		<pubDate>Mon, 04 Feb 2008 12:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-890452</guid>
		<description>Hello, 

Ironically, I found this post while doing a Google search on accessible feed readers, and figured I'd comment since I blog quite a bit, use WordPress, and use Jaws for Windows.  One thing I've noticed is that information doesn't read correctly when in forms mode, (I.E., text either gets sepearated after a couple of characters onto another line, or just doesn't read at all, as seems to be the case with this form, so sorry if there are misspellings.  Also, the visual editor is completely inaccessible, so that option is out, which I'm finally noticing the loss of since Jaws has now added a copy as-is feature which allows for the copying of formatting, links, ETC. from web pages in to html-aware documents such as email, Word documents and spread sheets.  To get around this, I use the code editor, and will try to remember to compose posts in a text editor so that I can correct spelling and things like that. But all and all, I think WordPress is the most accessible blogging platform around.  I've been using it on my own server since 2005 and am glad I made the switch.</description>
		<content:encoded><![CDATA[<p>Hello, </p>
<p>Ironically, I found this post while doing a Google search on accessible feed readers, and figured I&#8217;d comment since I blog quite a bit, use WordPress, and use Jaws for Windows.  One thing I&#8217;ve noticed is that information doesn&#8217;t read correctly when in forms mode, (I.E., text either gets sepearated after a couple of characters onto another line, or just doesn&#8217;t read at all, as seems to be the case with this form, so sorry if there are misspellings.  Also, the visual editor is completely inaccessible, so that option is out, which I&#8217;m finally noticing the loss of since Jaws has now added a copy as-is feature which allows for the copying of formatting, links, ETC. from web pages in to html-aware documents such as email, Word documents and spread sheets.  To get around this, I use the code editor, and will try to remember to compose posts in a text editor so that I can correct spelling and things like that. But all and all, I think WordPress is the most accessible blogging platform around.  I&#8217;ve been using it on my own server since 2005 and am glad I made the switch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Catherine Turner</title>
		<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-682470</link>
		<dc:creator>Catherine Turner</dc:creator>
		<pubDate>Tue, 30 Oct 2007 12:36:27 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-682470</guid>
		<description>I'm visually impaired and use JAWS screen reading software.  So far on the whole I've found blogs pretty accessible for me - I think this is because at the moment they seem to be largely text based.  That's not to say websites have to be text based to be screen reader accessible but if they are it automatically gets rid of some of the problems.  A problem I recently discovered as a blogger on Wordpress though is the requirement to drag and drop items when you want to customise your sidebar.  This is inaccessible for me and I had to get a friend to do it and I don't want to have to do that again.</description>
		<content:encoded><![CDATA[<p>I&#8217;m visually impaired and use JAWS screen reading software.  So far on the whole I&#8217;ve found blogs pretty accessible for me - I think this is because at the moment they seem to be largely text based.  That&#8217;s not to say websites have to be text based to be screen reader accessible but if they are it automatically gets rid of some of the problems.  A problem I recently discovered as a blogger on WordPress though is the requirement to drag and drop items when you want to customise your sidebar.  This is inaccessible for me and I had to get a friend to do it and I don&#8217;t want to have to do that again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why Search Engine Optimization (SEO) is Still Important &#171; Lorelle on WordPress</title>
		<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-482616</link>
		<dc:creator>Why Search Engine Optimization (SEO) is Still Important &#171; Lorelle on WordPress</dc:creator>
		<pubDate>Tue, 07 Aug 2007 08:19:51 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-482616</guid>
		<description>[...] will be highly accessible to all Web browsers, on all platforms, with all screen resolutions - even people with disabilities (like the blind using screen [...]</description>
		<content:encoded><![CDATA[<p>[...] will be highly accessible to all Web browsers, on all platforms, with all screen resolutions - even people with disabilities (like the blind using screen [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: naomi dagen bloom</title>
		<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-298516</link>
		<dc:creator>naomi dagen bloom</dc:creator>
		<pubDate>Thu, 24 May 2007 21:24:22 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-298516</guid>
		<description>encouraged more than once by O'Folks (previous commenter) to check this site out, i first need to say that my disability is minor--age plus the digital divide.  the latter means those of us who only began to use computers late in life.

my post today at www.alittleredhen.com is the second about what some blog services are doing to impede true interaction among bloggers.

wish Type Pad had someone like you on its case!  yours, naomi</description>
		<content:encoded><![CDATA[<p>encouraged more than once by O&#8217;Folks (previous commenter) to check this site out, i first need to say that my disability is minor&#8211;age plus the digital divide.  the latter means those of us who only began to use computers late in life.</p>
<p>my post today at <a href="http://www.alittleredhen.com" rel="nofollow">http://www.alittleredhen.com</a> is the second about what some blog services are doing to impede true interaction among bloggers.</p>
<p>wish Type Pad had someone like you on its case!  yours, naomi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle VanFossen</title>
		<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-275826</link>
		<dc:creator>Lorelle VanFossen</dc:creator>
		<pubDate>Mon, 14 May 2007 03:24:35 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-275826</guid>
		<description>Excellent information. I hadn't thought about captions for podcasts, but transcripts are a definite help. Thanks for your input on this. It's such a critical, fairly weakly explored area of web development with more facts than usable information.

I wish we'd had more time to chat at the conference. Wasn't that amazing! I'm sure, having worked with translators before, that they had fun with the new blogging jargon for you. ;-)</description>
		<content:encoded><![CDATA[<p>Excellent information. I hadn&#8217;t thought about captions for podcasts, but transcripts are a definite help. Thanks for your input on this. It&#8217;s such a critical, fairly weakly explored area of web development with more facts than usable information.</p>
<p>I wish we&#8217;d had more time to chat at the conference. Wasn&#8217;t that amazing! I&#8217;m sure, having worked with translators before, that they had fun with the new blogging jargon for you. <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen</title>
		<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-275797</link>
		<dc:creator>Karen</dc:creator>
		<pubDate>Mon, 14 May 2007 02:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-275797</guid>
		<description>Hi Lorelle--saw you at SOB and I'm really enjoying your book!

I'm deaf, so podcasts and videos are unaccessible to me unless there's a transcript or captioning provided.  I'm just now exploring some captioning options on the web and learning more myself.</description>
		<content:encoded><![CDATA[<p>Hi Lorelle&#8211;saw you at SOB and I&#8217;m really enjoying your book!</p>
<p>I&#8217;m deaf, so podcasts and videos are unaccessible to me unless there&#8217;s a transcript or captioning provided.  I&#8217;m just now exploring some captioning options on the web and learning more myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle VanFossen</title>
		<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-265013</link>
		<dc:creator>Lorelle VanFossen</dc:creator>
		<pubDate>Tue, 08 May 2007 16:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-265013</guid>
		<description>I agree and will be yelling about this soon. I was hoping it was temporary. Stay tuned and let your voice be heard next week when I lash out against this bad feature.</description>
		<content:encoded><![CDATA[<p>I agree and will be yelling about this soon. I was hoping it was temporary. Stay tuned and let your voice be heard next week when I lash out against this bad feature.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mpb</title>
		<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-264276</link>
		<dc:creator>mpb</dc:creator>
		<pubDate>Tue, 08 May 2007 07:29:46 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-264276</guid>
		<description>I've also listed several reasons at WP Feedback why snap view and similar things should not be default but can't add to what you have said. 

However, I still do NOT appreciate the default separate preview process in writing and editing posts. The older way enabled me to see the results of what I was doing quickly. This was particularly important because I need to add extra bits (like bold or characters) to be sure my readers can tell hotlinks from text (not all themes demarcate this), etc. (I have reported this to feedback.) If all themes gave comments edit buttons, that too would help. I try to regularly review previous posts and to skim each screenful for errors in display (sometimes in text, oops!).</description>
		<content:encoded><![CDATA[<p>I&#8217;ve also listed several reasons at WP Feedback why snap view and similar things should not be default but can&#8217;t add to what you have said. </p>
<p>However, I still do NOT appreciate the default separate preview process in writing and editing posts. The older way enabled me to see the results of what I was doing quickly. This was particularly important because I need to add extra bits (like bold or characters) to be sure my readers can tell hotlinks from text (not all themes demarcate this), etc. (I have reported this to feedback.) If all themes gave comments edit buttons, that too would help. I try to regularly review previous posts and to skim each screenful for errors in display (sometimes in text, oops!).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle VanFossen</title>
		<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-263503</link>
		<dc:creator>Lorelle VanFossen</dc:creator>
		<pubDate>Mon, 07 May 2007 21:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-263503</guid>
		<description>Jo and Erik: This is as I explained in &lt;a href="http://lorelle.wordpress.com/2006/12/29/wordpresscom-please-stop-using-snap-preview/" title="WordPress.com, Please Stop Using Snap Preview" rel="nofollow"&gt;WordPress.com, Please Stop Using Snap Preview&lt;/a&gt; and it continues to annoy me and many others including the disabled. 

I got a phone call yesterday from a friend of mine I'd recently set up Accessibility features on his computer wanting to know what he was doing wrong. He'd had another cataract surgery and it didn't quite work right and now he needed the larger fonts and screen size to see. Forgetting how WordPress.com continues to allow Snap on their blogs without realizing what a nuisance they are, I'd introduced him to WordPress.com bloggers. He kept having things pop up and lose his place and screw things up. It took 20 minutes to calm him down and find out that he wasn't doing anything wrong but Snap was making his viewing experience so miserable. He reads the words with his mouse to keep track of where he is and Snap kept popping up making him lose his place. He now won't visit any WordPress.com blogs except mine because he knows I've turned that annoying feature off. 

It's sad that what could be an interesting feature is foisted upon so many unsuspecting. The opt-out plan is dumb. These things should come with an opt-in option and carry a warning on all blogs using them. Or some distinctive quality like the text link ads with double lines under them - something that says "Don't come near unless you want interference between you and the content."

In my humble opinion. ;-)</description>
		<content:encoded><![CDATA[<p>Jo and Erik: This is as I explained in <a href="http://lorelle.wordpress.com/2006/12/29/wordpresscom-please-stop-using-snap-preview/" title="WordPress.com, Please Stop Using Snap Preview" rel="nofollow">WordPress.com, Please Stop Using Snap Preview</a> and it continues to annoy me and many others including the disabled. </p>
<p>I got a phone call yesterday from a friend of mine I&#8217;d recently set up Accessibility features on his computer wanting to know what he was doing wrong. He&#8217;d had another cataract surgery and it didn&#8217;t quite work right and now he needed the larger fonts and screen size to see. Forgetting how WordPress.com continues to allow Snap on their blogs without realizing what a nuisance they are, I&#8217;d introduced him to WordPress.com bloggers. He kept having things pop up and lose his place and screw things up. It took 20 minutes to calm him down and find out that he wasn&#8217;t doing anything wrong but Snap was making his viewing experience so miserable. He reads the words with his mouse to keep track of where he is and Snap kept popping up making him lose his place. He now won&#8217;t visit any WordPress.com blogs except mine because he knows I&#8217;ve turned that annoying feature off. </p>
<p>It&#8217;s sad that what could be an interesting feature is foisted upon so many unsuspecting. The opt-out plan is dumb. These things should come with an opt-in option and carry a warning on all blogs using them. Or some distinctive quality like the text link ads with double lines under them - something that says &#8220;Don&#8217;t come near unless you want interference between you and the content.&#8221;</p>
<p>In my humble opinion. <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-263432</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Mon, 07 May 2007 20:55:43 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2007/05/05/lets-hear-from-the-disabled/#comment-263432</guid>
		<description>I am a legally blind computer user and blogger. I am completely blind in one eye and vision-limited in the other so using a computer at all is a blessing with today's assistive technologies. I write, design and maintain a couple of WordPress blog sites (www.effectivebiblestudy.com, www.richardcravy.com) and I mostly get by with larger LCD screens running at lower than spec resolutions with large fonts turned on. However, this is not always enough as some WordPress blogs (and other sites) use themes that are still difficult for me to read. Namely, I struggle with sites that use color schemes with little contrast between background and text. For example, pale orange text in the sidebar on a white background. Very tough for me to read. Sure, I could use a screen reader and it would read it fine but I like to read for myself while I still can and I love to enjoy the artistic expression of the designers as well.
So, if I had a suggestion for WordPress designers, be mindful of the amount of contrast that you have between your text and your backgrounds. It will make a big difference.</description>
		<content:encoded><![CDATA[<p>I am a legally blind computer user and blogger. I am completely blind in one eye and vision-limited in the other so using a computer at all is a blessing with today&#8217;s assistive technologies. I write, design and maintain a couple of WordPress blog sites (www.effectivebiblestudy.com, <a href="http://www.richardcravy.com" rel="nofollow">http://www.richardcravy.com</a>) and I mostly get by with larger LCD screens running at lower than spec resolutions with large fonts turned on. However, this is not always enough as some WordPress blogs (and other sites) use themes that are still difficult for me to read. Namely, I struggle with sites that use color schemes with little contrast between background and text. For example, pale orange text in the sidebar on a white background. Very tough for me to read. Sure, I could use a screen reader and it would read it fine but I like to read for myself while I still can and I love to enjoy the artistic expression of the designers as well.<br />
So, if I had a suggestion for WordPress designers, be mindful of the amount of contrast that you have between your text and your backgrounds. It will make a big difference.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
