<?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: Best Practices: Writing for Accessibility</title>
	<atom:link href="http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<lastBuildDate>Tue, 07 Feb 2012 10:51:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Creative Blogging</title>
		<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/comment-page-1/#comment-28659</link>
		<dc:creator>Creative Blogging</dc:creator>
		<pubDate>Mon, 27 Oct 2008 17:53:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=241#comment-28659</guid>
		<description>Perhaps you should also have mentioned the font size changing option. It can really enhance the way a reader perceives text on screen. Just as you see in news websites.</description>
		<content:encoded><![CDATA[<p>Perhaps you should also have mentioned the font size changing option. It can really enhance the way a reader perceives text on screen. Just as you see in news&nbsp;websites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Sturn</title>
		<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/comment-page-1/#comment-24170</link>
		<dc:creator>Simon Sturn</dc:creator>
		<pubDate>Fri, 27 Jun 2008 12:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=241#comment-24170</guid>
		<description>I think that usability is most important thing, and you are right, even the punctuation is absolutely correct it still can confuse some readers. The usage of speech avatars is good decision of the problem. But I don&#039;t like the sites which sounds is on when load. It&#039;s very irritating.</description>
		<content:encoded><![CDATA[<p>I think that usability is most important thing, and you are right, even the punctuation is absolutely correct it still can confuse some readers. The usage of speech avatars is good decision of the problem. But I don&#8217;t like the sites which sounds is on when load. It&#8217;s very&nbsp;irritating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: [no name provided]</title>
		<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/comment-page-1/#comment-24058</link>
		<dc:creator>[no name provided]</dc:creator>
		<pubDate>Sat, 21 Jun 2008 15:02:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=241#comment-24058</guid>
		<description>There are many ways to write a good statement in order to make it clear and understanding. Use more action words that make your writing more interesting.</description>
		<content:encoded><![CDATA[<p>There are many ways to write a good statement in order to make it clear and understanding. Use more action words that make your writing more&nbsp;interesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/comment-page-1/#comment-24057</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Fri, 20 Jun 2008 14:17:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=241#comment-24057</guid>
		<description>Yes, the top-down content authoring model can work when applied at every level of granularity: a general introduction to start off the document, a leading sentence which clearly defines the problem in each section of the document, etc. 

Organizing your document in such a manner that it&#039;s crystal clear at any point what subject matter is being addressed is certainly important!</description>
		<content:encoded><![CDATA[<p>Yes, the top-down content authoring model can work when applied at every level of granularity: a general introduction to start off the document, a leading sentence which clearly defines the problem in each section of the document,&nbsp;etc. </p>
<p>Organizing your document in such a manner that it&#8217;s crystal clear at any point what subject matter is being addressed is certainly&nbsp;important!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrea Hill</title>
		<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/comment-page-1/#comment-24056</link>
		<dc:creator>Andrea Hill</dc:creator>
		<pubDate>Fri, 20 Jun 2008 13:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=241#comment-24056</guid>
		<description>Great article, Joe. I think this is an area most people ignore when it comes to accessibility: the actual content. 

When I worked at LexisNexis, we really endeavoured to introduce accessibility best practices through the entire design/development process, and thankfully the content was accounted for as well. One major change we had was the order of the most relevant bits of information. If you are listening to an entire list of elements, you want to hear the most salient information first, so you can skip to the next element if it&#039;s not what you are looking for.</description>
		<content:encoded><![CDATA[<p>Great article, Joe. I think this is an area most people ignore when it comes to accessibility: the actual&nbsp;content. </p>
<p>When I worked at LexisNexis, we really endeavoured to introduce accessibility best practices through the entire design/development process, and thankfully the content was accounted for as well. One major change we had was the order of the most relevant bits of information. If you are listening to an entire list of elements, you want to hear the most salient information first, so you can skip to the next element if it&#8217;s not what you are looking&nbsp;for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zohai</title>
		<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/comment-page-1/#comment-23978</link>
		<dc:creator>zohai</dc:creator>
		<pubDate>Wed, 21 May 2008 05:47:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=241#comment-23978</guid>
		<description>Captcha is needed to remove all those pesky spams =/ I even had to remove comments altogether at one point due to the amount of spams I have.</description>
		<content:encoded><![CDATA[<p>Captcha is needed to remove all those pesky spams =/ I even had to remove comments altogether at one point due to the amount of spams I&nbsp;have.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/comment-page-1/#comment-23965</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Sat, 10 May 2008 00:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=241#comment-23965</guid>
		<description>Using any CAPTCHA is such a challenge --- I definitely like your page of them! I really only resorted to this one out of desperation due to comment spam. It&#039;s frustrating; but I finally just had to do it. 

Thanks for those articles. I&#039;m looking forward to reading them (and then returning to this conversation, as well!)</description>
		<content:encoded><![CDATA[<p>Using any <abbr title="Completely Automated Public Turing test to tell Computers and Humans Apart">CAPTCHA</abbr> is such a challenge&thinsp;&#8212;&thinsp;- I definitely like your page of them! I really only resorted to this one out of desperation due to comment spam. It&#8217;s frustrating; but I finally just had to do&nbsp;it. </p>
<p>Thanks for those articles. I&#8217;m looking forward to reading them (and then returning to this conversation, as&nbsp;well!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tedd</title>
		<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/comment-page-1/#comment-23964</link>
		<dc:creator>tedd</dc:creator>
		<pubDate>Fri, 09 May 2008 15:52:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=241#comment-23964</guid>
		<description>The analogy I used simply exhibited a change in behavior based upon the limitations of the medium. For example, I should write less complex because most screen readers have problems with complexity. Similarly IE exhibits the most problems with standards, so I should use that as my browser. In both cases, if the user makes a decision not to dumb-down to the limitations, but rather use their own judgement, then they promote change for the greater good. That was my point. But granted, I probably could have made my point better by using a different analogy.

As to the Alzheimer’s evidence -- the original study was done by a nun and published in Time May 14, 2001.

Here&#039;s one article:

http://www.time.com/time/magazine/article/0,9171,999867-1,00.html

And here&#039;s some follow up.

http://www.msnbc.msn.com/id/22361498/

I am positive there are more. The article I originally read in 2001 was different than above. How&#039;s that for memory?

Cheers,

tedd

PS: I like your CAPTCHA -- here&#039;s a few of my own:

http://webbytedd.com/aa/assorted-captcha/</description>
		<content:encoded><![CDATA[<p>The analogy I used simply exhibited a change in behavior based upon the limitations of the medium. For example, I should write less complex because most screen readers have problems with complexity. Similarly <abbr title="Internet Explorer">IE</abbr> exhibits the most problems with standards, so I should use that as my browser. In both cases, if the user makes a decision not to dumb-down to the limitations, but rather use their own judgement, then they promote change for the greater good. That was my point. But granted, I probably could have made my point better by using a different&nbsp;analogy.</p>
<p>As to the Alzheimer’s evidence&thinsp;&#8212;&thinsp;the original study was done by a nun and published in Time May 14,&nbsp;2001.</p>
<p>Here&#8217;s one&nbsp;article:</p>
<p><a href="http://www.time.com/time/magazine/article/0,9171,999867-1,00.html" rel="nofollow">http://www.time.com/time/magazine/article/0,9171,999867-1,00.html</a></p>
<p>And here&#8217;s some follow&nbsp;up.</p>
<p><a href="http://www.msnbc.msn.com/id/22361498/" rel="nofollow">http://www.msnbc.msn.com/id/22361498/</a></p>
<p>I am positive there are more. The article I originally read in 2001 was different than above. How&#8217;s that for&nbsp;memory?</p>
<p>Cheers,</p>
<p>tedd</p>
<p>PS: I like your <abbr title="Completely Automated Public Turing test to tell Computers and Humans Apart">CAPTCHA</abbr>&thinsp;&#8212;&thinsp;here&#8217;s a few of my&nbsp;own:</p>
<p><a href="http://webbytedd.com/aa/assorted-captcha/" rel="nofollow">http://webbytedd.com/aa/assorted-captcha/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/comment-page-1/#comment-23963</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Fri, 09 May 2008 14:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=241#comment-23963</guid>
		<description>I don&#039;t want to tell anybody how to write --- but I do want to point out the consequences of that writing style. 

And please, do make a point of distinguishing between &quot;complex sentences&quot; and &quot;overly complex sentences.&quot; If you write &lt;em&gt;well&lt;/em&gt;, than this may not be an issue --- but there are a lot of people contributing web content who don&#039;t!

&lt;blockquote&gt;
Telling me to change the way I write because of limitations in JAWS is like telling me to use IE because more people use it. If we were all to do that, then M$ would not change their ways nor would we have better browsers like Safari and FireFox.
&lt;/blockquote&gt;

I don&#039;t think that&#039;s a valid analogy --- first, because I&#039;m not describing limitations in JAWS: I&#039;m describing limitations in screen readers. No screen reader fully effects pronunciation of sentence emphasis or punctuation. Second, because those aren&#039;t correlative: the first part is changing a second party&#039;s user agent, the second is changing your own. 

&lt;blockquote&gt;
Besides, there’s evidence that suggest people who write shorter sentences have a higher chance of developing Alzheimer’s than people who write more complex sentences — interesting huh?
&lt;/blockquote&gt;

Can you provide a citation for that? I&#039;d be interested in reading about it!

Thanks for your comments!</description>
		<content:encoded><![CDATA[<p>I don&#8217;t want to tell anybody how to write&thinsp;&#8212;&thinsp;- but I do want to point out the consequences of that writing&nbsp;style. </p>
<p>And please, do make a point of distinguishing between &#8220;complex sentences&#8221; and &#8220;overly complex sentences.&#8221; If you write <em>well</em>, than this may not be an issue&thinsp;&#8212;&thinsp;- but there are a lot of people contributing web content who&nbsp;don&#8217;t!</p>
<blockquote><p>
Telling me to change the way I write because of limitations in JAWS is like telling me to use <abbr title="Internet Explorer">IE</abbr> because more people use it. If we were all to do that, then M$ would not change their ways nor would we have better browsers like Safari and&nbsp;FireFox.
</p></blockquote>
<p>I don&#8217;t think that&#8217;s a valid analogy&thinsp;&#8212;&thinsp;- first, because I&#8217;m not describing limitations in JAWS: I&#8217;m describing limitations in screen readers. No screen reader fully effects pronunciation of sentence emphasis or punctuation. Second, because those aren&#8217;t correlative: the first part is changing a second party&#8217;s user agent, the second is changing your&nbsp;own. </p>
<blockquote><p>
Besides, there’s evidence that suggest people who write shorter sentences have a higher chance of developing Alzheimer’s than people who write more complex sentences — interesting&nbsp;huh?
</p></blockquote>
<p>Can you provide a citation for that? I&#8217;d be interested in reading about&nbsp;it!</p>
<p>Thanks for your&nbsp;comments!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tedd</title>
		<link>http://www.joedolson.com/articles/2008/05/best-practices-writing-for-accessibility/comment-page-1/#comment-23962</link>
		<dc:creator>tedd</dc:creator>
		<pubDate>Fri, 09 May 2008 14:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=241#comment-23962</guid>
		<description>I understand your point, but I write to express ideas.

Telling me to change the way I write because of limitations in JAWS is like telling me to use IE because more people use it. If we were all to do that, then M$ would not change their ways nor would we have better browsers like Safari and FireFox.

If there is a problem with JAWS, then competition should change that.

Besides, there&#039;s evidence that suggest people who write shorter sentences have a higher chance of developing Alzheimer&#039;s than people who write more complex sentences -- interesting huh?</description>
		<content:encoded><![CDATA[<p>I understand your point, but I write to express&nbsp;ideas.</p>
<p>Telling me to change the way I write because of limitations in JAWS is like telling me to use <abbr title="Internet Explorer">IE</abbr> because more people use it. If we were all to do that, then M$ would not change their ways nor would we have better browsers like Safari and&nbsp;FireFox.</p>
<p>If there is a problem with JAWS, then competition should change&nbsp;that.</p>
<p>Besides, there&#8217;s evidence that suggest people who write shorter sentences have a higher chance of developing Alzheimer&#8217;s than people who write more complex sentences&thinsp;&#8212;&thinsp;interesting&nbsp;huh?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

