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.
Bad value “X-UA-TextLayoutMetrics” for attribute “http-equiv” on element “meta”.
Bad value “cleartype” for attribute “http-equiv” on element “meta”.
Bad value “” for attribute “href” on element “link”: Must be non-empty.
Bad value “https://fonts.googleapis.com/css?family=Lato:300,400,900|Open+Sans:400,700” for attribute “href” on element “link”: Illegal character in query: “|” is not allowed.
Bad value “https://github.com/WP-API/WP-API” for attribute “rel” on element “link”: The string “https://github.com/WP-API/WP-API” is not a registered keyword.
Bad value “navigation” for attribute “role” on element “ul”.
Element “div” not allowed as child of element “button” 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.
Attribute “rotator-direction” not allowed on element “div” at this point.
Stray end tag “spancl”.
End tag “button” seen, but there were open elements.
Unclosed element “span”.
Element “img” is missing required attribute “src”.
The “label” element may contain at most one “button”, “input”, “meter”, “output”, “progress”, “select”, or “textarea” descendant.
No “p” element in scope but a “p” end tag seen.
Stray end tag “div”.
The “aria-controls” attribute must point to an element in the same document.
The “itemprop” attribute was specified, but the element is not a property of any item.
Warnings:
Consider avoiding viewport values that prevent users from resizing documents.
The “banner” role is unnecessary for element “header”.
The “navigation” role is unnecessary for element “nav”.
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).
Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.
“label” element with multiple labelable descendants.
The “contentinfo” role is unnecessary for element “footer”.
Russian Federation RU