<?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: Accessibility vs Universality &#8211; implications</title>
	<atom:link href="http://alastairc.ac/2007/02/accessibility-vs-universality-implications/feed/" rel="self" type="application/rss+xml" />
	<link>http://alastairc.ac/2007/02/accessibility-vs-universality-implications/</link>
	<description>Kything web interactions</description>
	<lastBuildDate>Fri, 13 Apr 2012 05:33:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: What is Web Universality? &#124; Joe Dolson Accessible Web Design</title>
		<link>http://alastairc.ac/2007/02/accessibility-vs-universality-implications/comment-page-1/#comment-13525</link>
		<dc:creator>What is Web Universality? &#124; Joe Dolson Accessible Web Design</dc:creator>
		<pubDate>Tue, 27 Mar 2007 16:52:54 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2007/02/accessibility-vs-universality-implications/#comment-13525</guid>
		<description>[...] Alastair Campbell: Accessibility vs. Universality Implications [...]</description>
		<content:encoded><![CDATA[<p>[...] Alastair Campbell: Accessibility vs. Universality Implications [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlastairC</title>
		<link>http://alastairc.ac/2007/02/accessibility-vs-universality-implications/comment-page-1/#comment-12727</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Wed, 28 Feb 2007 17:10:22 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2007/02/accessibility-vs-universality-implications/#comment-12727</guid>
		<description>I wouldn&#039;t have thought so, but you do need a more recent version of JAWs/Window eyes than some people have.

Also, if you are looking at forms, then version 7 of Acrobat (perhaps 8 for some things?) would be needed, and 6 or higher for the use of table headings.

The main point was that there can be practical issues you need to think about, as well as the theoretical aspects of the standards. (E.g. few UAs follow the appropriate guidelines.)</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t have thought so, but you do need a more recent version of JAWs/Window eyes than some people have.</p>
<p>Also, if you are looking at forms, then version 7 of Acrobat (perhaps 8 for some things?) would be needed, and 6 or higher for the use of table headings.</p>
<p>The main point was that there can be practical issues you need to think about, as well as the theoretical aspects of the standards. (E.g. few UAs follow the appropriate guidelines.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://alastairc.ac/2007/02/accessibility-vs-universality-implications/comment-page-1/#comment-12720</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Wed, 28 Feb 2007 15:04:20 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2007/02/accessibility-vs-universality-implications/#comment-12720</guid>
		<description>I don’t think there is any “upgrade” necessary for accessible PDF. Are people really using Acrobat 4 or earlier?</description>
		<content:encoded><![CDATA[<p>I don’t think there is any “upgrade” necessary for accessible PDF. Are people really using Acrobat 4 or earlier?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

