Errors found while checking this document as HTML5!

Result: 3 Errors, 2 warning(s)
:
: utf-8
: HTML5
Root Element: html
Options

Help on the options is available.

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

  1. Info Using experimental feature: HTML5 Conformance Checker.

    The validator checked your document with an experimental feature: HTML5 Conformance Checker. This feature has been made available for your convenience, but be aware that it may be unreliable, or not perfectly up to date with the latest development of some cutting-edge technologies. If you find any issues with this feature, please report them. Thank you.

↑ Top

Validation Output: 3 Errors

  1. Error Line 5, Column 70: A meta element with an http-equiv attribute whose value is X-UA-Compatible must have a content attribute with the value IE=edge. 
            <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">

    ✉

  2. Error Line 48, Column 132: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images. 
    …dfront.net/images/homepage/bora/img_screen_02.png" width="1106" height="588" />

    ✉

  3. Error Line 57, Column 67: & did not start a character reference. (& probably should have been escaped as &amp;.) 
    …ref="/signin?funnel=homepage_2014Dec04&entryGUID=55454c34a70b9" class="signIn"…

    ✉

  4. Warning Line 80, Column 117: Document uses the Unicode Private Use Area(s), which should not be used in publicly exchanged documents. (Charmod C073) 
    …expensify" target="_blank"><span class="iconButton">&#xe002;</span></a> &nbsp;

    ✉

↑ Top