Huddersfield Search Engine Optimization

Here we have a demo of a JOOMLA site, CMS (content management system) presented here with a selection of features that are more geared towards local user interaction than strictly conforming to W3C verification .

how important strict compliance really is OR NOT!, having a good user experience, interactive features - stuff like embedded video is alway way more engaging than spartan compliant sites, connectivity & localized presence much outweigh the squeeky clean code geeks - just look at youtube.com

Errors found while checking this document as HTML 4.01 Transitional!

didn't affect their value did it ??

Validation Output: 88 Errors

1. Line 28, Column 15: Attribute "ID" is not a valid attribute. Did you mean "id"?

   			<script id="www-core-js" src="http://s.ytimg.com/yt/jsbin/www-core-vfl129358.

   ✉

   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 28, Column 84: required attribute "TYPE" not specified

   ….com/yt/jsbin/www-core-vfl129358.js"></script>

   ✉

   The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

   Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

3. Line 57, Column 44: Attribute "STYLE" is not a valid attribute. Did you mean "style"?

   …pt id="legacy-user-datastore" style="behavior:url('#default#userdata')"></scr

   ✉

   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.

4. Line 57, Column 79: required attribute "TYPE" not specified

   …e="behavior:url('#default#userdata')"></script>

   ✉

   The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

   Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

5. Line 66, Column 74: required attribute "TYPE" not specified

   …com/yt/js/channel_legacy_all-vfl129247.js"></script>

   ✉

   The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

   Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

6. Line 68, Column 70: required attribute "TYPE" not specified

   …s.ytimg.com/yt/jsbin/www-channel-vfl128554.js"></script>

   ✉

   The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

   Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

7. Line 106, Column 10: required attribute "TYPE" not specified

   		<script>

   ✉

   The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

   Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

8. Line 153, Column 28: Attribute "ID" is not a valid attribute. Did you mean "id"?

   	<style type="text/css" id="channel-theme-css" name="channel-theme-css">

   ✉

   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.

9. Line 153, Column 53: Attribute "NAME" is not a valid attribute. Did you mean "name"?

   	<style type="text/css" id="channel-theme-css" name="channel-theme-css">

   ✉

   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.

10. Line 190, Column 49: NET-enabling start-tag requires SHORTTAG YES

    		<link rel="canonical" href="/user/spineyExtra"/>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

