Bobby isn’t so bad to get passed the automated checks etc.. it’s the W3C web accessibility guideline manual checks which will do your head in..

 

Like, color shouldn’t convey meaning, and content should be written in a way that users with cognitive disabilities can understand. :S Tell that to a designer or academic..

 

I completed a site recently (victorchang.org.au) that passes all the major online validators (did when I built it for my old employer), CSS for layouts, should downgrade when css is turned off. Etc etc.. But compromises were still made to keep the majority happy, not to mention clients that don’t always get it either.

 

This site/toolbar is a must for anyone concerned about accessible websites… When factored into the design and you have knowledgeable designers its not to bad..

 

http://www.nils.org.au/ais/web/resources/toolbar/

 

My two cents worth.

 

Jason

 

-----------------------
Jason Bayly
Newgency Pty Ltd
http://www.newgency.com/


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shane Farmer
Sent: Friday, 13 May 2005 3:56 PM
To: CFAussie Mailing List
Subject: [cfaussie] Re: OT: [best practice or your practice] CSS vs. Tables

 

If you have ever had to make a site "Bobby" compliant (for screen readers and the like) you will definitely have to go for CSS. A lot of government sites require this.

Shane
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/

---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to