Personally I think valid XHTML is a must these days for any CMS to be taken seriously. Besides that, it's not terribly hard to implement anyway for the company building the CMS.

About the authors: if the CMS incorporates an inline XHTML editor for large content areas it should be no problem to prevent them from entering invalid code. If they type raw HTML I agree you cannot possibly control what they do. But that's not necessary anymore :)

Cheers,

Marco

--
Marco van Hylckama Vlieg

Senior Internet Developer

email: [EMAIL PROTECTED]
www: http://www.i-marco.nl/
On Dec 10, 2004, at 1:06 AM, Mark Stanton wrote:

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/ *********************************************************



Reply via email to