First of all a thankyou for releasing DNN 5.0 & all the effort that has been put into this release.

One thing I thought was that DNN 5.0 was going to be WC3 compliant out of the box.

I did a fresh install of 5.0 & get the following WC3 errors:

Validation Output: 5 Errors

1. Line 92, Column 45: there is no attribute "width".

   …                    <span><div width="100%" class="DNNMenu main_dnnmenu_subme

   ✉

   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.

2. Line 92, Column 94: there is no attribute "name".

   …="DNNMenu main_dnnmenu_submenu" name="dnn$dnnNAV$ctldnnNAV" id="dnn_dnnNAV_ct

   ✉

   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.

3. Line 92, Column 142: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.

   …$ctldnnNAV" id="dnn_dnnNAV_ctldnnNAV">

   ✉

   The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

   One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

4. Line 93, Column 12: there is no attribute "name".

   	<span name="38" id="38"><span class=" "></span><a class="main_dnnmenu_rootitem_

   ✉

   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.

5. Line 93, Column 21: value of attribute "id" invalid: "3" cannot start a name.

   	<span name="38" id="38"><span class=" "></span><a class="main_dnnmenu_rootitem_

   ✉

   It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

ASP.NET which DNN is based on is not fully compliant. These errors are asp.net specific.

Plus the errors are not clear to me. Take the first one for example. Is it complaining there's no width attribute. Because I see one in the div tag. If it's complaining there's one, a div can havea width.

Why do you want a 100% w3c compliant site? If you test any popular site, it's full of errors. It doesn't stop people from using it!

I am not kidding. If and if it's a big hassle to create a fully compliant web site then I wouldn't worry about it. If asp.net adds these attributes then there's little I can do if I want to use asp.net.   Not fully 100% compliant does not mean it's a bad broken site. It's NICE to be fully compliant but there's no law you have to be one.

Microsoft has been yelled at a gazillion times about this before. You can start yelling.

I don't see any yelling at amazon.com, ebay.com, cnn.com for not creating 100% comliant sites.

Note that browsers IGNORE any tags or attributes they don't understand. It's OK to have them. A standard is a guideline. It's not a law.