Dani Iswara .Net

Failed on Validome-XHTML Validation

Although they got (really) “valid XHTML” status from W3C Markup Validator (not only text / button / banner), some failed on validome.org validation.
From the List of Valid XHTML Sites, I found most of websites and weblogs only have simple errors/remarks/warnings. I guess the (validome) validation result pages were clearly defined.

Some documentations (slightly edited):

1. MIME-type problem

Remarks

This XHTML 1.0 document was delivered with MIME-Type text/html. This MIME-Type should not be used, if the document does not correspond to the HTML Compatibility Guidelines (for XHTML 1.0).

This XHTML 1.1-Document was delivered with the MIME-Type “text/html“, what is not recommended.
Please change the MIME-Type in the HTTP-Header (Content-Type=xxx) to “application/xhtml+xml“.

It clear enough but there are several advance solutions, I guess.
Don’t ask me..I’m beginner, not a web developer/designer/programmer..

2. Encoding declaration problem

Warnings

No encoding declaration found within this XHTML document.
However the validator found a Meta element containing some information concerning encoding (utf-8).
This kind of encoding declaration will be not processed within XHTML documents, it is useful for downward compatibility to HTML.
Please add either a XML declaration containing a encoding information at the very beginning of your document (z. B. <?xml version="1.0" encoding="utf-8"?>, or prompt your server to send an appropriate HTTP-Header (example for PHP users: header('Content-Type: text/html; charset=utf-8');).
As no valid encoding declaration found, your document was processed via fallback to UTF-8.

Clear enough. Add an XML declaration or server side script.

3. Link warnings

On Strict DOCTYPE, e.g. :

The Link “#search” points to a not existing Anchor.

Add “slash”, e.g. /#search (relative URL).

The Link “#sidebar” points to a not existing Anchor.

Link better using e.g. /#sidebar (relative URL).

4. META problem

Error

When using style attributes, you must specify the style language within a META element
(<meta http-equiv="Content-Style-Type" content="text/css" />) and/or within HTTP-Header (Content-Style-Type: text/css).
Here you can find more informations.

Error Position: <... style="...">

Just need to add that meta.

Error

When using embedded events (Event-Handler), script language must be specified within Meta-Tag (<meta http-equiv="Content-Script-Type" content="text/javascript" />) or HTTP-Header (Content-Script-Type: text/javascript).

Add the meta will solve problem.
So we can use inline script legally, e.g. :

Error Position: <onclick="...">

Error Position: <onfocus="...">

5. Attribute problem

Error

Invalid value “…px” in attribute “width” (and “height“).
Only integer or percentage values (e.g. 10%) are allowed.

Delete px, so it’s become e.g. width="80" and/or height="31".