WCAG 2 Comment

I have supported WCAG 1 and have implemented its guidelines in the sites I build. The guidelines were relatively easy to understand and implement.
 
My eyes glaze over looking at the massive volumes produced to explain WCAG 2. Isn't the purpose of WCAG 2 to promote website accessibility? If these bloated, dense, inscrutable texts are approved, WCAG 2 risks becoming utterly irrelevant to small to medium web development shops. Accessibility will suffer. 
 
Let's do the right thing and rework these guidelines for usability. We've got to make them easy for developers to understand and use. 
 
Art Zoller Wagner       www.DigitalDesign.us

		
---------------------------------
How low will we go? Check out Yahoo! Messengerís low  PC-to-Phone call rates.
--0-35331346-1148442033=:47218
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I have supported WCAG 1 and have implemented its guidelines in the sites I build. The guidelines were relatively easy to understand and implement.<br>&nbsp;<br>My eyes glaze over looking at the massive volumes produced to explain WCAG 2. Isn't the purpose of WCAG 2 to promote website accessibility? If these bloated, dense, inscrutable texts are approved, WCAG 2 risks becoming utterly irrelevant to small to medium web development shops. Accessibility will suffer. <br>&nbsp;<br>Let's do the right thing and rework these guidelines for usability. We've got to make them easy for developers to understand and use. <br>&nbsp;<br>Art Zoller Wagner&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; www.DigitalDesign.us<br><p>
		<hr size=1>How low will we go? Check out Yahoo! Messengerís low <a href="http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com"> PC-to-Phone call rates.
--0-35331346-1148442033=:47218--

Received on Wednesday, 24 May 2006 04:37:30 UTC