Errors:
Attribute “xmlns:fb” not allowed here.
Attribute “xmlns:addthis” not allowed here.
Attribute “xmlns:og” not allowed here.
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 “true” for attribute “async” on element “script”.
Element “script” must not have attribute “async” unless attribute “src” is also specified or unless attribute “type” is specified with value “module”.
Element “style” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)
Attribute “onpaste” not allowed on element “input” at this point.
Bad value “” for attribute “name” on element “input”: Must not be empty.
Bad value “” for attribute “id” on element “input”: An ID must not be the empty string.
Stray end tag “img”.
Bad value “false” for attribute “novalidate” on element “form”.
No space between attributes.
Bad value “01/03/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “11/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “15/02/2019 17:11:08” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “28/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “27/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “13/02/2019 16:40:21” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
End tag “aside” seen, but there were open elements.
Unclosed element “div”.
Bad value “26/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “22/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “21/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “20/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Bad value “19/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “18/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “17/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “16/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “14/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “12/02/2019 00:00:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Attribute “aria-required” not allowed on element “input” at this point.
Attribute “required” is only allowed when the input type is “checkbox”, “date”, “datetime-local”, “email”, “file”, “month”, “number”, “password”, “radio”, “search”, “tel”, “text”, “time”, “url”, or “week”.
The value of the “for” attribute of the “label” element must be the ID of a non-hidden form control.
Warnings:
Attribute with the local name “xmlns:fb” is not serializable as XML 1.0.
Attribute with the local name “xmlns:addthis” is not serializable as XML 1.0.
Attribute with the local name “xmlns:og” is not serializable as XML 1.0.
Consider avoiding viewport values that prevent users from resizing documents.
The “type” attribute is unnecessary for JavaScript resources.
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).
France FR