blog won’t validate
-
At the link below you’ll see all the errors. What can I do to change it?
Markup Validation Servicev0.7.3
Skip Navigation | Home About… News Docs Help & FAQ Feedback
Jump To:
Results
Result: Failed validation, 11 errors
Address:
Encoding: utf-8 (detect automatically) utf-8 (Unicode, worldwide) utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European) iso-8859-5 (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew, visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-11 (Latin/Thai) iso-8859-13 (Latin 7, Baltic Rim) iso-8859-14 (Latin 8, Celtic) iso-8859-15 (Latin 9) iso-8859-16 (Latin 10) us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian) iso-ir-111 (Cyrillic KOI-8) macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)
Doctype: XHTML 1.1 (detect automatically) XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset HTML 3.2 HTML 2.0 ISO/IEC 15445:2000 (“ISO HTML”) XHTML 1.1 XHTML Basic 1.0 XHTML-Print 1.0 XHTML 1.1 plus MathML 2.0 XHTML 1.1 plus MathML 2.0 plus SVG 1.1 MathML 2.0 SVG 1.0 SVG 1.1 SVG 1.1 Tiny SVG 1.1 Basic SMIL 1.0 SMIL 2.0
Root Namespace: https://www.w3.org/1999/xhtml
Revalidate With Options: Show Source Verbose Output
Validate error pagesHelp on the options is available.
Note: The Validator XML support has some limitations.
This page is not Valid XHTML 1.1!
Below are the results of checking this document for XML well-formedness and validity.Error Line 9 column 11: there is no attribute “name”.
<META name=”verify-v1″ content=”7oycLsOAcX1aSppJoydGANPg1yRe86cLcWhvoW9v55k=” .
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.
?
Error Line 9 column 31: there is no attribute “content”.
<META name=”verify-v1″ content=”7oycLsOAcX1aSppJoydGANPg1yRe86cLcWhvoW9v55k=” .
?Error Line 9 column 80: element “META” undefined.
…aSppJoydGANPg1yRe86cLcWhvoW9v55k=” />
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 “Frameset” document type to get the “<frameset>” element),
by using vendor proprietary extensions such as “<spacer>” or “<marquee>” (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case.?
Error Line 184 column 603: required attribute “alt” not specified.
…i100/erika_conn/Creative/spirit_in_pond.jpg” /></p>
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>.
?
Error Line 185 column 88: required attribute “alt” not specified.
…/erika_conn/Creative/verticals.jpg” /><a href=”https://i70.photobucket.com/alb
?Error Line 185 column 399: end tag for “a” omitted, but OMITTAG NO was specified.
…?I had a late night and early morning.</p>
You may have neglected to close an element, or perhaps you meant to “self-close” an element, that is, ending it with “/>” instead of “>”.?
Info Line 185 column 174: start tag was here.
…erika_conn/Creative/verticals.jpg” /><a href=”https://i70.photobucket.com/albu
Error Line 186 column 6: end tag for element “a” which is not open.
<p>
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 occured in a script section of your document, you should probably read this FAQ entry.
?
Error Line 326 column 125: required attribute “alt” not specified.
…/randomimages/rotate.php” width=”46%”>
?Error Line 326 column 129: end tag for “img” omitted, but OMITTAG NO was specified.
…domimages/rotate.php” width=”46%”>
?Info Line 326 column 16: start tag was here.
<img src=”https://www.ceconn.com/canwetalk/wp-content/themes/andr
Error Line 327 column 125: required attribute “alt” not specified.
…/randomimages/random.php” width=”46%”>
?Error Line 327 column 129: end tag for “img” omitted, but OMITTAG NO was specified.
…domimages/random.php” width=”46%”>
?Info Line 327 column 16: start tag was here.
<img src=”https://www.ceconn.com/canwetalk/wp-content/themes/andr
The W3C Validator Team
- The topic ‘blog won’t validate’ is closed to new replies.