Errors:
Obsolete doctype. Expected “<!DOCTYPE html>”.
Bad value “//www.w3.org/1999/xhtml” for the attribute “xmlns” (only “http://www.w3.org/1999/xhtml” permitted here).
A document must not include both a “meta” element with an “http-equiv” attribute whose value is “content-type”, and a “meta” element with a “charset” attribute.
Bad start tag in “img” in “head”.
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Stray end tag “noscript”.
Element “style” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)
Stray end tag “head”.
Start tag “body” seen but an element of the same type was already open.
Element “style” not allowed as child of element “section” in this context. (Suppressing further errors from this subtree.)
CSS: Parse Error.
CSS: “position”: Too many values or values are not recognized.
Element “div” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)
The element “button” must not appear as a descendant of the “a” element.
The “align” attribute on the “div” element is obsolete. Use CSS instead.
End tag “div” seen, but there were open elements.
Unclosed element “span”.
Attribute “align” not allowed on element “section” at this point.
The “align” attribute on the “h2” element is obsolete. Use CSS instead.
Text not allowed in element “ul” in this context.
Element “br” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)
The “align” attribute on the “h1” element is obsolete. Use CSS instead.
The “align” attribute on the “img” element is obsolete. Use CSS instead.
Warnings:
Attribute “xmlns” is not serializable as XML 1.0.
The “type” attribute is unnecessary for JavaScript resources.
The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).
United States US