Here I'm with CoffeeCup HTML Editor 2007!
That is all by CoffeeCup. What I don't find ready in the editor to obtain a page that passes immediately the validation.
With only two elements the Editor can produce from the beginning an excellent page. Look at the two elements that are missing: character and language.
This is the result from the first attempt to overcome the validation.
Tentatively passed validation, 1 warning:
No Character Encoding Found! Falling back to UTF-8.
None of the standards sources gave any information on the character encoding labeling for this document. Without encoding information it is impossible to reliably validate the document. As a fallback solution, the "UTF-8" encoding was used to read the content and attempt to perform the validation, but this is likely to fail for all non-trivial documents.
The uploaded document "ingen.html" was checked and found to be tentatively valid HTML 4.0 Transitional. This means that with the use of some fallback or override mechanism, we successfully performed a formal validation using an SGML or XML Parser. In other words, the document would validate as HTML 4.0 Transitional if you changed the markup to match the changes we have performed automatically, but it will not be valid until you make these changes.
No Character Encoding Found!
An HTML document should be served along with its character encoding.
Specifying a character encoding is typically done by the web server configuration, by the scripts that put together pages, and inside the document itself. IANA maintains the list of official names for character encodings (called charsets in this context). You can choose from a number of encodings, though we recommend UTF-8 as particularly useful.
The W3C I18N Activity has collected a few tips on how to do this.
To quickly check whether the document would validate after addressing the missing character encoding information, you can use the "Encoding" form control (accesskey "2") earlier in the page to force an encoding override to take effect. "iso-8859-1" (Western Europe and North America) and "UTF-8" (Universal, and more commonly used in recent documents) are common encodings if you are not sure what encoding to choose.
For HTML or XHTML served as HTML, you should always use the <meta> tag inside <head>. Example:
<meta http-equiv= . . . . charset=utf-8" >
And at last the page passed validation:
Last updated Friday, December 14, 2007, 00:10 pm
Here is the result of the page with the mere mention of its language. With a small addition you get a good result. And now this page complies with all of the automatic checkpoints of the W3C Web Content Accessibility Guidelines. However, it does not comply with all of the manual checkpoints, and requires manual verification. Go, validate and observe the result!