I think we are talking about a java-based CMS, so I guess JSP (as opposed to PHP, ASP etc.) that generates valid output. Right?
In the end the CMS server technology is not really an issue. It is how the developers have used the technology to create the CMS output. For example if they generate a dynamic page and use invalid X/HTML markup then the page will of course not validate. Johan > ------------Original Message------------ > From: "Geoff Deering" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: Wed, Oct-6-2004 8:59 AM > Subject: RE: [WSG CMS] Re: digest for [EMAIL PROTECTED] > > > Gang: Great discussion on standards & CMS. > > > > One puzzle for me is finding a Java system that is easily made web > > standards compliant. Any pointers? > > > > My guess is the java gang is more oriented towards great engineering > > and technology .. but I've tried getting java based sites to validate > > via: http://validator.w3.org/ .. and I don't think I've gotten any to > > validate! This includes roller, pebble, blojsom etc. > > > > -- Owen > > I trust you are meaning Java on the client side and not server side > Java. > > If so, that has nothing to do with Java. The validator is just parsing > the > markup (HTML/XHTML). Java is seperate. You should be able to put Java > in > your web page and validate it. Just seems all the Java sites you have > been > too have invalid markup. > > On the other hand, if your site is dependant on Java functionality, it > cannot pass Accessibility WCAG1 P1; > http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-scripts > > Geoff > > ********************************************************* > The CMS discussion list for http://webstandardsgroup.org/ > ********************************************************* > > > ********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
