<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>xBlog: The visual thinking weblog &#187; Accessibility</title>
	<atom:link href="http://www.xplane.com/xblog/category/accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xplane.com/xblog</link>
	<description>ISSN 1543-7477. Published by XPLANE since 1999.</description>
	<lastBuildDate>Sun, 14 Mar 2010 14:16:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The Design State</title>
		<link>http://www.xplane.com/xblog/2008/11/12/the-design-state/</link>
		<comments>http://www.xplane.com/xblog/2008/11/12/the-design-state/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 21:07:00 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Web design]]></category>

		<guid isPermaLink="false">http://www.xplane.com/xblog/2008/11/12/the-design-state/</guid>
		<description><![CDATA[http://thedesignstate.com/]]></description>
			<content:encoded><![CDATA[<p>&#8220;Design State is a weblog about government web design and its attendant subtopics: accessibility, usability, and web standards. In addition to these nuts and bolts, Design State will also focus on higher level issues and project challenges that affect government and public-sector web design.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xplane.com/xblog/2008/11/12/the-design-state/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sim Daltonism</title>
		<link>http://www.xplane.com/xblog/2007/10/23/sim-daltonism/</link>
		<comments>http://www.xplane.com/xblog/2007/10/23/sim-daltonism/#comments</comments>
		<pubDate>Tue, 23 Oct 2007 14:19:38 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Apple/Macintosh]]></category>
		<category><![CDATA[Color]]></category>
		<category><![CDATA[Graphic design]]></category>
		<category><![CDATA[Software/Hardware]]></category>
		<category><![CDATA[Web design]]></category>

		<guid isPermaLink="false">http://www.xplane.com/xblog/2007/10/23/sim-daltonism/</guid>
		<description><![CDATA[http://michelf.com/projects/sim-daltonism/]]></description>
			<content:encoded><![CDATA[<p>&#8220;Sim Daltonism is a color blindness simulator for Mac OS X. It filters in real-time the area around the mouse pointer and displays the result â€” as seen by a color blind person â€” in a floating palette.</p>
<p>Since there are many types of color blindness, Sim Daltonism allow you to choose the one you want to see.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xplane.com/xblog/2007/10/23/sim-daltonism/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is Ajax accessible? At all?</title>
		<link>http://www.xplane.com/xblog/2006/05/11/is-ajax-accessible-at-all/</link>
		<comments>http://www.xplane.com/xblog/2006/05/11/is-ajax-accessible-at-all/#comments</comments>
		<pubDate>Thu, 11 May 2006 14:21:03 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://xplane.dreamhosters.com/xblog/?p=5417</guid>
		<description><![CDATA[http://joeclark.org/ice/iceweb2006-notes.html]]></description>
			<content:encoded><![CDATA[<p>&#8220;In these notes, I summarize my presentation of original research and testing of an Ajax application (Basecamp) with users of screen readers and other adaptive technologies. Here&#8217;s my working definition of Ajax: The use of scripting to cause portions of a page to refresh without reloading the entire page. That usually happens after the user does something, but it can also happen automatically.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xplane.com/xblog/2006/05/11/is-ajax-accessible-at-all/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessiblity for the Masses</title>
		<link>http://www.xplane.com/xblog/2006/04/04/accessiblity-for-the-masses/</link>
		<comments>http://www.xplane.com/xblog/2006/04/04/accessiblity-for-the-masses/#comments</comments>
		<pubDate>Tue, 04 Apr 2006 14:56:06 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://xplane.dreamhosters.com/xblog/?p=5370</guid>
		<description><![CDATA[http://www.garrettdimon.com/archives/accessiblity-for-the-masses]]></description>
			<content:encoded><![CDATA[<p>&#8220;I was recently reminded while working on our panel for SXSW that accessibility isn&#8217;t just about screen readers, markup guidelines, or alt tags. Unfortunately, that&#8217;s about as far as most of us ever get with accessibility. It&#8217;s good that most of us are making an effort, but it&#8217;s time to start consistently thinking bigger.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xplane.com/xblog/2006/04/04/accessiblity-for-the-masses/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Accessibility Hat Trick: Getting Abbreviations Right</title>
		<link>http://www.xplane.com/xblog/2006/02/06/the-accessibility-hat-trick-getting-abbreviations-right/</link>
		<comments>http://www.xplane.com/xblog/2006/02/06/the-accessibility-hat-trick-getting-abbreviations-right/#comments</comments>
		<pubDate>Mon, 06 Feb 2006 15:22:05 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://xplane.dreamhosters.com/xblog/?p=5300</guid>
		<description><![CDATA[http://www.alistapart.com/articles/hattrick]]></description>
			<content:encoded><![CDATA[<p>&#8220;AAA-level compliance is the ideal of accessibility, the bonus-round of accessible design: AAA-level compliant pages meet the needs of every group of users. AAA is achievable, but requires preparation and forethought. To create a forward-looking, fully AAA-compliant site, we need to execute a sort of hat trick: XHTML 1.0 and 2.0-compliant markup, a generous breadth of backwards compatibility, and real universal accessibility.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xplane.com/xblog/2006/02/06/the-accessibility-hat-trick-getting-abbreviations-right/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>I don&#8217;t care about accessibility</title>
		<link>http://www.xplane.com/xblog/2004/03/19/i-dont-care-about-accessibility/</link>
		<comments>http://www.xplane.com/xblog/2004/03/19/i-dont-care-about-accessibility/#comments</comments>
		<pubDate>Fri, 19 Mar 2004 16:16:07 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://xplane.dreamhosters.com/xblog/?p=4365</guid>
		<description><![CDATA[http://www.veen.com/jeff/archives/000503.html]]></description>
			<content:encoded><![CDATA[<p>&#8220;These are the speaking notes I used during the &#8216;Accessibility is for everyone!&#8217; panel discussion at South by SouthWest earlier this week [March 2004]. I came here to be on this panel to tell y&#8217;all that I don&#8217;t care about accessibility. Don&#8217;t care. Not an issue. Hardly ever comes up. Here&#8217;s my big secret for you today. When you design for the Web ó that is, when you design exclusively and specifically for this medium ó when you do that natively, so many of the things we consider problems just start to fall away.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xplane.com/xblog/2004/03/19/i-dont-care-about-accessibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessible Website Menu</title>
		<link>http://www.xplane.com/xblog/2004/01/29/accessible-website-menu/</link>
		<comments>http://www.xplane.com/xblog/2004/01/29/accessible-website-menu/#comments</comments>
		<pubDate>Thu, 29 Jan 2004 20:18:35 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://xplane.dreamhosters.com/xblog/?p=4257</guid>
		<description><![CDATA[http://af.brothercake.com/dropdown/]]></description>
			<content:encoded><![CDATA[<p>&#8220;UDM is a lightweight and accessible javascript menu, which provides useable content to all browsers&#8212;- including screenreaders, search-engines and text-only browsers. But accessibility shouldn&#8217;t mean compromise, and so UDM has a sophisticated range of design and usability controls, many of which are unique to this script. The navigation bar is simply a list of links. You can use Tab for navigation, and Enter to activate links, or whatever keystrokes you would normally use. To the best of our knowledge, Ultimate Drop Down Menu is the ONLY fully-featured and accessible DHTML menu in the world!&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xplane.com/xblog/2004/01/29/accessible-website-menu/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>An Interview with Joe Clark</title>
		<link>http://www.xplane.com/xblog/2003/11/06/an-interview-with-joe-clark/</link>
		<comments>http://www.xplane.com/xblog/2003/11/06/an-interview-with-joe-clark/#comments</comments>
		<pubDate>Thu, 06 Nov 2003 08:00:00 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://xplane.dreamhosters.com/xblog/?p=38</guid>
		<description><![CDATA[http://www.digital-web.com/interviews/interview_2003-10.shtml]]></description>
			<content:encoded><![CDATA[<p>&#8220;Digital Web: &#8216;Accessibility&#8217; is now part of the Web development community&#8217;s lingua franca. However, it&#8217;s often used as shorthand to mean making a site function for blind people. How would you define it, in the Web development context? Joe Clark: I use the same definition of accessibility everywhere: Accommodating features a person cannot change or cannot change easily.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xplane.com/xblog/2003/11/06/an-interview-with-joe-clark/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Joe Clark&#8217;s Answers &#8212; In Valid XHTML</title>
		<link>http://www.xplane.com/xblog/2002/12/16/joe-clarks-answers-in-valid-xhtml/</link>
		<comments>http://www.xplane.com/xblog/2002/12/16/joe-clarks-answers-in-valid-xhtml/#comments</comments>
		<pubDate>Mon, 16 Dec 2002 08:00:00 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://xplane.dreamhosters.com/xblog/?p=39</guid>
		<description><![CDATA[http://interviews.slashdot.org/article.pl?sid=02/12/09/1446221]]></description>
			<content:encoded><![CDATA[<p>&#8220;We sent 10 of your questions to usability guy Joe Clark, and he took it upon himself to go a bit beyond simply answering them. In his reply he said, &#8216;Answers attached in a valid XHTML file. I would suggest at least retaining the id attributes. I copy-edited all the questions, but the words are all the same; they are now merely spelled and capitalized correctly. I think all the links work.&#8217; Whatever. We left Joe&#8217;s formatting intact. It&#8217;s a little different from our usual style, but variety is the spice of Slashdot.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xplane.com/xblog/2002/12/16/joe-clarks-answers-in-valid-xhtml/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building Accessible Websites</title>
		<link>http://www.xplane.com/xblog/2002/10/17/building-accessible-websites/</link>
		<comments>http://www.xplane.com/xblog/2002/10/17/building-accessible-websites/#comments</comments>
		<pubDate>Thu, 17 Oct 2002 08:00:00 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://xplane.dreamhosters.com/xblog/?p=40</guid>
		<description><![CDATA[http://joeclark.org/book/]]></description>
			<content:encoded><![CDATA[<p>&#8220;The purpose of the book? Teaching developers, of any sophistication and working with any kind of budget (including none), how to improve the accessibility of online media. I have come up with a new approach to the issue, which has never been documented properly in the past.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xplane.com/xblog/2002/10/17/building-accessible-websites/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
