Cant figure out this validation errors...

seomul

05-11-2010, 07:59 AM

I am having one hell of a time validating this page I suspect the main issue is the header:
can anyone explain what does this validation error mean:

document type does not allow element "html" here <html xmlns="http://www.w3.org/1999/xhtml">

what needs to be fixed here with respect to validation.

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.themoroccanbazaar.com%2F&charset=%28detect+automatically%29&doctype=Inline&group=1&user-agent=W3C_Validator%2F1.767 (http://validator.w3.org/check?uri=http%3A%2F%2Fwww.themoroccanbazaar.com%2F&charset=%28detect+automatically%29&doctype=Inline&group=1&user-agent=W3C_Validator%2F1.767)

I appreciate any input on this! Thanks!

mbaker

05-11-2010, 08:40 AM

[oops this first one was from the copy I'm working with, not your original page.
Several errors will disappear if you use the validator to replace your Doctype.

I can't see the difference, but when it places the doctype on your document there are less errors. ]

Next replace the & in your meta description with & That will remove one error.

mbaker

05-11-2010, 09:31 AM

Replacing all </li><br /> with <br /></li> will reduce your errors by more than 50%. Most of these you can do with a global replace. However there is one at about line 250 that you will have to do by hand. [<br /> is not allowed in <ul>, but it is allowed in <li>]

[BTW rather than using markup to create the display you want, it would be better to use CSS]

In the URL at about line 290 replace the & with &

From all <table> tags remove the height attributes and height values.

From the iframe delete allowtransparency="allowtransparency"

You should be able to fix the rest of the errors using CSS.

You may know this already, but CSS is a much better way of adding styling to your pages than using tables and has been for the past 10 years.

seomul

05-11-2010, 05:25 PM

MBaker,
I truly Appreciate the feedback! I am going to try to correct the errors. Yes indeed CSS/tables free design is much better and that is precisely what we are working on.
Again thank you so much!!