<?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: WAI has been an astounding success but. . .</title>
	<atom:link href="http://www.headstar.com/eablive/?feed=rss2&#038;p=82" rel="self" type="application/rss+xml" />
	<link>http://www.headstar.com/eablive/?p=82</link>
	<description>Access to technology for all</description>
	<lastBuildDate>Sun, 01 Apr 2018 16:32:15 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.0.1</generator>
	<item>
		<title>By: Richard Warren</title>
		<link>http://www.headstar.com/eablive/?p=82&#038;cpage=1#comment-33</link>
		<dc:creator><![CDATA[Richard Warren]]></dc:creator>
		<pubDate>Wed, 21 Feb 2007 13:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=82#comment-33</guid>
		<description><![CDATA[You are right that the first version of WAI takes time to understand, it mixes up techniques that are design issues (colour and layout), authoring issues (language and structure) and technical issues (correct html code etc.). It was also written by committee process and attempted to form the basis for a legal document.

The new (version 2) WAI is much better as it clearly seperates the disciplines. Now the graphic designer can concentrate on ensuring that the &quot;look and feel&quot; is accessible, the author can concentrate on the text leaving the engineer to do all the technical stuff required to deliver that style and content reliably over the Internet. 

The key to successful use of WAI is to understand that &quot;web-design&quot; is a combination of these disciplines. Wherever possible it should be a team effort, but if only one person is responsible for the whole enterprise then s/he needs to understand each of the disciplines and apply the different skills at the appropriate stages of development.

Another benefit of version 2 is the ability to define a baseline for users and technologies. This means that the guidelines can be applied quite easily to a whole range of communication technologies (not just html websites). So the new version is platform neutral and should not limit creativity. However it does require webdesigners to think about what they are doing and take responsibility for ensuring that they properly understand the technologies they are using and do not introduce barriers to accessibility through poor engineering.]]></description>
		<content:encoded><![CDATA[<p>You are right that the first version of WAI takes time to understand, it mixes up techniques that are design issues (colour and layout), authoring issues (language and structure) and technical issues (correct html code etc.). It was also written by committee process and attempted to form the basis for a legal document.</p>
<p>The new (version 2) WAI is much better as it clearly seperates the disciplines. Now the graphic designer can concentrate on ensuring that the &#8220;look and feel&#8221; is accessible, the author can concentrate on the text leaving the engineer to do all the technical stuff required to deliver that style and content reliably over the Internet. </p>
<p>The key to successful use of WAI is to understand that &#8220;web-design&#8221; is a combination of these disciplines. Wherever possible it should be a team effort, but if only one person is responsible for the whole enterprise then s/he needs to understand each of the disciplines and apply the different skills at the appropriate stages of development.</p>
<p>Another benefit of version 2 is the ability to define a baseline for users and technologies. This means that the guidelines can be applied quite easily to a whole range of communication technologies (not just html websites). So the new version is platform neutral and should not limit creativity. However it does require webdesigners to think about what they are doing and take responsibility for ensuring that they properly understand the technologies they are using and do not introduce barriers to accessibility through poor engineering.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
