The first dozen or so errors have to do with XHTML syntax being used for <meta> and <link> elements in an HTML document. Basicly there's a bunch of "/" where they shouldn't be.
There's some errors later on similar to this, but apply to <img> elements instead of <meta> and <link>.
The next half-dozen or so are byproducts of the first errors. When those unneeded "/" characters are removed these errors will cease to exist.
The "onresize" attribute error means you're not supposed to use the onresize event attached to the <body> element as an attribute.
I'd have to take a better look at that one, but the fix breaks basicly amounts to removing the attribute from the <body> element and attaching the event in one of the *.js files being loaded instead.
The "autocomplete" error is similar to the "onresize" error.
The "document doesn't allow <form> element here" error has to do with a <form> element being placed inside a <span> element. First thing I would try is swapping the order of the <form> and <span> elements like the following, and if that made somthing look different I'd look at it more closely.
from
<span ...><form>...</form></span>
to
<form><span>...</span></form>
- from
- <span ...><form>...</form></span>
-
- to
- <form><span>...</span></form>
All of the "required attribute 'ALT' not specified." errors have to do with a missing alt attribute on images. When for some reason a browser can't load an image, it uses the alt attribute to tell the visitor what they would have been looking at.
Fixing this can be easy or hard depending on how things are setup on the server. In some cases where there's already a title attribute, a simple find & replace using patterns can be used to copy the title attributes as alt attributes.
There's some errors about "height" and "width" attributes on some elements. All of those are correctable by using the "style" attribute with width & height CSS instead of attributes.
For instance
instead of
<table height="100" width="100">
it would be
<table style="width:100px;height:100px"
- instead of
- <table height="100" width="100">
-
- it would be
- <table style="width:100px;height:100px"
Not the most elegant way to do it, but will get rid of the errors.
The "reference to entity" errors boil down to URLs in your links and form actions using "&" as an argument separator, instead of "&".
The parser thinks the next alphabetic characters after the ampersand are supposed to define an entity. Finding and replacing "&" with "&" then replacing "&amp;" with "&" in templates and application code will get rid of those errors.
The errors that look like the following happen because of " (double quote) characters in your product descriptions and/or titles.
Line 1069, Column 163: "WIDECREEN" is not a member of a group specified for any attribute.
Information on LCD22WV 22" Widecreen 5ms LCD Monitor"></a>
To fix these, someone needs to run a query on the database table holding the product descriptions that replaces " with the " entity.
For instance,
22" Widescreen would become
22" Widescreen.
It looks like there's <style> elements inside the <body> comtainer, and these needto be moved to the inside of the <head> container instead.
The "ID FOOTER_ITEM already defined." errors have to do with what's supposed to be an attribute that uniquely identifies an element being used on more than one element.
The CSS which applies to "#footer_item" may likely need to be changed to ".footer_item" and the elements with "id='footer_item'" changed to "class='footer_item'".
class is an attribute that makes an element part of a group, which is what is needed because of the multiple elements using the attribute.
I probably missed some because I page-down'ed through the majority of it. But that's what I saw.
Strong with this one, the sudo is.