<?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>Unrepentant &#187; web accessibility</title>
	<atom:link href="http://john.foliot.ca/category/web-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://john.foliot.ca</link>
	<description>...my perspective - without apology</description>
	<lastBuildDate>Fri, 16 Jul 2010 14:57:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Open Web Camp II</title>
		<link>http://john.foliot.ca/open-web-camp-ii/</link>
		<comments>http://john.foliot.ca/open-web-camp-ii/#comments</comments>
		<pubDate>Fri, 16 Jul 2010 14:57:06 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[HTML5]]></category>
		<category><![CDATA[web accessibility]]></category>

		<guid isPermaLink="false">http://john.foliot.ca/?p=192</guid>
		<description><![CDATA[The idea was simple: put on a free, cool web-event in the Bay Area, and ensure that there were a number of interesting tracks that covered multiple aspects of open web technologies and web development, including accessibility.  But rather than put accessibility on a pedestal or separate it out as something "special" or niche, treat the accessibility tracks as equal 'partners' in the stack - as interesting, exciting and crucial as learning the next CSS3 tricks, or exploring the emergent mobile platform. ]]></description>
		<wfw:commentRss>http://john.foliot.ca/open-web-camp-ii/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>A Letter to the U.S. House of Representatives Committee on the Judiciary</title>
		<link>http://john.foliot.ca/a-letter-to-the-u-s-house-of-representatives-committee-on-the-judiciary/</link>
		<comments>http://john.foliot.ca/a-letter-to-the-u-s-house-of-representatives-committee-on-the-judiciary/#comments</comments>
		<pubDate>Sat, 24 Apr 2010 06:43:31 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[web accessibility]]></category>

		<guid isPermaLink="false">http://john.foliot.ca/?p=168</guid>
		<description><![CDATA[John Conyers, Jr.
Chairman
U.S. House of Representatives Committee on the Judiciary
Washington, DC
Dear Mr. Conyers,
You don&#8217;t know me. However, I feel that at the very least you should know that I&#8217;ve dedicated the last decade of my life working towards making the Internet accessible to everyone. To you, your family and friends, your colleagues and associates &#8211; [...]]]></description>
		<wfw:commentRss>http://john.foliot.ca/a-letter-to-the-u-s-house-of-representatives-committee-on-the-judiciary/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Thoughts on &lt;details&gt; versus @summary</title>
		<link>http://john.foliot.ca/thoughts-on-detail-versus-summary/</link>
		<comments>http://john.foliot.ca/thoughts-on-detail-versus-summary/#comments</comments>
		<pubDate>Thu, 25 Feb 2010 22:09:36 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[HTML5]]></category>
		<category><![CDATA[web accessibility]]></category>

		<guid isPermaLink="false">http://john.foliot.ca/?p=150</guid>
		<description><![CDATA[I originally sent these out as a series of tweets on twitter. It was late at night on the west coast, so likely most were asleep when I pumped them out.  I hope to expand on these further, but for now, my bullet points:

Elements are better than attributes; for semantics, javascript, css
If something needs [...]]]></description>
		<wfw:commentRss>http://john.foliot.ca/thoughts-on-detail-versus-summary/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Standard or Specification?</title>
		<link>http://john.foliot.ca/145/</link>
		<comments>http://john.foliot.ca/145/#comments</comments>
		<pubDate>Mon, 08 Feb 2010 23:41:01 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[HTML5]]></category>
		<category><![CDATA[Rants]]></category>
		<category><![CDATA[web accessibility]]></category>

		<guid isPermaLink="false">http://john.foliot.ca/?p=145</guid>
		<description><![CDATA[Preamble
You skipped over a question I asked in the previous e-mail: If there
is advice in the UAAG spec that you think implementors should follow
here, then the best way we can ensure that it is followed is, IMHO, to
also include it in HTML. Is there something I&#8217;ve omitted that UAAG
recommends of relevance here? If so, what?
Ian [...]]]></description>
		<wfw:commentRss>http://john.foliot.ca/145/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Talismans, Active Listening, and a half-time show</title>
		<link>http://john.foliot.ca/talismans-active-listening-and-a-half-time-show/</link>
		<comments>http://john.foliot.ca/talismans-active-listening-and-a-half-time-show/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 05:44:30 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[HTML5]]></category>
		<category><![CDATA[web accessibility]]></category>

		<guid isPermaLink="false">http://john.foliot.ca/?p=111</guid>
		<description><![CDATA[Talismans
First of all, I would like to suggest that today the @summary debate has digressed to something of a fight over a Talisman.  Maybe that is in part my fault, and if so I will take the blame.  I used that Talisman to force a dialog that has needed to happen for a [...]]]></description>
		<wfw:commentRss>http://john.foliot.ca/talismans-active-listening-and-a-half-time-show/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>The most pressing Accessibility issue in HTML5 today? &lt;video&gt;</title>
		<link>http://john.foliot.ca/the-most-pressing-accessibility-issue-in-html5-today-video/</link>
		<comments>http://john.foliot.ca/the-most-pressing-accessibility-issue-in-html5-today-video/#comments</comments>
		<pubDate>Sun, 26 Jul 2009 22:48:31 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[HTML5]]></category>
		<category><![CDATA[web accessibility]]></category>

		<guid isPermaLink="false">http://john.foliot.ca/?p=97</guid>
		<description><![CDATA[Over a wonderfully authentic Thai dinner the other night with my friend, Opera Web Evangelist  and HTML5 Doctor Bruce Lawson, conversation naturally turned to the outstanding accessibility issues that still need to be addressed in HTML5.  While we both agree that finding a solution for &#60;canvas&#62; is going to be both vexing and [...]]]></description>
		<wfw:commentRss>http://john.foliot.ca/the-most-pressing-accessibility-issue-in-html5-today-video/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Thoughts towards an accessible canvas</title>
		<link>http://john.foliot.ca/thoughts-towards-an-accessible-canvas/</link>
		<comments>http://john.foliot.ca/thoughts-towards-an-accessible-canvas/#comments</comments>
		<pubDate>Tue, 17 Mar 2009 00:59:00 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[HTML5]]></category>
		<category><![CDATA[web accessibility]]></category>

		<guid isPermaLink="false">http://john.foliot.ca/?p=11</guid>
		<description><![CDATA[How can we ensure that the canvas element is at the very least user-friendly to those who may never actually be able to consume the author envisioned content of &#60;canvas>?  I propose a ‘block’ of 5 attributes - 2 mandatory and 3 optional – that constitutes the fallback.]]></description>
		<wfw:commentRss>http://john.foliot.ca/thoughts-towards-an-accessible-canvas/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
