Veb.net W3C HTML Markup Validation
HTML markup errors and warnings
(Rescan now...)
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”.
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.
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Element “form” not allowed as child of element “span” in this context. (Suppressing further errors from this subtree.)
Attribute “ng-app” not allowed on element “div” at this point.
Attribute “ng-controller” not allowed on element “div” at this point.
Attribute “ng-cloak” not allowed on element “ul” at this point.
Attribute “ng-repeat” not allowed on element “li” at this point.
Bad value “{{item.detailsPageUrl}}” for attribute “href” on element “a”: Illegal character in path segment: “{” is not allowed.
Attribute “alt” not allowed on element “a” at this point.
Duplicate attribute “class”.
Warnings:
Consider avoiding viewport values that prevent users from resizing documents.
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.
Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.
Netherlands NL