<?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: Responsibilities in accessibility</title>
	<atom:link href="http://alastairc.ac/2007/05/responsibilities-in-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://alastairc.ac/2007/05/responsibilities-in-accessibility/</link>
	<description>Kything web interactions</description>
	<lastBuildDate>Thu, 12 Jan 2012 09:29:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: sprungmarker &#187; Blog Archive &#187; BLOCKQUOTE-Element und wo kommt das CITE-Element hin?</title>
		<link>http://alastairc.ac/2007/05/responsibilities-in-accessibility/comment-page-1/#comment-25432</link>
		<dc:creator>sprungmarker &#187; Blog Archive &#187; BLOCKQUOTE-Element und wo kommt das CITE-Element hin?</dc:creator>
		<pubDate>Wed, 05 Dec 2007 21:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2007/05/responsibilities-in-accessibility/#comment-25432</guid>
		<description>[...] AlastairC (Beispielseite) [...]</description>
		<content:encoded><![CDATA[<p>[...] AlastairC (Beispielseite) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BLOCKQUOTE-Element und wo kommt das CITE-Element hin? - sprungmarker</title>
		<link>http://alastairc.ac/2007/05/responsibilities-in-accessibility/comment-page-1/#comment-15052</link>
		<dc:creator>BLOCKQUOTE-Element und wo kommt das CITE-Element hin? - sprungmarker</dc:creator>
		<pubDate>Mon, 14 May 2007 20:48:40 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2007/05/responsibilities-in-accessibility/#comment-15052</guid>
		<description>[...] AlastairC (Beispielseite) [...]</description>
		<content:encoded><![CDATA[<p>[...] AlastairC (Beispielseite) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlastairC</title>
		<link>http://alastairc.ac/2007/05/responsibilities-in-accessibility/comment-page-1/#comment-14994</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Sat, 12 May 2007 19:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2007/05/responsibilities-in-accessibility/#comment-14994</guid>
		<description>Hi Andrea, you might find my &lt;a href=&quot;http://www.nomensa.com/resources/articles/accessibility-articles/accessibility-lifecycle.html&quot; rel=&quot;nofollow&quot;&gt;accessibility lifecyle article&lt;/a&gt; better for that purpose (i.e. the developer end of things). The next one is how user-agents can be improved, and the final one will be on tools.</description>
		<content:encoded><![CDATA[<p>Hi Andrea, you might find my <a href="http://www.nomensa.com/resources/articles/accessibility-articles/accessibility-lifecycle.html" rel="nofollow">accessibility lifecyle article</a> better for that purpose (i.e. the developer end of things). The next one is how user-agents can be improved, and the final one will be on tools.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrea Hill</title>
		<link>http://alastairc.ac/2007/05/responsibilities-in-accessibility/comment-page-1/#comment-14964</link>
		<dc:creator>Andrea Hill</dc:creator>
		<pubDate>Fri, 11 May 2007 17:50:41 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2007/05/responsibilities-in-accessibility/#comment-14964</guid>
		<description>I will definitely be &#039;tuning in&#039; for the next few episodes. I just spent the last few days at &quot;&lt;a href=&quot;http://www.knowbility.org/conference/&quot; rel=&quot;nofollow&quot;&gt;Access U&lt;/a&gt;&quot;  really trying to figure out the best way to introduce accessibility into our design and development processes. One of the sessions claimed that the tasks associated with accessibility rested between content authors, testers and management, and another advocated addressing it as a QA issue, above all else. I will be interested to learn your thoughts..</description>
		<content:encoded><![CDATA[<p>I will definitely be &#8216;tuning in&#8217; for the next few episodes. I just spent the last few days at &#8220;<a href="http://www.knowbility.org/conference/" rel="nofollow">Access U</a>&#8221;  really trying to figure out the best way to introduce accessibility into our design and development processes. One of the sessions claimed that the tasks associated with accessibility rested between content authors, testers and management, and another advocated addressing it as a QA issue, above all else. I will be interested to learn your thoughts..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alun David</title>
		<link>http://alastairc.ac/2007/05/responsibilities-in-accessibility/comment-page-1/#comment-14958</link>
		<dc:creator>Alun David</dc:creator>
		<pubDate>Fri, 11 May 2007 16:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2007/05/responsibilities-in-accessibility/#comment-14958</guid>
		<description>As usual a cracking article.</description>
		<content:encoded><![CDATA[<p>As usual a cracking article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrick h. lauke</title>
		<link>http://alastairc.ac/2007/05/responsibilities-in-accessibility/comment-page-1/#comment-14829</link>
		<dc:creator>patrick h. lauke</dc:creator>
		<pubDate>Tue, 08 May 2007 22:34:08 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2007/05/responsibilities-in-accessibility/#comment-14829</guid>
		<description>i&#039;m intrigued...can&#039;t wait for the next two episodes, as you well know that this is right up my street.</description>
		<content:encoded><![CDATA[<p>i&#8217;m intrigued&#8230;can&#8217;t wait for the next two episodes, as you well know that this is right up my street.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

