<?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: Progressive enhancements with &#8220;longdesc&#8221;</title>
	<atom:link href="http://idhana.com/2008/08/11/progressive-enhancements-with-longdesc/feed/" rel="self" type="application/rss+xml" />
	<link>http://idhana.com/2008/08/11/progressive-enhancements-with-longdesc/</link>
	<description>Making happy users!</description>
	<lastBuildDate>Tue, 22 Nov 2011 07:12:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Longdesc - Another look &#171; idhana.com</title>
		<link>http://idhana.com/2008/08/11/progressive-enhancements-with-longdesc/comment-page-1/#comment-49</link>
		<dc:creator>Longdesc - Another look &#171; idhana.com</dc:creator>
		<pubDate>Tue, 06 Jan 2009 05:47:27 +0000</pubDate>
		<guid isPermaLink="false">http://idhana.com/2008/08/11/progressive-enhancements-with-longdesc/#comment-49</guid>
		<description>[...] coming up with a quick bit of code yesterday for the longdesc comment that Ruth left, I had another idea. I decided to try approaching the problem using the [...]</description>
		<content:encoded><![CDATA[<p>[...] coming up with a quick bit of code yesterday for the longdesc comment that Ruth left, I had another idea. I decided to try approaching the problem using the [...]
<p><span id="reportcomment_results_div_49"><a href="javascript:void(0);" onclick="reportComment( 49 );" title="Report this comment" rel="nofollow">Report this comment</a></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruth</title>
		<link>http://idhana.com/2008/08/11/progressive-enhancements-with-longdesc/comment-page-1/#comment-18</link>
		<dc:creator>Ruth</dc:creator>
		<pubDate>Tue, 12 Aug 2008 16:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://idhana.com/2008/08/11/progressive-enhancements-with-longdesc/#comment-18</guid>
		<description>Neat idea - that is the kind of thing I was suggesting. Following that original posting, I did a heap more research. The whole issue of long description seems to be/has caused something of a &quot;stir&quot; - particularly the execution of the thing.

I decided, in the end, to use the notion of hidden footnotes - probably along the lines of your original notion.

Back to this example.

It passes the WAVE test by the way... so that is neat. However, for real accessibility purposes, you might need to accommodate an &quot;auto&quot; expanding kind of box area.

While most images don&#039;t in fact need a long description, a basic one would do. Apparently, the whole point of long description is to attempt to describe - as fully as possible - the meaning of an image to an unsighted website visitor.

Long description is usually not there on mouse over - as you then assume the ability to use a mouse... apparently, screen readers pick up on the location of long description and that enables the user to access - somehow. Question then would be - how do they &quot;mouse out&quot;.

Your creation does provide a solution that would resolve one of the main problems of having long descriptions on their own page - that problem being some software actually opens up a whole new window to display them - making the back button redundant and causing concern as to how the viewer gets taken back to the relevant area of the specific page they were on - without having to work through a page again...

I have to say, I am damn impressed with your work here, you are pretty rapid at popping this JQuery/javascript stuff out.</description>
		<content:encoded><![CDATA[<p>Neat idea &#8211; that is the kind of thing I was suggesting. Following that original posting, I did a heap more research. The whole issue of long description seems to be/has caused something of a &#8220;stir&#8221; &#8211; particularly the execution of the thing.</p>
<p>I decided, in the end, to use the notion of hidden footnotes &#8211; probably along the lines of your original notion.</p>
<p>Back to this example.</p>
<p>It passes the WAVE test by the way&#8230; so that is neat. However, for real accessibility purposes, you might need to accommodate an &#8220;auto&#8221; expanding kind of box area.</p>
<p>While most images don&#8217;t in fact need a long description, a basic one would do. Apparently, the whole point of long description is to attempt to describe &#8211; as fully as possible &#8211; the meaning of an image to an unsighted website visitor.</p>
<p>Long description is usually not there on mouse over &#8211; as you then assume the ability to use a mouse&#8230; apparently, screen readers pick up on the location of long description and that enables the user to access &#8211; somehow. Question then would be &#8211; how do they &#8220;mouse out&#8221;.</p>
<p>Your creation does provide a solution that would resolve one of the main problems of having long descriptions on their own page &#8211; that problem being some software actually opens up a whole new window to display them &#8211; making the back button redundant and causing concern as to how the viewer gets taken back to the relevant area of the specific page they were on &#8211; without having to work through a page again&#8230;</p>
<p>I have to say, I am damn impressed with your work here, you are pretty rapid at popping this JQuery/javascript stuff out.
<p><span id="reportcomment_results_div_18"><a href="javascript:void(0);" onclick="reportComment( 18 );" title="Report this comment" rel="nofollow">Report this comment</a></span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

