Moin Leute,
als ich heute meinen Blog aufgesetzt habe musste ich durch den W3 Validator leider feststellen, dass dieser viele Fehler enthält.
Jetzt meine Frage an euch: Wie bekomme ich diese doch sehr zahlreichen Fehler weg und wo finde ich die Datei(en), die ich bearbeiten muss?
Programmiersprachen kann ich leider keine.
Bin also auf eure Hilfe angewiesen, Danke schonmal im Voraus! : )
[ol]
[li] http://validator.w3.org/images/info_icons/error.png Line 5, Column 71: end tag for „meta“ omitted, but OMITTAG NO was specified <meta name=„viewport“ content=„width=device-width; initial-scale=1.0“> 
[/li] You may have neglected to close an element, or perhaps you meant to „self-close“ an element, that is, ending it with „/>“ instead of „>“.
[li] http://validator.w3.org/images/info_icons/info.png Line 5, Column 1: start tag was here <meta name=„viewport“ content=„width=device-width; initial-scale=1.0“>[/li][li] http://validator.w3.org/images/info_icons/error.png Line 27, Column 90: required attribute „type“ not specified …www.alltagsnews.de/wp-content/themes/itheme2/js/css3-mediaqueries.js"> [/li] 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 and type=„text/javascript“ for .
[li] http://validator.w3.org/images/info_icons/error.png Line 67, Column 7: required attribute „type“ not specified <style> .recentcomments a{display:inline !import… [/li] 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 and type=„text/javascript“ for .
[li] http://validator.w3.org/images/info_icons/warning.png Line 178, Column 19: character „&“ is the first character of a delimiter but occurred as data !window.jQuery && document.write('<script type=„text/javascript“ src="http:/… [/li] This message may appear in several cases:
[ul]
[li]You tried to include the „<“ character in your page: you should escape it as „<“[/li][li]You used an unescaped ampersand „&“: this may be valid in some contexts, but it is recommended to use „&“, which is always safe.[/li][li]Another possibility is that you forgot to close quotes in a previous tag.[/li][/ul]
[li] http://validator.w3.org/images/info_icons/warning.png Line 178, Column 20: character „&“ is the first character of a delimiter but occurred as data !window.jQuery && document.write('<script type=„text/javascript“ src="http:/… [/li] This message may appear in several cases:
[ul]
[li]You tried to include the „<“ character in your page: you should escape it as „<“[/li][li]You used an unescaped ampersand „&“: this may be valid in some contexts, but it is recommended to use „&“, which is always safe.[/li][li]Another possibility is that you forgot to close quotes in a previous tag.[/li][/ul]
[li] http://validator.w3.org/images/info_icons/error.png Line 178, Column 147: document type does not allow element „script“ here …www.alltagsnews.de/wp-content/themes/itheme2/themify/js/jquery.js"></script>‚) [/li] 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).
[li] http://validator.w3.org/images/info_icons/warning.png Line 178, Column 148: character „<“ is the first character of a delimiter but occurred as data …www.alltagsnews.de/wp-content/themes/itheme2/themify/js/jquery.js"></script>‘) [/li] This message may appear in several cases:
[ul]
[li]You tried to include the „<“ character in your page: you should escape it as „<“[/li][li]You used an unescaped ampersand „&“: this may be valid in some contexts, but it is recommended to use „&“, which is always safe.[/li][li]Another possibility is that you forgot to close quotes in a previous tag.[/li][/ul]
[li] http://validator.w3.org/images/info_icons/error.png Line 180, Column 33: document type does not allow element „script“ here <script type=‚text/javascript‘> [/li] 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).
[li] http://validator.w3.org/images/info_icons/error.png Line 191, Column 31: document type does not allow element „script“ here <script type=‚text/javascript‘> [/li] 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).
[/ol]
