Check Accessibility, HTML, CSS, Broken Links & Spelling

E0

This page was not tested as it appeared to contain a binary file

One or more characters were discovered which appear to mean that the file is a binary file and not a web page or CSS file.

E0

Page didn't contain anything to validate

The page appears to be empty or doesn't contain any HTML tags. If this is a CSS page then you may have forgotten to select the CSS Level.

E1

There is either a > missing or you may have used < instead of < in the content

A > character was expected but was not found. Sometimes this error appears when you have mismatched quotes, but more often it is caused by using a < character in the text. The < character should only be used to start a new tag. Within text you should use the character reference < instead.

E2

There is either a < missing or you may have used > instead of > in the content

A < character was expected but was not found. Sometimes this error appears when you have mismatched quotes, but more often it is caused by using a > character in the text. The > character should only be used to end a tag. Within text you should use the character reference > instead.

E3

There is either an extra < or you may have used < instead of < in the content

A < character was found in an unexpected place. This is often caused by using a < character in the text. The < character should only be used to start a new tag. Within text you should use the character reference < instead.

E4

There is either an extra > or you may have used > instead of > in the content

A > character was found in an unexpected place. This is often caused by using a > character in the text. The > character should only be used to end a tag. Within text you should use the character reference > instead.

E5

Extra quote character found or quote character missing

There is either an unnecessary extra single or double quote character or there is a missing quote. This may be caused by putting single or double quote characters within quoted text e.g. "Mary said "hello" to her friends". In this case you should replace the quote character with the character reference equivalent. For example, "Mary said "hello" to her friends". Note that this error may cause several others to appear that can all be fixed by correcting this issue. See HTML5 Attributes. For earlier HTML versions see HTML 4.01 Attributes.

E61

The ATTRIBUTE NAME's value is missing

It appears that you have specified an attribute name but not supplied the attribute's value. If the value does appear to be present then this error may have been caused by a badly formatted tag possibly with single or double quotes in the wrong place or even mismatched.

E62

The attribute's value is missing

It appears that you have specified an attribute name but not supplied the attribute's value. If the value does appear to be present then this error may have been caused by a badly formatted tag possibly with single or double quotes in the wrong place or even mismatched.

E7

Found &. You should use & instead

You should not use the & character within attribute values as this may be confused with the start of character references. This error may also appear if you used a character reference but did not terminate it with a semicolon. Only the first issue in the attribute will be marked, so look out for others.

E8

Found invalid character reference

A character entity reference was found in an attribute that is not defined as part of the HTML specification being tested against. This error may be caused by using an & character when no character reference was intended, in which case use & instead. It may also be caused by specifying an invalid numeric reference containing non-numeric characters.

E9

Invalid characters found in attribute's value starting at character: INDEX

It is good practice to always put quotes around an attribute's value. But if you do not use quotes then you are not allowed to use white space characters, nor control characters, nor ", ', =, <, >, /, and `. See HTML5 Attributes.

E10

Unrecognised or malformed <!DOCTYPE> tag (if "auto-detecting" then a best-fit <!DOCTYPE> will be used)

Common reasons for this error are a misspelt declaration, the wrong case used (the declaration is case-sensitive), or an incomplete declaration. See Recognised Doctypes.

E11

Found & within content without a terminating ';'

You should not use the & character within content as this may be confused with the start of character references. You should use & instead.

E12

Found invalid character reference

A character entity reference was found that is not defined as part of the HTML specification being tested against. This error may be caused by using an & character when no character reference was intended, in which case use & instead. It may also be caused by specifying an invalid numeric reference containing non-numeric characters.

E13

Badly defined self-closing tag

A self-closing tag should end with />. There should be no whitespace between the '/' and the > characters. Note that in the report this extra whitespace will have been removed for you, so you need to consult the original source.

E14

Found & within content without a terminating ';'

This error typically appears if you used a character reference but did not terminate it with a semicolon.

E15

Found 'X' within character entity reference

This error appears if you used a hexadecimal entity reference with a capital 'X'. In XHTML you must use a lowercase 'x'. See XHTML 1.0 Entity References.

E16

The ATTRIBUTE NAME attribute is duplicated

It appears that you have specified two attributes with the same case-insensitive name. The second attribute will normally be ignored but this cannot be guaranteed.

E17

There appears to be a badly formed comment here (real comment is not displayed)

Most browsers can cope with badly formed comments but some robots may not. So, it pays to define comments correctly to ensure your site is indexed properly. See HTML5 Comments. For other versions of HTML see HTML 4.01 Comments.

E18

There appears to be a badly formed CDATA section on this line (only start of section shown)

The end of the CDATA section could not be found.

E19

There appears to be a badly formed comment here (real comment is not displayed)

Most browsers can cope with badly formed comments but some robots may not. So, it pays to define comments correctly to ensure your site is indexed properly. See HTML5 Comments.

E20

No matching start tag found

There are two common causes of this error. Either you have forgotten the start tag, or you may have tags that are improperly nested. For example, <b><i></b></i>

E21

Empty tag

This error may be caused by inadvertently using < and > characters together in the text rather than representing these characters using < and > instead

E22

Attributes are not allowed in end tags

End tags cannot have attributes. You may have inadvertently added a '/' character at the beginning of a tag by mistake.

E23

An attribute name is missing

It appears that you have specified an attribute value but not supplied the attribute's name. This tends to indicate a badly formatted tag possibly with single or double quotes in the wrong place or mismatched. Check that there are no extra or missing quote characters.

E24

Extra '/' character found within tag

A '/' character was found at the start of a tag and at the end of a tag. One of the two '/' characters should be removed.

E27

Found character that is not allowed in the character set

The character set being used to read the page does not support the character you are trying to use. Either replace the character with one that is valid, or change the character set to one that supports it. Note that the character shown in the results may not be the original.

E28

Unrecognised reserved name - possibly an invalid conditional comment

Most browsers can cope with invalid tags but some robots may not. It pays to use valid tags to ensure your site is indexed properly. If you are using a Microsoft downlevel-revealed conditional comment, try converting this to a downlevel-hidden conditional comment by hiding it within a <!-- comment -->

E29

Found BOM at start of document that conflicts with the content-type HTTP header

The page starts with a Byte Order Mark (BOM) that is different to the character encoding specified in the content-type HTTP header. The HTTP header information always takes precedence and this may cause the entire document to be full of errors.

W1

There should not be any white space at the start or end of an attribute's value

There should not be any white space at the start or end of an attribute's value. This is a minor issue and can probably be ignored. See HTML 4.01 SGML basic types.

W3

Comments should not contain two or more '-' characters (real comment is not displayed)

Most browsers can cope with badly formed comments but some robots may not. So, it pays to define comments correctly to ensure your site is indexed properly. See HTML 4.01 Comments.