Re: Nu HTML Checker - Version: 18.4.19

"Dixon, Elizabeth" <Elizabeth.Dixon@ros.gov.uk>, 2018-04-26 09:30 +0000:
> Archived-At: <https://www.w3.org/mid/4ef863d677ed4426a442d1514561c6da@ros.gov.uk>
> 
> The downloaded Nu markup tool (sourced from the Paciello Group) was used
> to validate markup.

Please provide the web URL for the document that was checked. It’s
otherwise pretty impossible to help you.

And to be clear, it’s not sufficient to just be looking at the server-side
code that generates the document (if it’s coming from a CMS or whatever).
Instead you need to look at what the server is sending back over the wire
when it responds to the request from the checker.

If you tick the Show: source checkbox in the checker Web UI, the checker
itself will display back to you exactly the source of the document it’s
receiving from your server.

> The following errors were reported when not expected:
> 
>   1.  Error: The character encoding was not declared. Proceeding using windows-1252.

What’s unexpected about that message? It indicates that the document was
served without a charset parameter in the Content-Type header, and without
a <meta> element in the document itself that specifies the character set.

>   2.  Error: End of file seen without seeing a doctype first. Expected <!DOCTYPE html>.

What’s unexpected about that? It indicates the document lacks the required
<!DOCTYPE html> doctype declaration. Make <!DOCTYPE html> the first line of
the document, and you won’t get that error.

>   3.  Error: Element head<http://www.w3.org/html/wg/drafts/html/master/single-page.html#the-head-element> is missing a required instance of child element title.

? The document has no <title> element. It needs one..

>   4.  Warning: Consider adding a lang attribute to the html start tag to declare the language of this document.

Change the <html> element to <html lang=en>

> I've checked through the code and the code looks good.

It’s not good

> A developer has also checked the code and has confirmed it is correct.

That developer is wrong. You probably consider find somebody else to look at it 

> It uses lowercase for doctype and utf and as far as I am aware HTML is
> case insensitive.
> Can you investigate at your end?

There’s nothing anybody else can do to help you without having the actual
URL for the document you’re giving to the checker

-- 
Michael[tm] Smith https://people.w3.org/mike

Received on Thursday, 3 May 2018 07:24:59 UTC