Вы находитесь на странице: 1из 8

[Invalid] Markup Validation of http://www.saludinforma.es/start.

htm - W3C Markup Validator 16/06/09 13:45

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.01


Transitional!
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: html

The W3C validators rely on community support for hosting and


development.
Donate and help us build better tools for a better web.

Options

List Messages Sequentially Group Error


Show Source
Show Outline Messages by Type

Clean up Markup with HTML Tidy


Validate error pages Verbose Output

Help on the options is available.


Revalidate

Notes and Potential Issues


The following notes and warnings highlight missing or conflicting information which
caused the validator to perform some guesswork prior to validation. If the guess or
fallback 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-validate
the document.

Unable to Determine Parse Mode!

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.

As a default, the validator is falling back to SGML mode.

No DOCTYPE found! Checking with default HTML 4.01 Transitional Document


Type.
No DOCTYPE Declaration could be found or recognized in this document. This
generally means that the document is not declaring its Document Type at the top. It
can also mean that the DOCTYPE declaration contains a spelling error, or that it is
not using the correct syntax.
The document was checked using a default "fallback" Document Type Definition that
closely resembles “HTML 4.01 Transitional”.
Learn how to add a doctype to your document from our FAQ.

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

Character Encoding mismatch!

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

Validation Output: 16 Errors

Line 7, Column 1: no document type declaration; implying "<!DOCTYPE


HTML SYSTEM>"
!
< html lang="es-ES">
The checked page did not contain a document type ("DOCTYPE") declaration. The
Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect
and will generate a large number of incorrect error messages. It is highly recommended
that you insert the proper DOCTYPE declaration in your document -- instructions for
doing this are given above -- and it is necessary to have this declaration before the
page 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 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 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 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 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: 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 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 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: 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 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 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: 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 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 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 35, Column 8: NET-enabling start-tag requires SHORTTAG YES


!
<br />
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 55, Column 41: NET-enabling start-tag requires SHORTTAG YES


!
<div style="z-index: 1000;" id="overDiv" />
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 67, Column 16: end tag for "SCRIPT" omitted, but its declaration does
not permit this
!
window.open("./ formulario_tajerta.pdf" , "FormularioTarjeta" , "width=600,heigh

You forgot to close a tag, or


you used something inside this tag that was not allowed, and the validator is complaining
that the tag should be closed before such content can be allowed.
The next message, "start tag was here " points to the particular instance of the tag in
question); the positional indicator points to where the validator expected you to close the
tag.

Line 64: start tag was here

> <script type="text/javascript">

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

You forgot to close a tag, or


you used something inside this tag that was not allowed, and the validator is complaining
that the tag should be closed before such content can be allowed.
The next message, "start tag was here " points to the particular instance of the tag in
question); the positional indicator points to where the validator expected you to close the
tag.

Line 59, Column 9: start tag was here

<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

You forgot to close a tag, or


you used something inside this tag that was not allowed, and the validator is complaining
that the tag should be closed before such content can be allowed.
The next message, "start tag was here " points to the particular instance of the tag in
question); the positional indicator points to where the validator expected you to close the
tag.

Line 58, Column 5: start tag was here

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

You forgot to close a tag, or


you used something inside this tag that was not allowed, and the validator is complaining
that the tag should be closed before such content can be allowed.
The next message, "start tag was here " points to the particular instance of the tag in
question); the positional indicator points to where the validator expected you to close the
tag.

Line 57: start tag was here

> <div class="currentContent">

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 71, Column 4: NET-enabling start-tag requires SHORTTAG YES


!
<br />
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 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.

Line 101, Column 5: NET-enabling start-tag requires SHORTTAG YES


!
<br/ >

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

Line 105, Column 8: NET-enabling start-tag requires SHORTTAG YES


!
<br/ ><br/>

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 105, Column 13: NET-enabling start-tag requires SHORTTAG YES


!
<br/><br/ >

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 115, Column 76: NET-enabling start-tag requires SHORTTAG YES


!
…ass="cmSearchInput" type="text" value="" />
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 122, Column 78: NET-enabling start-tag requires SHORTTAG YES


!
…s="cmSearchInput" type="text" value="" />
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 125, Column 54: NET-enabling start-tag requires SHORTTAG YES


!
<input id="cip" name="cip" type="hidden" value=""/ >

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.

Line 138, Column 121: NET-enabling start-tag requires SHORTTAG YES


!
… size="10" name="j_captcha_response" />
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 144, Column 164: NET-enabling start-tag requires SHORTTAG YES


!
…d gray;" onclick="refrescaImagen();" />
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

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.

Line 159, Column 28: NET-enabling start-tag requires SHORTTAG YES


!
<p class="cmClear"/ >

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 160, Column 28: NET-enabling start-tag requires SHORTTAG YES


!
<p class="cmClear"/ >

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 161, Column 13: NET-enabling start-tag requires SHORTTAG YES


!
<br/ ><br/>

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 161, Column 18: NET-enabling start-tag requires SHORTTAG YES


!
<br/><br/ >

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 165, Column 59: NET-enabling start-tag requires SHORTTAG YES


!
<img alt="Ayuda" src="/imagenes/contenidos/ayuda.png"/ > Ayuda

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 168, Column 63: NET-enabling start-tag requires SHORTTAG YES


!
… alt="Limpiar" src="/imagenes/contenidos/limpiar.gif" /> Limpiar

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 171, Column 99: NET-enabling start-tag requires SHORTTAG YES


!
…contenidos/buscar_subcontenidos.gif" /> <span style="font-weight:bold; colo

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

Home About... News Docs Help & FAQ Feedback Contribute

This service runs the W3C Markup Validator, v0.8.5.


COPYRIGHT © 1994-2009 W3C® (MIT, ERCIM, KEIO), ALL RIGHTS
RESERVED. W3C LIABILITY, TRADEMARK, DOCUMENT USE AND
SOFTWARE LICENSING RULES APPLY. YOUR INTERACTIONS WITH
THIS SITE ARE IN ACCORDANCE WITH OUR PUBLIC AND MEMBER
PRIVACY STATEMENTS.

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

Вам также может понравиться