Suggestions on accessibility: testing tools are a good start but you need to use your own judgement of results: http://bobby.watchfire.com/bobby/bobbyServlet?URL=http://www.blacktown.nsw.gov.au/
For table layouts it can be informative to use a screen reader. Tables can be coded so that header information repeats in each row which you'll appreciate if you "listen" to a table being read. Transforming this page to screenreader format (just a demo so do not expect to navigate the site in screenreader mode) shows you what the table looks like: http://www.assetnow.com/anx/index.cfm/1,56,exp However please accept the positives - the site certainly looks great and appears to have a heap of useful content. Regards Johan > ------------Original Message------------ > From: Mark Stanton <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: Fri, Dec-10-2004 1:08 PM > Subject: Re: [WSG CMS] General CMS consensus > > XHTML - bleh. Why exactly? Personally I've only found a use for it > once and that was a very specific case where XHTML file were the data > storage medium (rather than a database). > > Validation - true. I'd love to be able to say the CMS only allows > valid code, but it doesn't :( I'd also love to say all the authors > make sure they only write clean valid content rather than pasting word > documents in, but... > > Accessibility - yes. In my opinion its not too bad, but if you've got > any suggestion or feedback I'd appreciate hearing it. > > -- > Mark Stanton > Gruden Pty Ltd > http://www.gruden.com > ********************************************************* > The CMS discussion list for http://webstandardsgroup.org/ > ********************************************************* > > > ********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
