<?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: Keep Going Despite Pain and Challenges</title>
	<atom:link href="http://www.howtocopewithpain.org/blog/248/pain-blindness-book/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.howtocopewithpain.org/blog/248/pain-blindness-book/</link>
	<description></description>
	<lastBuildDate>Sat, 13 Mar 2010 12:43:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: How to Cope with Pain</title>
		<link>http://www.howtocopewithpain.org/blog/248/pain-blindness-book/comment-page-1/#comment-6196</link>
		<dc:creator>How to Cope with Pain</dc:creator>
		<pubDate>Tue, 24 Jun 2008 12:30:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtocopewithpain.org/blog/?p=248#comment-6196</guid>
		<description>Thanks, Phil.  I had read about putting descriptions of pictures, but haven&#039;t known exactly where to do that.  But instead of using that excuse, I should just find out!  Does anyone know how to do this?</description>
		<content:encoded><![CDATA[<p>Thanks, Phil.  I had read about putting descriptions of pictures, but haven&#8217;t known exactly where to do that.  But instead of using that excuse, I should just find out!  Does anyone know how to do this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://www.howtocopewithpain.org/blog/248/pain-blindness-book/comment-page-1/#comment-6195</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Mon, 23 Jun 2008 23:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtocopewithpain.org/blog/?p=248#comment-6195</guid>
		<description>Hi -- Having blind friends has sensitized me to issues of accessibility on web sites, and I see that your contact with Nickie has done the same. However, your blog post violates at least a few principles of accessibility that I think you could fix with a little bit of work. A good resource for this is at this Web site: http://wave.webaim.org/ You can enter the address of a page of your site, and the site returns a list of items -- if there are any! -- where your site could be made more accessible.

The two areas I notice are tags on the photos and tags on the links; as a sighted person, you would see &quot;tooltips&quot; when you hovered on such things. A blind person using a browser would be able to read the tag describing the photo (e.g., &quot;Photograph of Nickie with her service dog&quot;) or the link. 

You may not be able to do anything about the ads that appear on your site, though you could be proactive and urge the agency you deal with to make sure their ads are accessible.</description>
		<content:encoded><![CDATA[<p>Hi &#8212; Having blind friends has sensitized me to issues of accessibility on web sites, and I see that your contact with Nickie has done the same. However, your blog post violates at least a few principles of accessibility that I think you could fix with a little bit of work. A good resource for this is at this Web site: <a href="http://wave.webaim.org/" rel="nofollow">http://wave.webaim.org/</a> You can enter the address of a page of your site, and the site returns a list of items &#8212; if there are any! &#8212; where your site could be made more accessible.</p>
<p>The two areas I notice are tags on the photos and tags on the links; as a sighted person, you would see &#8220;tooltips&#8221; when you hovered on such things. A blind person using a browser would be able to read the tag describing the photo (e.g., &#8220;Photograph of Nickie with her service dog&#8221;) or the link. </p>
<p>You may not be able to do anything about the ads that appear on your site, though you could be proactive and urge the agency you deal with to make sure their ads are accessible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
