Академический Документы
Профессиональный Документы
Культура Документы
Address : http://www.saludinforma.es/start.htm
Options
The validator can process documents either as XML (for document types such as
XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document,
the information available was not sufficient to determine the parsing mode
unambiguously, because:
the MIME Media Type ( text/html) can be used for XML or SGML
document types
No known Document Type could be detected
No XML declaration (e.g <?xml version="1.0"?>) could be found at the
beginning 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.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654 Página 1 de 8
[Invalid] Markup Validation of http://www.saludinforma.es/start.htm - W3C Markup Validator 16/06/09 13:45
The character encoding specified in the HTTP header ( iso-8859-1) is different from
the value in the <meta> element ( iso-8859-15). I will use the value from the HTTP
header ( iso-8859-1) for this validation.
! TOP
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 could
mean 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 not
allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due
to HTML's rules of implicitly closed elements, this error can create cascading effects. For
instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of
a HTML document may cause the parser to infer the end of the "head" section and the
beginning of the "body" section (where "link" and "meta" are not allowed; hence the
reported error).
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 could
mean 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 not
allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due
to HTML's rules of implicitly closed elements, this error can create cascading effects. For
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654 Página 2 de 8
[Invalid] Markup Validation of http://www.saludinforma.es/start.htm - W3C Markup Validator 16/06/09 13:45
to HTML's rules of implicitly closed elements, this error can create cascading effects. For
instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of
a HTML document may cause the parser to infer the end of the "head" section and the
beginning of the "body" section (where "link" and "meta" are not allowed; hence the
reported error).
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 could
mean 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 not
allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due
to HTML's rules of implicitly closed elements, this error can create cascading effects. For
instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of
a HTML document may cause the parser to infer the end of the "head" section and the
beginning of the "body" section (where "link" and "meta" are not allowed; hence the
reported error).
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 could
mean 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 not
allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due
to HTML's rules of implicitly closed elements, this error can create cascading effects. For
instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of
a HTML document may cause the parser to infer the end of the "head" section and the
beginning of the "body" section (where "link" and "meta" are not allowed; hence the
reported 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 currently
open. This is often caused by a leftover end tag from an element that was removed
during editing, or by an implicitly closed element (if you have an error related to an
element being used where it is not allowed, this is almost certainly the case). In the
latter 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 this
FAQ 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 could
mean 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 not
allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due
to HTML's rules of implicitly closed elements, this error can create cascading effects. For
instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654 Página 3 de 8
[Invalid] Markup Validation of http://www.saludinforma.es/start.htm - W3C Markup Validator 16/06/09 13:45
instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of
a HTML document may cause the parser to infer the end of the "head" section and the
beginning of the "body" section (where "link" and "meta" are not allowed; hence the
reported error).
Line 67, Column 16: end tag for "SCRIPT" omitted, but its declaration does
not permit this
!
window.open("./ formulario_tajerta.pdf" , "FormularioTarjeta" , "width=600,heigh
Line 67, Column 16: end tag for "DIV" omitted, but its declaration does not
permit this
!
window.open("./ formulario_tajerta.pdf" , "FormularioTarjeta" , "width=600,heigh
<div id="bodyContentDiv">
Line 67, Column 16: end tag for "DIV" omitted, but its declaration does not
permit this
!
window.open("./ formulario_tajerta.pdf" , "FormularioTarjeta" , "width=600,heigh
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654 Página 4 de 8
[Invalid] Markup Validation of http://www.saludinforma.es/start.htm - W3C Markup Validator 16/06/09 13:45
<div class="contentBody">
Line 67, Column 16: end tag for "DIV" omitted, but its declaration does not
permit this
!
window.open("./ formulario_tajerta.pdf" , "FormularioTarjeta" , "width=600,heigh
Line 70, Column 9: end tag for element "SCRIPT" which is not open
!
</script >
The Validator found an end tag for the above element, but that element is not currently
open. This is often caused by a leftover end tag from an element that was removed
during editing, or by an implicitly closed element (if you have an error related to an
element being used where it is not allowed, this is almost certainly the case). In the
latter 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 this
FAQ entry.
Line 77, Column 11: end tag for element "DIV" which is not open
!
</div>
The Validator found an end tag for the above element, but that element is not currently
open. This is often caused by a leftover end tag from an element that was removed
during editing, or by an implicitly closed element (if you have an error related to an
element being used where it is not allowed, this is almost certainly the case). In the
latter 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 this
FAQ entry.
Line 78, Column 11: end tag for element "DIV" which is not open
!
</div>
The Validator found an end tag for the above element, but that element is not currently
open. This is often caused by a leftover end tag from an element that was removed
during editing, or by an implicitly closed element (if you have an error related to an
element being used where it is not allowed, this is almost certainly the case). In the
latter 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 this
FAQ entry.
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654 Página 5 de 8
[Invalid] Markup Validation of http://www.saludinforma.es/start.htm - W3C Markup Validator 16/06/09 13:45
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
Line 135, Column 20: syntax of attribute value does not conform to declared
value
!
<label for="" > Por favor, por motivos de seguridad, introduzca debajo las
The value of an attribute contained something that is not allowed by the specified syntax
for that type of attribute. For instance, the “ selected ” attribute must be either minimized
as “ selected ” or spelled out in full as “ selected="selected" ”; the variant
“ selected="" ” is not allowed.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654 Página 6 de 8
[Invalid] Markup Validation of http://www.saludinforma.es/start.htm - W3C Markup Validator 16/06/09 13:45
(with an implied '>'). However, since many browsers don't interpret it this way, even in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
The sequence <FOO /> can be interpreted in at least two different ways, depending on
the 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 in
the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure
HTML documents and reserve its use solely for those written in XHTML.
Line 181, Column 6: end tag for element "DIV" which is not open
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654 Página 7 de 8
[Invalid] Markup Validation of http://www.saludinforma.es/start.htm - W3C Markup Validator 16/06/09 13:45
Line 181, Column 6: end tag for element "DIV" which is not open
!
</div >
The Validator found an end tag for the above element, but that element is not currently
open. This is often caused by a leftover end tag from an element that was removed
during editing, or by an implicitly closed element (if you have an error related to an
element being used where it is not allowed, this is almost certainly the case). In the
latter 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 this
FAQ entry.
! TOP
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.saludinforma.…ally%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654 Página 8 de 8