Exxonmobil.com W3C HTML Markup Validation
HTML markup errors and warnings
(Rescan now...)
Errors:
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.
A document must not include more than one “meta” element with a “charset” attribute.
Bad value “” for attribute “target” on element “a”: Browsing context name must be at least one character long.
“=” in an unquoted attribute value. Probable causes: Attributes running together or a URL query string in an unquoted attribute value.
Bad value “\#\” for attribute “href” on element “a”: Backslash ("\") used as path segment delimiter.
Element “p” not allowed as child of element “span” in this context. (Suppressing further errors from this subtree.)
Element “p” not allowed as child of element “h2” in this context. (Suppressing further errors from this subtree.)
No “p” element in scope but a “p” end tag seen.
Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)
Element “img” is missing required attribute “src”.
The element “footer” must not appear as a descendant of the “footer” element.
Warnings:
Consider avoiding viewport values that prevent users from resizing documents.
The “button” role is unnecessary for element “button”.
The “type” attribute is unnecessary for JavaScript resources.
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.
United States US