<?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: Comic Update: Squirrel In The Dark</title>
	<atom:link href="http://cssquirrel.com/2009/08/31/comic-update-squirrel-in-the-dark/feed/" rel="self" type="application/rss+xml" />
	<link>http://cssquirrel.com/blog/2009/08/31/comic-update-squirrel-in-the-dark/</link>
	<description>opinions and news on web design</description>
	<lastBuildDate>Thu, 17 May 2012 05:41:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Erik Vorhes</title>
		<link>http://cssquirrel.com/blog/2009/08/31/comic-update-squirrel-in-the-dark/comment-page-1/#comment-26926</link>
		<dc:creator>Erik Vorhes</dc:creator>
		<pubDate>Thu, 03 Sep 2009 16:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=420#comment-26926</guid>
		<description>One thing to look into for the JavaScript stuff (since some assistive technologies operate without disabling it) would be some of the attributes in the &lt;a href=&quot;http://www.w3.org/WAI/intro/aria&quot; rel=&quot;nofollow&quot;&gt;WAI-ARIA specification&lt;/a&gt;. (Sure, it means that pre-HTML5 code won&#039;t validate, unless you&#039;re using XHTML 1.1, but I&#039;ll take accessibility over validation any day.)

The ARIA spec can be a bit intimidating, but there&#039;s some decent stuff out there to help you through, including &lt;a href=&quot;http://dev.opera.com/articles/view/introduction-to-wai-aria/&quot; rel=&quot;nofollow&quot;&gt;Gez Lemon&#039;s introduction&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>One thing to look into for the JavaScript stuff (since some assistive technologies operate without disabling it) would be some of the attributes in the <a href="http://www.w3.org/WAI/intro/aria" rel="nofollow">WAI-ARIA specification</a>. (Sure, it means that pre-HTML5 code won&#8217;t validate, unless you&#8217;re using XHTML 1.1, but I&#8217;ll take accessibility over validation any day.)</p>
<p>The ARIA spec can be a bit intimidating, but there&#8217;s some decent stuff out there to help you through, including <a href="http://dev.opera.com/articles/view/introduction-to-wai-aria/" rel="nofollow">Gez Lemon&#8217;s introduction</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rhyaniwyn</title>
		<link>http://cssquirrel.com/blog/2009/08/31/comic-update-squirrel-in-the-dark/comment-page-1/#comment-26912</link>
		<dc:creator>Rhyaniwyn</dc:creator>
		<pubDate>Tue, 01 Sep 2009 15:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=420#comment-26912</guid>
		<description>Well, sometimes I don&#039;t think you can make &quot;it&quot; work for everyone. ;-) But hopefully you can make it degrade and provide alternatives for everyone.  How do you alert a blind user of an ajax dialog?  I haven&#039;t ever used a screen reader to be sure, but if you &lt;a href=&quot;login.html&quot; id=&quot;login&quot;&gt; where #login hooks to the javascript which loads login.html in an ajax dialog, but without javascript it just goes straight to login... I hope that would work fine.

Like you, I&#039;ve always meant to do more.  I use the techniques I know of, but I also know there is a lot more to it and I always intend to delve deeper.  But it always gets put off in favor of something else, even though it shouldn&#039;t.

What good is my alt text if it&#039;s poorly written?  What&#039;s the best way to describe the image, really?  And having never used a screen reader myself to experience it, how can I be sure what I&#039;m doing really works?

