Errors:
A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.
Bad value “imagetoolbar” for attribute “http-equiv” on element “meta”.
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Self-closing syntax (“/>”) used on a non-void HTML element. Ignoring the slash and treating as a start tag.
Element “div” not allowed as child of element “span” in this context. (Suppressing further errors from this subtree.)
Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)
Attribute “href” not allowed on element “p” at this point.
The “font” element is obsolete. Use CSS instead.
Bad value “40px” for attribute “height” on element “img”: Expected a digit but saw “p” instead.
Element “style” not allowed as child of element “main” in this context. (Suppressing further errors from this subtree.)
Element “style” not allowed as child of element “section” in this context. (Suppressing further errors from this subtree.)
Duplicate ID “homepage”.
Duplicate attribute “data-slick”.
Element “p” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)
No “p” element in scope but a “p” end tag seen.
The “aria-labelledby” attribute must point to an element in the same document.
Warnings:
The “type” attribute is unnecessary for JavaScript resources.
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
The “type” attribute for the “style” element is not needed and should be omitted.
The first occurrence of ID “homepage” was here.
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).
Germany DE