Errors:
X-UA-Compatible HTTP header must have the value “IE=edge”, was “IE=Edge,chrome=1”.
The “profile” attribute on the “head” element is obsolete. To declare which “meta” terms are used in the document, instead register the names as meta extensions. To trigger specific UA behaviors, use a “link” element instead.
A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.
Element “span” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)
Bad value “06/26/2019” 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 “06/19/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “05/09/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “04/12/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “04/05/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “03/28/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “03/26/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “03/25/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “03/13/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “03/08/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “02/25/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “11/14/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “10/18/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “09/28/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “09/27/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “09/17/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “09/03/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “06/21/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “05/28/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “04/27/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “03/23/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “03/08/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “03/07/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “03/06/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad character “<” after “<”. Probable cause: Unescaped “<”. Try escaping it as “<”.
Warnings:
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).