Divami.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 “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.
Attribute “pagename” not allowed on element “a” at this point.
Element “div” not allowed as child of element “span” in this context. (Suppressing further errors from this subtree.)
Element “div” not allowed as child of element “a” in this context. (Suppressing further errors from this subtree.)
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Element “div” not allowed as child of element “button” in this context. (Suppressing further errors from this subtree.)
Bad value “https://www.googletagmanager.com/gtag/js?id= UA-18464216-4” for attribute “src” on element “script”: Illegal character in query: space is not allowed.
The value of the “for” attribute of the “label” element must be the ID of a non-hidden form control.
Warnings:
Consider avoiding viewport values that prevent users from resizing documents.
The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.
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).
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
The “type” attribute is unnecessary for JavaScript resources.
India IN