I&#039;ve delayed investigating the most fundamental aspects -- where do I find assistive software for testing?  Are there any tutorials for writing good alternative text?  Only after simulating the experience and assuring my content itself is accessible can I really begin to think critically about the techniques to deliver content accessibly...</description>
		<content:encoded><![CDATA[<p>Well, sometimes I don&#8217;t think you can make &#8220;it&#8221; work for everyone. ;-) But hopefully you can make it degrade and provide alternatives for everyone.  How do you alert a blind user of an ajax dialog?  I haven&#8217;t ever used a screen reader to be sure, but if you &lt;a href=&#8221;login.html&#8221; id=&#8221;login&#8221;&gt; where #login hooks to the javascript which loads login.html in an ajax dialog, but without javascript it just goes straight to login&#8230; I hope that would work fine.</p>
<p>Like you, I&#8217;ve always meant to do more.  I use the techniques I know of, but I also know there is a lot more to it and I always intend to delve deeper.  But it always gets put off in favor of something else, even though it shouldn&#8217;t.</p>
<p>What good is my alt text if it&#8217;s poorly written?  What&#8217;s the best way to describe the image, really?  And having never used a screen reader myself to experience it, how can I be sure what I&#8217;m doing really works?</p>
<p>I&#8217;ve delayed investigating the most fundamental aspects &#8212; where do I find assistive software for testing?  Are there any tutorials for writing good alternative text?  Only after simulating the experience and assuring my content itself is accessible can I really begin to think critically about the techniques to deliver content accessibly&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Foliot</title>
		<link>http://cssquirrel.com/blog/2009/08/31/comic-update-squirrel-in-the-dark/comment-page-1/#comment-26908</link>
		<dc:creator>John Foliot</dc:creator>
		<pubDate>Tue, 01 Sep 2009 05:28:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=420#comment-26908</guid>
		<description>Following along from Matt&#039;s comment, Marco Zehe posted a superb tutorial on using NVDA and Firefox to test your site for accessibility.  Marco is one of the great developers working within the Mozilla Foundation enhancing the accessibility of that browser. Read his post at: http://www.marcozehe.de/articles/how-to-use-nvda-and-firefox-to-test-your-web-pages-for-accessibility/

While testing to address the needs of the non-sighted user is a great thing to implement into your QA cycle, don&#039;t forget that there are other types of access barriers that also need to be accounted for. Users with mobility impairments, audio impairments and cognitive impairments all have needs that transcend simple &quot;alt text for images&quot;. 

If in doubt, developers should not hesitate to pose questions to any number of on-line fora where old dogs like me hang out: http://www.webaim.org has a great mailing list, as does the W3C&#039;s WAI http://w3c.org/wai.  The UK&#039;s Guild of Accessible Web Developers (GAWDS - http://www.gawds.org/ ) has an active mailing list as well as other useful resources, and Accessify http://accessify.com/ features a number of useful developer tools and a great forum. Finally, on-line educational resources include both the WaSP Interact http://interact.webstandards.org/ and Opera&#039;s Web Standards Curriculum http://www.opera.com/company/education/curriculum/ providing developers with potential solutions to improve accessibility of their sites.

Thanks Kyle for &quot;shedding some light&quot; on an important topic.</description>
		<content:encoded><![CDATA[<p>Following along from Matt&#8217;s comment, Marco Zehe posted a superb tutorial on using NVDA and Firefox to test your site for accessibility.  Marco is one of the great developers working within the Mozilla Foundation enhancing the accessibility of that browser. Read his post at: <a href="http://www.marcozehe.de/articles/how-to-use-nvda-and-firefox-to-test-your-web-pages-for-accessibility/" rel="nofollow">http://www.marcozehe.de/articles/how-to-use-nvda-and-firefox-to-test-your-web-pages-for-accessibility/</a></p>
<p>While testing to address the needs of the non-sighted user is a great thing to implement into your QA cycle, don&#8217;t forget that there are other types of access barriers that also need to be accounted for. Users with mobility impairments, audio impairments and cognitive impairments all have needs that transcend simple &#8220;alt text for images&#8221;. </p>
<p>If in doubt, developers should not hesitate to pose questions to any number of on-line fora where old dogs like me hang out: <a href="http://www.webaim.org" rel="nofollow">http://www.webaim.org</a> has a great mailing list, as does the W3C&#8217;s WAI <a href="http://w3c.org/wai" rel="nofollow">http://w3c.org/wai</a>.  The UK&#8217;s Guild of Accessible Web Developers (GAWDS &#8211; <a href="http://www.gawds.org/" rel="nofollow">http://www.gawds.org/</a> ) has an active mailing list as well as other useful resources, and Accessify <a href="http://accessify.com/" rel="nofollow">http://accessify.com/</a> features a number of useful developer tools and a great forum. Finally, on-line educational resources include both the WaSP Interact <a href="http://interact.webstandards.org/" rel="nofollow">http://interact.webstandards.org/</a> and Opera&#8217;s Web Standards Curriculum <a href="http://www.opera.com/company/education/curriculum/" rel="nofollow">http://www.opera.com/company/education/curriculum/</a> providing developers with potential solutions to improve accessibility of their sites.</p>
<p>Thanks Kyle for &#8220;shedding some light&#8221; on an important topic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mia</title>
		<link>http://cssquirrel.com/blog/2009/08/31/comic-update-squirrel-in-the-dark/comment-page-1/#comment-26902</link>
		<dc:creator>Mia</dc:creator>
		<pubDate>Mon, 31 Aug 2009 22:34:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=420#comment-26902</guid>
		<description>A friend of mine does a webcomic with pretty good alternative text. (At least, this blind person thinks so.)
http://braincomics.net/?comic=197

It appears that the platform she&#039;s using even supports the provision of alternative text, since there&#039;s a show/hide link for it there.

More webcomics need alternative text!</description>
		<content:encoded><![CDATA[<p>A friend of mine does a webcomic with pretty good alternative text. (At least, this blind person thinks so.)<br />
<a href="http://braincomics.net/?comic=197" rel="nofollow">http://braincomics.net/?comic=197</a></p>
<p>It appears that the platform she&#8217;s using even supports the provision of alternative text, since there&#8217;s a show/hide link for it there.</p>
<p>More webcomics need alternative text!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle Weems</title>
		<link>http://cssquirrel.com/blog/2009/08/31/comic-update-squirrel-in-the-dark/comment-page-1/#comment-26901</link>
		<dc:creator>Kyle Weems</dc:creator>
		<pubDate>Mon, 31 Aug 2009 21:33:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=420#comment-26901</guid>
		<description>@Pat-Trip Thank you for your feedback, it helped push me to get back to this topic.

I gather, then, that you&#039;ve never been able to access the content of any of the comic strips. In your opinion, is some sort of summary that&#039;s presented in a format like a movie script a sensible way to make it accessible for blind visitors?</description>
		<content:encoded><![CDATA[<p>@Pat-Trip Thank you for your feedback, it helped push me to get back to this topic.</p>
<p>I gather, then, that you&#8217;ve never been able to access the content of any of the comic strips. In your opinion, is some sort of summary that&#8217;s presented in a format like a movie script a sensible way to make it accessible for blind visitors?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pat-Trip Dyspenzer</title>
		<link>http://cssquirrel.com/blog/2009/08/31/comic-update-squirrel-in-the-dark/comment-page-1/#comment-26899</link>
		<dc:creator>Pat-Trip Dyspenzer</dc:creator>
		<pubDate>Mon, 31 Aug 2009 21:05:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=420#comment-26899</guid>
		<description>Thanks for getting into this topic. Narrator is an exercise in pain, though. ... Blind people have been searching for good descriptions of comics for a long time. At least this blind ppl haz. ... In closing, YAAY FOR SQUIRRELS!</description>
		<content:encoded><![CDATA[<p>Thanks for getting into this topic. Narrator is an exercise in pain, though. &#8230; Blind people have been searching for good descriptions of comics for a long time. At least this blind ppl haz. &#8230; In closing, YAAY FOR SQUIRRELS!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt May</title>
		<link>http://cssquirrel.com/blog/2009/08/31/comic-update-squirrel-in-the-dark/comment-page-1/#comment-26898</link>
		<dc:creator>Matt May</dc:creator>
		<pubDate>Mon, 31 Aug 2009 20:08:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=420#comment-26898</guid>
		<description>Working without the monitor is a worthwhile experiment, though I wouldn&#039;t recommend Narrator to my worst enemy. :) If anyone else wants to try it with free software, I would point them to http://www.nvda-project.org/ .</description>
		<content:encoded><![CDATA[<p>Working without the monitor is a worthwhile experiment, though I wouldn&#8217;t recommend Narrator to my worst enemy. :) If anyone else wants to try it with free software, I would point them to <a href="http://www.nvda-project.org/" rel="nofollow">http://www.nvda-project.org/</a> .</p>
]]></content:encoded>
	</item>
</channel>
</rss>