11. Line 193, Column 111: cannot generate system identifier for general entity "user"

    …e?desktop_uri=%2Fuser%2FspineyExtra&user=spineyExtra">

    ✉

    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 "&" (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 æ 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.

12. Line 193, Column 111: general entity "user" not defined and no default entity

    …e?desktop_uri=%2Fuser%2FspineyExtra&user=spineyExtra">

    ✉

    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.

13. Line 193, Column 115: reference to entity "user" for which no system identifier could be generated

    …sktop_uri=%2Fuser%2FspineyExtra&user=spineyExtra">

    ✉

    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. Line 193, Column 109: entity was defined here

    …ile?desktop_uri=%2Fuser%2FspineyExtra&user=spineyExtra">

15. Line 193, Column 128: document type does not allow element "LINK" here

    …user%2FspineyExtra&user=spineyExtra">

    ✉

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

16. Line 197, Column 91: document type does not allow element "META" here

    …with friends, family, and the world">

    ✉

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

17. Line 199, Column 89: document type does not allow element "META" here

    …ra phone, video phone, free, upload">

    ✉

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

18. Line 201, Column 7: end tag for element "HEAD" which is not open

    </head>

    ✉

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

19. Line 204, Column 31: document type does not allow element "BODY" here

    <body class="en_US is-english">

    ✉

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

20. Line 223, Column 21: Attribute "AUTOCOMPLETE" is not a valid attribute

    	<form autocomplete="off" class="search-form" action="/results" method="get" nam

    ✉

    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.

21. Line 226, Column 45: syntax of attribute value does not conform to declared value

    …s="yt-button yt-button-primary" id="" style="" href="#" onclick="if (_gel('ma

    ✉

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

22. Line 233, Column 130: cannot generate system identifier for general entity "ltmpl"

    ….com%2Fcreate_account%3Fnext%3DNone&ltmpl=sso&hl=en_US&service=youtube" onmou

    ✉

    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 "&" (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 æ 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. Line 233, Column 130: general entity "ltmpl" not defined and no default entity

    ….com%2Fcreate_account%3Fnext%3DNone&ltmpl=sso&hl=en_US&service=youtube" onmou

    ✉

    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. Line 233, Column 135: reference to entity "ltmpl" for which no system identifier could be generated

    …2Fcreate_account%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedow

    ✉

    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.

25. Line 233, Column 128: entity was defined here

    …be.com%2Fcreate_account%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onm

26. Line 233, Column 140: cannot generate system identifier for general entity "hl"

    …ate_account%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedown="yt

    ✉

    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 "&" (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 æ 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.

27. Line 233, Column 140: general entity "hl" not defined and no default entity

    …ate_account%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedown="yt

    ✉

    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.

28. Line 233, Column 142: reference to entity "hl" for which no system identifier could be generated

    …e_account%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedown="yt.a

    ✉

    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.

29. Line 233, Column 138: entity was defined here

    …reate_account%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedown="

30. Line 233, Column 149: cannot generate system identifier for general entity "service"

    …nt%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedown="yt.analytic

    ✉

    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 "&" (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 æ 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.

31. Line 233, Column 149: general entity "service" not defined and no default entity

    …nt%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedown="yt.analytic

    ✉

    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.

32. Line 233, Column 156: reference to entity "service" for which no system identifier could be generated

    …xt%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedown="yt.analytics.urchi

    ✉

    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.

33. Line 233, Column 147: entity was defined here

    …ount%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedown="yt.analyt

34. Line 235, Column 75: reference to entity "service" for which no system identifier could be generated

    …ccounts/ServiceLogin?uilel=3&service=youtube&passive=true&continue=http%3A%2F

    ✉

    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.

35. Line 233, Column 147: entity was defined here

    …ount%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedown="yt.analyt

36. Line 235, Column 84: cannot generate system identifier for general entity "passive"

    …erviceLogin?uilel=3&service=youtube&passive=true&continue=http%3A%2F%2Fwww.yo

    ✉

    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 "&" (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 æ 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.

37. Line 235, Column 84: general entity "passive" not defined and no default entity

    …erviceLogin?uilel=3&service=youtube&passive=true&continue=http%3A%2F%2Fwww.yo

    ✉

    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.

38. Line 235, Column 91: reference to entity "passive" for which no system identifier could be generated

    …ogin?uilel=3&service=youtube&passive=true&continue=http%3A%2F%2Fwww.youtube.c

    ✉

    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.

39. Line 235, Column 82: entity was defined here

    …/ServiceLogin?uilel=3&service=youtube&passive=true&continue=http%3A%2F%2Fwww.

40. Line 235, Column 97: cannot generate system identifier for general entity "continue"

    …ilel=3&service=youtube&passive=true&continue=http%3A%2F%2Fwww.youtube.com%2Fs

    ✉

    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 "&" (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 æ 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.

41. Line 235, Column 97: general entity "continue" not defined and no default entity

    …ilel=3&service=youtube&passive=true&continue=http%3A%2F%2Fwww.youtube.com%2Fs

    ✉

    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.

42. Line 235, Column 105: reference to entity "continue" for which no system identifier could be generated

    …ervice=youtube&passive=true&continue=http%3A%2F%2Fwww.youtube.com%2Fsignin%3F

    ✉

    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.

43. Line 235, Column 95: entity was defined here

    …?uilel=3&service=youtube&passive=true&continue=http%3A%2F%2Fwww.youtube.com%2

44. Line 235, Column 243: reference to entity "hl" for which no system identifier could be generated

    …6next%3D%252Fuser%252FspineyExtra&hl=en_US<mpl=sso" onmousedown="yt.analyti

    ✉

    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.

45. Line 233, Column 138: entity was defined here

    …reate_account%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onmousedown="

46. Line 235, Column 255: reference to entity "ltmpl" for which no system identifier could be generated

    …Fuser%252FspineyExtra&hl=en_US<mpl=sso" onmousedown="yt.analytics.urchinTra

    ✉

    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.

47. Line 233, Column 128: entity was defined here

    …be.com%2Fcreate_account%3Fnext%3DNone<mpl=sso&hl=en_US&service=youtube" onm

48. Line 242, Column 62: syntax of attribute value does not conform to declared value

    …-button-urgent yt-button-short" id="" style="" href="/my_videos_upload" oncli

    ✉

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

49. Line 280, Column 14: syntax of attribute value does not conform to declared value

        <img id="" src="http://i3.ytimg.com/i/vdi74K1MwsuHqmV62ePWsA/1.jpg?v=7ba06e"

    ✉

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

50. Line 293, Column 46: syntax of attribute value does not conform to declared value

    …ss="yt-button yt-button-urgent" id="" style="" href="https://www.google.com/a

    ✉

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

51. Line 314, Column 24: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

    		<div class="contents">

    ✉

    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>").

52. Line 328, Column 24: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

    		<div class="contents">

    ✉

    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>").

53. Line 361, Column 193: end tag for element "A" which is not open

    …er/\">Get the latest Flash player</a>.');

    ✉

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

54. Line 562, Column 32: required attribute "TYPE" not specified

    		<script language="javascript">

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

55. Line 594, Column 198: NET-enabling start-tag requires SHORTTAG YES

    …http://kirklees-badgers.co.uk</a><br/><a href="http://ubp.wq2rx.com" target="

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

56. Line 594, Column 328: NET-enabling start-tag requires SHORTTAG YES

    …ir="ltr">http://ubp.wq2rx.com</a><br/><br/>ѕ¢ιєи¢є σя ѕ¢αм  ?<br/><br/>Snares

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

57. Line 594, Column 333: NET-enabling start-tag requires SHORTTAG YES

    …tr">http://ubp.wq2rx.com</a><br/><br/>ѕ¢ιєи¢є σя ѕ¢αм  ?<br/><br/>Snares are 

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

58. Line 594, Column 356: NET-enabling start-tag requires SHORTTAG YES

    …m</a><br/><br/>ѕ¢ιєи¢є σя ѕ¢αм  ?<br/><br/>Snares are crude & cruel killi

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

59. Line 594, Column 361: NET-enabling start-tag requires SHORTTAG YES

    …<br/><br/>ѕ¢ιєи¢є σя ѕ¢αм  ?<br/><br/>Snares are crude & cruel killing de

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

60. Line 615, Column 9: required attribute "TYPE" not specified

    	<script>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

61. Line 643, Column 120: required attribute "ALT" not specified

    …l-vfl73.gif" height="60" width="300"></div>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

62. Line 658, Column 71: NET-enabling start-tag requires SHORTTAG YES

    …d="playnav-playlist-uploads-count" value="82"/>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

63. Line 666, Column 29: syntax of attribute value does not conform to declared value

    			<a class="yt-button" id="" style="" href="javascript:;" onclick="playnav.sear

    ✉

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

64. Line 701, Column 43: Attribute "ONSCROLL" is not a valid attribute. Did you mean "scrolling"?

    …iv class="outer-scrollbox" onscroll="playnav.updateScrollbox('playnav-play-up

    ✉

    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.

65. Line 1107, Column 75: NET-enabling start-tag requires SHORTTAG YES

    …yt/img/icn_loading_animated-vfl24663.gif"/>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

66. Line 1107, Column 75: required attribute "ALT" not specified

    …yt/img/icn_loading_animated-vfl24663.gif"/>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

67. Line 1125, Column 75: NET-enabling start-tag requires SHORTTAG YES

    …yt/img/icn_loading_animated-vfl24663.gif"/>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

68. Line 1125, Column 75: required attribute "ALT" not specified

    …yt/img/icn_loading_animated-vfl24663.gif"/>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

69. Line 1141, Column 119: required attribute "ALT" not specified

    …xt-align:center; padding:30px 280px'>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

70. Line 1145, Column 120: required attribute "ALT" not specified

    …xt-align:center; padding:30px 300px'>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

71. Line 1159, Column 14: syntax of attribute value does not conform to declared value

        <img id="" src="http://i3.ytimg.com/i/vdi74K1MwsuHqmV62ePWsA/1.jpg?v=7ba06e"

    ✉

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

72. Line 1171, Column 46: syntax of attribute value does not conform to declared value

    …ss="yt-button yt-button-urgent" id="" style="" href="https://www.google.com/a

    ✉

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

73. Line 1183, Column 63: cannot generate system identifier for general entity "action_compose"

    …="aProfileSendMsg" href="/inbox?to_users=spineyExtra&action_compose=1">Send Message</a>

    ✉

    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 "&" (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 æ 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.

74. Line 1183, Column 63: general entity "action_compose" not defined and no default entity

    …="aProfileSendMsg" href="/inbox?to_users=spineyExtra&action_compose=1">Send Message</a>

    ✉

    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.

75. Line 1183, Column 77: reference to entity "action_compose" for which no system identifier could be generated

    …box?to_users=spineyExtra&action_compose=1">Send Message</a>

    ✉

    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.

76. Line 1183, Column 61: entity was defined here

    …a id="aProfileSendMsg" href="/inbox?to_users=spineyExtra&action_compose=1">Send Message</a>

77. Line 1266, Column 47: NET-enabling start-tag requires SHORTTAG YES

    …ort domain alternative to youtube<br/><a href="http://spiney.at.tc/" target="

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

78. Line 1266, Column 177: NET-enabling start-tag requires SHORTTAG YES

    …ir="ltr">http://spiney.at.tc/</a><br/>has so many advantages - such as metada

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

79. Line 1266, Column 243: NET-enabling start-tag requires SHORTTAG YES

    …h as metadata,favicon,description<br/><br/>badgers<br/><a href="http://ubp.wq

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

80. Line 1266, Column 248: NET-enabling start-tag requires SHORTTAG YES

    …metadata,favicon,description<br/><br/>badgers<br/><a href="http://ubp.wq2rx.c

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

81. Line 1266, Column 260: NET-enabling start-tag requires SHORTTAG YES

    …icon,description<br/><br/>badgers<br/><a href="http://ubp.wq2rx.com" target="

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

82. Line 1266, Column 390: NET-enabling start-tag requires SHORTTAG YES

    …ir="ltr">http://ubp.wq2rx.com</a><br/><a href="http://shame.uk.tc" target="_b

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

83. Line 1266, Column 514: NET-enabling start-tag requires SHORTTAG YES

    … dir="ltr">http://shame.uk.tc</a><br/><a href="http://kirklees-badgers.co.uk"

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

84. Line 1266, Column 671: NET-enabling start-tag requires SHORTTAG YES

    …http://kirklees-badgers.co.uk</a><br/><a href="http://buzzbeeman.com" target=

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

85. Line 1266, Column 804: NET-enabling start-tag requires SHORTTAG YES

    …r="ltr">http://buzzbeeman.com</a><br/>youtube<br/><a href="http://youtube.com

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

86. Line 1266, Column 816: NET-enabling start-tag requires SHORTTAG YES

    …://buzzbeeman.com</a><br/>youtube<br/><a href="http://youtube.com/BLACKADDERE

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

87. Line 1266, Column 984: NET-enabling start-tag requires SHORTTAG YES

    …ttp://youtube.com/BLACKADD...</a><br/><a href="http://www.youtube.com/user/BE

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

88. Line 1266, Column 1178: NET-enabling start-tag requires SHORTTAG YES

    …ttp://www.youtube.com/user...</a><br/><a href="http://www.youtube.com/user/ki

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

89. Line 1266, Column 1352: NET-enabling start-tag requires SHORTTAG YES

    …ttp://www.youtube.com/user...</a><br/>wq2rx<br/><a href="http://wq2rx.com" ta

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

90. Line 1266, Column 1362: NET-enabling start-tag requires SHORTTAG YES

    …youtube.com/user...</a><br/>wq2rx<br/><a href="http://wq2rx.com" target="_bla

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

91. Line 1266, Column 1480: NET-enabling start-tag requires SHORTTAG YES

    …w" dir="ltr">http://wq2rx.com</a><br/><a href="http://junkie.wq2rx.com" targe

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

92. Line 1266, Column 1619: NET-enabling start-tag requires SHORTTAG YES

    …"ltr">http://junkie.wq2rx.com</a><br/>robin hood/history<br/><a href="http://

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

93. Line 1266, Column 1642: NET-enabling start-tag requires SHORTTAG YES

    …rx.com</a><br/>robin hood/history<br/><a href="http://robinhood.wq2rx.com" ta

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

94. Line 1266, Column 1790: NET-enabling start-tag requires SHORTTAG YES

    …r">http://robinhood.wq2rx.com</a><br/><a href="http://huddersfield.wq2rx.com"

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

95. Line 1266, Column 1947: NET-enabling start-tag requires SHORTTAG YES

    …http://huddersfield.wq2rx.com</a><br/><a href="http://outlaw.wq2rx.com" targe

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

96. Line 1266, Column 2086: NET-enabling start-tag requires SHORTTAG YES

    …"ltr">http://outlaw.wq2rx.com</a><br/><a href="http://ghost.wq2rx.com" target

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

97. Line 1266, Column 2222: NET-enabling start-tag requires SHORTTAG YES

    …="ltr">http://ghost.wq2rx.com</a><br/>weed<br/><a href="http://e-skunk.co.uk"

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

98. Line 1266, Column 2231: NET-enabling start-tag requires SHORTTAG YES

    …tp://ghost.wq2rx.com</a><br/>weed<br/><a href="http://e-skunk.co.uk" target="

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

99. Line 1266, Column 2361: NET-enabling start-tag requires SHORTTAG YES

    …ir="ltr">http://e-skunk.co.uk</a><br/>music & podcasts<br/><a href="http:

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

100. Line 1266, Column 2386: NET-enabling start-tag requires SHORTTAG YES

     …o.uk</a><br/>music & podcasts<br/><a href="http://mp3.wq2rx.com" target="

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

101. Line 1266, Column 2516: NET-enabling start-tag requires SHORTTAG YES

     …ir="ltr">http://mp3.wq2rx.com</a><br/><a href="http://wq2rx.podomatic.com/rss

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

102. Line 1266, Column 2686: NET-enabling start-tag requires SHORTTAG YES

     …ttp://wq2rx.podomatic.com/...</a><br/>aliases<br/><a href="http://badger.uk.t

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

103. Line 1266, Column 2698: NET-enabling start-tag requires SHORTTAG YES

     …podomatic.com/...</a><br/>aliases<br/><a href="http://badger.uk.tc" target="_

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

104. Line 1266, Column 2825: NET-enabling start-tag requires SHORTTAG YES

     …dir="ltr">http://badger.uk.tc</a><br/><a href="http://urban-badger.uk.tc" tar

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

105. Line 1266, Column 2970: NET-enabling start-tag requires SHORTTAG YES

     …tr">http://urban-badger.uk.tc</a><br/><a href="http://robin-hood.at.tc" targe

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

106. Line 1266, Column 3109: NET-enabling start-tag requires SHORTTAG YES

     …"ltr">http://robin-hood.at.tc</a><br/><a href="http://robinhood.co.uk.tc" tar

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

107. Line 1266, Column 3254: NET-enabling start-tag requires SHORTTAG YES

     …tr">http://robinhood.co.uk.tc</a><br/><a href="http://spiney.hu.tc" target="_

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

108. Line 1266, Column 3381: NET-enabling start-tag requires SHORTTAG YES

     …dir="ltr">http://spiney.hu.tc</a><br/><a href="http://linkfish.me.uk" target=

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

109. Line 1266, Column 3514: NET-enabling start-tag requires SHORTTAG YES

     …r="ltr">http://linkfish.me.uk</a><br/><a href="http://vi-gu.wq2rx.com" target

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

110. Line 1266, Column 3650: NET-enabling start-tag requires SHORTTAG YES

     …="ltr">http://vi-gu.wq2rx.com</a><br/>нєяє υи∂єяиєαтн ∂ιѕ ℓαιтℓ ѕтєαи<br/>ℓαz

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

111. Line 1266, Column 3686: NET-enabling start-tag requires SHORTTAG YES

     …/>нєяє υи∂єяиєαтн ∂ιѕ ℓαιтℓ ѕтєαи<br/>ℓαz яσвєят єαяℓ σf нυитιитυи<br/>иє'єя 

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

112. Line 1266, Column 3719: NET-enabling start-tag requires SHORTTAG YES

     …<br/>ℓαz яσвєят єαяℓ σf нυитιитυи<br/>иє'єя αя¢ιя νєя αѕ нιє ѕα gєυ∂<br/>αи ρ

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

113. Line 1266, Column 3754: NET-enabling start-tag requires SHORTTAG YES

     …r/>иє'єя αя¢ιя νєя αѕ нιє ѕα gєυ∂<br/>αи ριρℓ кαυℓ∂ ιм яσвιи нєυ∂<br/>ѕι¢к υт

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

114. Line 1266, Column 3786: NET-enabling start-tag requires SHORTTAG YES

     …∂<br/>αи ριρℓ кαυℓ∂ ιм яσвιи нєυ∂<br/>ѕι¢к υтℓαωz αѕ нιѕ αѕ ιz мєи<br/>νιℓ єи

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

115. Line 1266, Column 3819: NET-enabling start-tag requires SHORTTAG YES

     …<br/>ѕι¢к υтℓαωz αѕ нιѕ αѕ ιz мєи<br/>νιℓ єиgℓαи∂ иινя ѕι αgєи<br/>try<br/><a

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

116. Line 1266, Column 3848: NET-enabling start-tag requires SHORTTAG YES

     … мєи<br/>νιℓ єиgℓαи∂ иινя ѕι αgєи<br/>try<br/><a href="http://disdroid.co.uk"

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

117. Line 1266, Column 3856: NET-enabling start-tag requires SHORTTAG YES

     …>νιℓ єиgℓαи∂ иινя ѕι αgєи<br/>try<br/><a href="http://disdroid.co.uk" target=

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

118. Line 1266, Column 3989: NET-enabling start-tag requires SHORTTAG YES

     …r="ltr">http://disdroid.co.uk</a><br/>for breaking news

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

119. Line 1272, Column 41: NET-enabling start-tag requires SHORTTAG YES

     			the only way to beat the b*stards <br/>is by being an even bigger B*STARD !

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

120. Line 1343, Column 18: Attribute "NAME" is not a valid attribute. Did you mean "name"?

     					(<span name="channel-box-item-count">176</span>)

     ✉

     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.

121. Line 1362, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i1.ytimg.com/i/PJXfmxMYAoH02CFudZxmgg/1.jpg" alt="Gol

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

122. Line 1383, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i3.ytimg.com/i/baagNfk8Q4e2kBTm4F9I_Q/1.jpg?v=7bd2a4"

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

123. Line 1404, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i4.ytimg.com/i/WVHp0gy7Vm9erlxuUqvzBQ/1.jpg?v=79a1b6"

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

124. Line 1425, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i2.ytimg.com/vi/I_VOeUog7zU/default.jpg" alt="krulls…

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

125. Line 1446, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i3.ytimg.com/i/jW5A1u_qhn03vQXjGhBYwA/1.jpg" alt="eye

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

126. Line 1467, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i1.ytimg.com/vi/pmJFVN-vlLw/default.jpg" alt="SuperCa

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

127. Line 1488, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i3.ytimg.com/i/vdi74K1MwsuHqmV62ePWsA/1.jpg?v=7ba06e"

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

128. Line 1509, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i3.ytimg.com/i/FrH7bkCdKK9WrezHmn9JuA/1.jpg" alt="twa

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

129. Line 1530, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i3.ytimg.com/i/RmHgjBzqIMAjfYxOuQkXRQ/1.jpg" alt="Run

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

130. Line 1541, Column 31: NET-enabling start-tag requires SHORTTAG YES

     				I like this channel :-)<br/>Have a great day!<br/>xoxo<br/>Runae

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

131. Line 1541, Column 54: NET-enabling start-tag requires SHORTTAG YES

     				I like this channel :-)<br/>Have a great day!<br/>xoxo<br/>Runae

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

132. Line 1541, Column 63: NET-enabling start-tag requires SHORTTAG YES

     …e this channel :-)<br/>Have a great day!<br/>xoxo<br/>Runae

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

133. Line 1598, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i2.ytimg.com/vi/5n438GBkQOg/default.jpg" alt="madcyri

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

134. Line 1607, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i1.ytimg.com/vi/xVH_Rtn68ro/default.jpg" alt="reedski

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

135. Line 1616, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i4.ytimg.com/vi/SVTYbPbEGkw/default.jpg" alt="debdazz

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

136. Line 1625, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i3.ytimg.com/i/rfb9YbopAVX60poLkiaNfw/1.jpg?v=7639c7"

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

137. Line 1634, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i2.ytimg.com/i/aZaXg7VhnkJKztRO186ymw/1.jpg?v=743c05"

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

138. Line 1643, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i2.ytimg.com/vi/-HT5ks2OsTw/default.jpg" alt="lukepie

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

139. Line 1652, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://s.ytimg.com/yt/img/no_videos_140-vfl121214.png" alt="

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

140. Line 1695, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i3.ytimg.com/i/rfb9YbopAVX60poLkiaNfw/1.jpg?v=7639c7"

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

141. Line 1704, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://s.ytimg.com/yt/img/no_videos_140-vfl121214.png" alt="

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

142. Line 1713, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i2.ytimg.com/vi/Ywy4iABlopQ/default.jpg" alt="michael

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

143. Line 1722, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://s.ytimg.com/yt/img/no_videos_140-vfl121214.png" alt="

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

144. Line 1731, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i1.ytimg.com/vi/Twr15Kn65NQ/default.jpg" alt="SynEcd0

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

145. Line 1740, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i2.ytimg.com/vi/Uj87yXaPyHk/default.jpg" alt="BEATOFT

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

146. Line 1749, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i1.ytimg.com/vi/HC9jTMIx-eU/default.jpg" alt="tpban…

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

147. Line 1758, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i1.ytimg.com/vi/Thp46olQz3M/default.jpg" alt="Hectorz

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

148. Line 1767, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i1.ytimg.com/vi/lEVWAnJVw4M/default.jpg" alt="Facez0f

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

149. Line 1776, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i4.ytimg.com/vi/GqQFTGg1tBw/default.jpg" alt="razelm…

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

150. Line 1785, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i4.ytimg.com/vi/csa3x4Pnymg/default.jpg" alt="FableFo

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

151. Line 1794, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i2.ytimg.com/vi/99vdVgWz9dw/default.jpg" alt="arrowso

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

152. Line 1803, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i4.ytimg.com/vi/WCEii6tW6hY/default.jpg" alt="Cinemat

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

153. Line 1812, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i2.ytimg.com/vi/5n438GBkQOg/default.jpg" alt="madcyri

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

154. Line 1821, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i2.ytimg.com/vi/yLV0o4rM_4s/default.jpg" alt="huddsdi

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

155. Line 1830, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i4.ytimg.com/vi/s8unuoRRpiw/default.jpg" alt="bossSE7

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

156. Line 1839, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i4.ytimg.com/vi/C0O15aCILfg/default.jpg" alt="brazens

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

157. Line 1848, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i1.ytimg.com/vi/xVH_Rtn68ro/default.jpg" alt="reedski

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

158. Line 1857, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i4.ytimg.com/vi/SVTYbPbEGkw/default.jpg" alt="debdazz

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

159. Line 1866, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i2.ytimg.com/vi/URW-3HSp8X4/default.jpg" alt="g0dzW0r

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

160. Line 1875, Column 14: syntax of attribute value does not conform to declared value

         <img id="" src="http://i3.ytimg.com/i/6B8yR34e5X3gpf7QJcwaSA/1.jpg" alt="Den

     ✉

     The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.