High Quality
Open the downloaded document, and select print from the file menu (PDF reader required).
16/06/09 13:45[Invalid] Markup Validation of http://www.saludinforma.es/start.htm - W3C Markup ValidatorPágina 1 de 8http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654
Helpon the options is available.
Revalidate
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Jump To:
Notes and Potential Issues Validation Output
Errors found while checking this document as HTML 4.01Transitional!
Result:
16 Errors, 26 warning(s)
Address:
http://www.saludinforma.es/start.htm
Encoding:
iso-8859-1
(detect automatically)
Doctype:
HTML 4.01 Transitional
(detect automatically)
Root Element:
htmlThe W3C validators rely on community support for hosting anddevelopment.
Donate
and help us build better tools for a better web.
Options
Group ErrorMessages by TypeValidate error pagesVerbose OutputClean up Markup with HTML Tidy
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information whichcaused the validator to perform some guesswork prior to validation. If the guess orfallback 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-validatethe document.
Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types such asXHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document,the information available was not sufficient to determine the parsing modeunambiguously, because:the MIME Media Type (
text/html
) can be used for XML or SGMLdocument typesNo known Document Type could be detectedNo XML declaration (e.g
<?xml version="1.0"?>
) could be found at thebeginning of the document.No XML namespace (e.g
<html xmlns="http://www.w3.org/1999/xhtml"xml:lang="en">
) could be found at the root of the document.As a default, the validator is falling back to SGML mode.
No
DOCTYPE
found! Checking with default HTML 4.01 Transitional DocumentType.
No DOCTYPE Declaration could be found or recognized in this document. Thisgenerally means that the document is not declaring its Document Type at the top. Itcan also mean that the DOCTYPE declaration contains a spelling error, or that it isnot using the correct syntax.The document was checked using a default "fallback" Document Type Definition thatclosely resembles “HTML 4.01 Transitional”.Learnhow to add a doctype to your documentfrom our FAQ.
16/06/09 13:45[Invalid] Markup Validation of http://www.saludinforma.es/start.htm - W3C Markup ValidatorPágina 2 de 8http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654
Character Encoding mismatch!
The character encoding specified in the HTTP header (
iso-8859-1
) is different fromthe value in the
<meta>
element (
iso-8859-15
). I will use the value from the HTTPheader (
iso-8859-1
) for this validation.
!
TOP
Validation Output: 16 Errors
Line 7, Column 1
:
no document type declaration; implying "<!DOCTYPEHTML SYSTEM>"
<
html lang="es-ES">
The checked page did not contain a document type ("DOCTYPE") declaration. TheValidator has tried to validate with a fallback DTD, but this is quite likely to be incorrectand will generate a large number of incorrect error messages. It is highly recommendedthat you insert the proper DOCTYPE declaration in your document -- instructions fordoing this are given above -- and it is necessary to have this declaration before thepage can be declared to be valid.
Line 10, Column 75
:
NET-enabling start-tag requires SHORTTAG YES
… content="text/html; charset=ISO-8859-15"
/
>
The sequence <FOO /> can be interpreted in at least two different ways, depending onthe DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO(with an implied '>'). However, since many browsers don't interpret it this way, even inthe presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pureHTML documents and reserve its use solely for those written in XHTML.
Line 13, Column 79
:
NET-enabling start-tag requires SHORTTAG YES
…href="/css/formulariosDinamicos.css"
/
>
The sequence <FOO /> can be interpreted in at least two different ways, depending onthe DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO(with an implied '>'). However, since many browsers don't interpret it this way, even inthe presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pureHTML documents and reserve its use solely for those written in XHTML.
Line 13, Column 79
:
document type does not allow element "LINK" here
…href="/css/formulariosDinamicos.css"
/
>
The element named above was found in a context where it is not allowed. This couldmean that you have incorrectly nested elements -- such as a "style" element in the"body" section instead of inside "head" -- or two elements that overlap (which is notallowed).One common cause for this error is the use of XHTML syntax in HTML documents. Dueto HTML's rules of implicitly closed elements, this error can create cascading effects. Forinstance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section ofa HTML document may cause the parser to infer the end of the "head" section and thebeginning of the "body" section (where "link" and "meta" are not allowed; hence thereported error).
Line 14, Column 68
:
NET-enabling start-tag requires SHORTTAG YES
…heet" type="text/css" href="/css/cm-estilo.css"
/
>
The sequence <FOO /> can be interpreted in at least two different ways, depending onthe DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO(with an implied '>'). However, since many browsers don't interpret it this way, even inthe presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pureHTML documents and reserve its use solely for those written in XHTML.
Line 14, Column 68
:
document type does not allow element "LINK" here
…heet" type="text/css" href="/css/cm-estilo.css"
/
>
The element named above was found in a context where it is not allowed. This couldmean that you have incorrectly nested elements -- such as a "style" element in the"body" section instead of inside "head" -- or two elements that overlap (which is notallowed).One common cause for this error is the use of XHTML syntax in HTML documents. Due
!!!!!!
16/06/09 13:45[Invalid] Markup Validation of http://www.saludinforma.es/start.htm - W3C Markup ValidatorPágina 3 de 8http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654
to HTML's rules of implicitly closed elements, this error can create cascading effects. Forinstance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section ofa HTML document may cause the parser to infer the end of the "head" section and thebeginning of the "body" section (where "link" and "meta" are not allowed; hence thereported error).
Line 15, Column 65
:
NET-enabling start-tag requires SHORTTAG YES
…stylesheet" type="text/css" href="/css/estilo.css"
/
>
The sequence <FOO /> can be interpreted in at least two different ways, depending onthe DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO(with an implied '>'). However, since many browsers don't interpret it this way, even inthe presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pureHTML documents and reserve its use solely for those written in XHTML.
Line 15, Column 65
:
document type does not allow element "LINK" here
…stylesheet" type="text/css" href="/css/estilo.css"
/
>
The element named above was found in a context where it is not allowed. This couldmean that you have incorrectly nested elements -- such as a "style" element in the"body" section instead of inside "head" -- or two elements that overlap (which is notallowed).One common cause for this error is the use of XHTML syntax in HTML documents. Dueto HTML's rules of implicitly closed elements, this error can create cascading effects. Forinstance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section ofa HTML document may cause the parser to infer the end of the "head" section and thebeginning of the "body" section (where "link" and "meta" are not allowed; hence thereported error).
Line 16, Column 87
:
NET-enabling start-tag requires SHORTTAG YES
…s/general.css" media="screen,print"
/
>
The sequence <FOO /> can be interpreted in at least two different ways, depending onthe DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO(with an implied '>'). However, since many browsers don't interpret it this way, even inthe presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pureHTML documents and reserve its use solely for those written in XHTML.
Line 16, Column 87
:
document type does not allow element "LINK" here
…s/general.css" media="screen,print"
/
>
The element named above was found in a context where it is not allowed. This couldmean that you have incorrectly nested elements -- such as a "style" element in the"body" section instead of inside "head" -- or two elements that overlap (which is notallowed).One common cause for this error is the use of XHTML syntax in HTML documents. Dueto HTML's rules of implicitly closed elements, this error can create cascading effects. Forinstance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section ofa HTML document may cause the parser to infer the end of the "head" section and thebeginning of the "body" section (where "link" and "meta" are not allowed; hence thereported error).
Line 33, Column 7
:
end tag for element "HEAD" which is not open
</head
>
The Validator found an end tag for the above element, but that element is not currentlyopen. This is often caused by a leftover end tag from an element that was removedduring editing, or by an implicitly closed element (if you have an error related to anelement being used where it is not allowed, this is almost certainly the case). In thelatter case this error will disappear as soon as you fix the original problem.If this error occurred in a script section of your document, you should probably read thisFAQ entry.
Line 34, Column 65
:
document type does not allow element "BODY" here
…background-image: none; background-color: #FFFFFF;"
>
The element named above was found in a context where it is not allowed. This couldmean that you have incorrectly nested elements -- such as a "style" element in the"body" section instead of inside "head" -- or two elements that overlap (which is notallowed).One common cause for this error is the use of XHTML syntax in HTML documents. Dueto HTML's rules of implicitly closed elements, this error can create cascading effects. For
!!!!!!
Add a Comment