Hi there,

I'm trying to make the repository module W3C compliant and I use Mozilla Firefox to validate the local HTML to find out what needs to be modified in order for the module to meet XHTML 1.0 Transitional standards.

I've been able to bring the errors from 62 down to 29 errors by fixing / closing tags etc. Most errors were straight forward and were easy to fix.

Unfortunatately I am unable to fix the last 29 errors as these relate to certain HTML tags that do not exist in the repository.aspx page or the default.aspx page.

I've tried stepping through the code and i've not had a lot of luck trying to decipher where I need to make changes. I believe a JavaScript file is generating HTML code on the fly or even a 'code behind' vb file. I just cannot seem to find it. I've looked at the dnncore.js and dnn.js.

Can anyone shed some light and help me out?

Once this is done I have to find a work around to replace javascript classes / functions as most of our users use screen readers and some are colour deficient as well as hearing impaired.

Below are some brief examples of the error messages I get.

Example of error messages:

This page is not Valid XHTML 1.0 Transitional!

Error Line 62 column 13: there is no attribute "CLASS".

<TABLE CLASS= " normal" WIDTH="100%" CELLSPACING="0" CELLPADDING="0" STYLE="paddin

You have used the attribute named above in your document, but the document type
you are using does not support that attribute for this element. This error is often caused
by incorrect use of the "Strict" document type with a document that uses frames (e.g.
you must use the "Transitional" document type to get the "target" attribute), or by using
vendor proprietary extensions such as "marginheight" (this is usually fixed by using
CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you
are using, as an undefined element will have no supported attributes; in this case, see
the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember
XHTML is all lower-case) and/or check that they are both allowed in the chosen
document type, and/or use CSS instead of this attribute. If you received this error when
using the <embed> element to incorporate flash media in a Web page, see the FAQ
item on valid flash.

Error Line 62 column 28: there is no attribute "WIDTH".

<TABLE CLASS="normal" WIDTH= " 100%" CELLSPACING="0" CELLPADDING="0" STYLE="paddin

You have used the attribute named above in your document, but the document type
you are using does not support that attribute for this element. This error is often caused
by incorrect use of the "Strict" document type with a document that uses frames (e.g.
you must use the "Transitional" document type to get the "target" attribute), or by using
vendor proprietary extensions such as "marginheight" (this is usually fixed by using
CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you
are using, as an undefined element will have no supported attributes; in this case, see
the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember
XHTML is all lower-case) and/or check that they are both allowed in the chosen
document type, and/or use CSS instead of this attribute. If you received this error when
using the <embed> element to incorporate flash media in a Web page, see the FAQ
item on valid flash.

Thanks Steve I'll investigate this and see if I can clear the remaining errors.

With regards to the Default.aspx and the Repsoitory.ascx files (I did type Repository.aspx, sorry I was meant to type in the ascx extension), I've located the Default.aspx page in the website folder, (C:\Inetpub\DotNetNuke\Website\Default.aspx) and the Repsoitory.ascx is in (C:\Inetpub\DotNetNuke441\Website\DesktopModules\Repository\Repository.ascx)