CSS errors raining using W3C validator

Yes, I have real CSS (&JavaScript/AJAX/jQuery) errors so checking the CSS and repairing is important. have no idea if the errors from Swekey are contributing to the problems I experience, but if not, its difficult to find the real errors with this huge list using http://validator.w3.org :

...
11. Error Line 502, Column 122: an attribute value must be a literal unless it contains only name characters
…hare.gif" width="125" height="16" alt=&quot;&quot; /></a><script type="text/ja…
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
12. Warning Line 583, Column 51: cannot generate system identifier for general entity "swekey_id"
swekey_loginname_resolve_url = "?q=swekey_resolve&swekey_id=$swekey_id";
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
13. Error Line 583, Column 51: general entity "swekey_id" not defined and no default entity
swekey_loginname_resolve_url = "?q=swekey_resolve&swekey_id=$swekey_id";
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
14. Warning Line 583, Column 60: reference not terminated by REFC delimiter
swekey_loginname_resolve_url = "?q=swekey_resolve&swekey_id=$swekey_id";
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
15. Error Line 583, Column 60: reference to entity "swekey_id" for which no system identifier could be generated
swekey_loginname_resolve_url = "?q=swekey_resolve&swekey_id=$swekey_id";
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
16. Info Line 583, Column 50: entity was defined here
swekey_loginname_resolve_url = "?q=swekey_resolve&swekey_id=$swekey_id";
17. Warning Line 584, Column 76: cannot generate system identifier for general entity "check_server"
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
18. Error Line 584, Column 76: general entity "check_server" not defined and no default entity
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
19. Warning Line 584, Column 88: reference not terminated by REFC delimiter
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
20. Error Line 584, Column 88: reference to entity "check_server" for which no system identifier could be generated
...es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
21. Info Line 584, Column 75: entity was defined here
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
22. Warning Line 584, Column 90: cannot generate system identifier for general entity "rndtoken_server"
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
23. Error Line 584, Column 90: general entity "rndtoken_server" not defined and no default entity
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
24. Warning Line 584, Column 105: reference not terminated by REFC delimiter
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
25. Error Line 584, Column 105: reference to entity "rndtoken_server" for which no system identifier could be generated
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
26. Info Line 584, Column 89: entity was defined here
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
27. Error Line 492, Column 80: Opening and ending tag mismatch: br line 492 and ul
…446</li><li>Unique Visitor: 51</li><li>Registered Users: 1</li><li>Unregistere…
28. Error Line 492, Column 81: Opening and ending tag mismatch: br line 492 and div
…46</li><li>Unique Visitor: 51</li><li>Registered Users: 1</li><li>Unregistered…
29. Error Line 493, Column 6: Opening and ending tag mismatch: br line 492 and div
</div>
30. Error Line 502, Column 80: AttValue: " or ' expected
…><img src="http://s9.addthis.com/button1-share.gif" width="125" height="16" al…
31. Error Line 502, Column 80: attributes construct error
…><img src="http://s9.addthis.com/button1-share.gif" width="125" height="16" al…
32. Error Line 502, Column 80: Couldn't find end of Start Tag img line 502
…><img src="http://s9.addthis.com/button1-share.gif" width="125" height="16" al…
33. Error Line 548, Column 15: Opening and ending tag mismatch: ul line 492 and div
</div>
34. Error Line 583, Column 59: EntityRef: expecting ';'
swekey_loginname_resolve_url = "?q=swekey_resolve&swekey_id=$swekey_id";
35. Error Line 584, Column 80: EntityRef: expecting ';'
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
36. Error Line 584, Column 80: EntityRef: expecting ';'
…es/all/modules/swekey/authframe.php?use_file=1&check_server=&rndtoken_server=";
37. Error Line 600, Column 9: Opening and ending tag mismatch: div line 452 and body
</body>
38. Error Line 601, Column 7: Opening and ending tag mismatch: div line 227 and html
</html>
39. Error Line 601, Column 7: Premature end of data in tag div line 157
</html>
40. Error Line 601, Column 7: Premature end of data in tag body line 156
</html>
41. Error Line 601, Column 7: Premature end of data in tag html line 2
</html>

Other validators: http://wi-ca.org/Drupal_CSS