[Invalid] Markup Validation of webdeveloper-sole.adm.jyu.fi-1248861563498.html - W3C Markup Validator
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Errors found while checking this document as HTML 4.01 Transitional!
| Result: | 68 Errors, 5 warning(s) | |
|---|---|---|
| File: |
Use the file selection box above if you wish to re-validate the uploaded file webdeveloper-sole.adm.jyu.fi-1248861563498.html |
|
| Modified: | (undefined) | |
| Server: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) Gecko/2009060215 Firefox/3.0.11 (.NET CLR 3.5.30729) | |
| Size: | (undefined) | |
| Content-Type: | text/html | |
| Encoding: | iso-8859-1 | (detect automatically) utf-8 (Unicode, worldwide) utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European) iso-8859-5 (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew, visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-11 (Latin/Thai) iso-8859-13 (Latin 7, Baltic Rim) iso-8859-14 (Latin 8, Celtic) iso-8859-15 (Latin 9) iso-8859-16 (Latin 10) us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional) Big5-HKSCS (Chinese, Hong Kong) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian) iso-ir-111 (Cyrillic KOI-8) macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim) |
| Doctype: | HTML 4.01 Transitional | (detect automatically) HTML5 (experimental) XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset HTML 3.2 HTML 2.0 ISO/IEC 15445:2000 ("ISO HTML") XHTML 1.1 XHTML + RDFa XHTML Basic 1.0 XHTML Basic 1.1 XHTML Mobile Profile 1.2 XHTML-Print 1.0 XHTML 1.1 plus MathML 2.0 XHTML 1.1 plus MathML 2.0 plus SVG 1.1 MathML 2.0 SVG 1.0 SVG 1.1 SVG 1.1 Tiny SVG 1.1 Basic SMIL 1.0 SMIL 2.0 |
| Root Element: | html | |
| Show Source | Show Outline | List Messages Sequentially Group Error Messages by Type |
| Validate error pages | Verbose Output | Clean up Markup with HTML Tidy |
Help on the options is available.
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.
-
the MIME Media Type (
- No
DOCTYPEfound! 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”.
It is recommended to use a DOCTYPE declaration as the very first thing in your HTML document, to identify the precise language being used. For example, for a typical XHTML 1.0 document:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head> <title>Title</title> </head> <body> <!-- ... body of document ... --> </body> </html>For XML documents, you may also wish to include an "XML Declaration" even before the DOCTYPE Declaration, but this is not well supported in older browsers. More information about this can be found in the XHTML 1.0 Recommendation.
The W3C QA Activity maintains a List of Valid Doctypes that you can choose from, and the WDG maintains a document on "Choosing a DOCTYPE".
Validation Output: 68 Errors
-
Line 1, Column 1:
no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<html xmlns:java-sole="http://xml.apache.org/xslt/java/fi.solenovo.servlet.ui.SoThe 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 1, Column 23:
Attribute "XMLNS:JAVA-SOLE" is not a valid attribute
<html xmlns:java-sole="http://xml.apache.org/xslt/java/fi.solenovo.servlet.ui.SoYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
-
Line 1, Column 102:
Attribute "XMLNS:DYN" is not a valid attribute
…o.servlet.ui.SoleSession" xmlns:dyn="http://exslt.org/dynamic">You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
-
Line 13, Column 11:
Attribute "HREF" is not a valid attribute. Did you mean "href"?
<rel href="/tyoaikatest/all/css/favicon.ico" type="shortcut icon"></rel>You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
-
Line 13, Column 51:
Attribute "TYPE" is not a valid attribute. Did you mean "type"?
<rel href="/tyoaikatest/all/css/favicon.ico" type="shortcut icon"></rel>You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
-
Line 13, Column 66:
element "REL" undefined. Did you mean "area" or "del"?
…aikatest/all/css/favicon.ico" type="shortcut icon"></rel>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
- incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
- by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
- by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
-
Line 14, Column 57:
element "REL" undefined. Did you mean "area" or "del"?
<rel href="/tyoaikatest/all/css/favicon.gif" type="icon"></rel>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
- incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
- by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
- by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
-
Line 420, Column 163:
required attribute "ALT" not specified
…" class="topmenu_ekakuva" border="0">Etusivu</a><a href="/tyoaikatest/disp/fiThe attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 420, Column 324:
required attribute "ALT" not specified
…gif" class="topmenu_kuva" border="0">Yhteydenotto</a><a target="new" href="/tThe attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 420, Column 482:
required attribute "ALT" not specified
…gif" class="topmenu_kuva" border="0">Käyttöohje</a></td><td class="ylatunnus_The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 421, Column 235:
required attribute "ALT" not specified
…gif" class="topmenu_kuva" border="0">Lopetus</a></td>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 429, Column 53:
required attribute "ALT" not specified
<img border="0" src="/tyoaikatest/all/gifs/logo.gif"></p>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 431, Column 103:
required attribute "ALT" not specified
…tyoaikatest/all/gifs/menu_minus.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 434, Column 60:
cannot generate system identifier for general entity "vainomat"
…isp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img bordeAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
-
Line 434, Column 60:
general entity "vainomat" not defined and no default entity
…isp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img bordeThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 68:
reference to entity "vainomat" for which no system identifier could be generated
…a_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" srThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 58:
entity was defined here
…/disp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img bor -
Line 434, Column 69:
cannot generate system identifier for general entity "menuid"
…_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" srcAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
-
Line 434, Column 69:
general entity "menuid" not defined and no default entity
…_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" srcThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 75:
reference to entity "menuid" for which no system identifier could be generated
…k/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 67:
entity was defined here
…ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s -
Line 434, Column 78:
cannot generate system identifier for general entity "omat"
…ab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoaikAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
-
Line 434, Column 78:
general entity "omat" not defined and no default entity
…ab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoaikThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 82:
reference to entity "omat" for which no system identifier could be generated
…ab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoaikatesThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 76:
entity was defined here
…/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoa -
Line 434, Column 148:
required attribute "ALT" not specified
…/tyoaikatest/all/gifs/menu_none.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 434, Column 226:
reference to entity "vainomat" for which no system identifier could be generated
…a_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120" style="color: blacThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 58:
entity was defined here
…/disp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img bor -
Line 434, Column 233:
reference to entity "menuid" for which no system identifier could be generated
…k/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120" style="color: black; textThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 67:
entity was defined here
…ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s -
Line 434, Column 240:
reference to entity "omat" for which no system identifier could be generated
…ab/clr?page=0&vainomat&menuid=2&omat=519120" style="color: black; text-decoraThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 76:
entity was defined here
…/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoa -
Line 437, Column 65:
reference to entity "menuid" for which no system identifier could be generated
…i/ta_pohja/tab/tab/clr?page=0&menuid=3"><img border="0" src="/tyoaikatest/allThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 67:
entity was defined here
…ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s -
Line 437, Column 126:
required attribute "ALT" not specified
…/tyoaikatest/all/gifs/menu_none.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 437, Column 201:
reference to entity "menuid" for which no system identifier could be generated
…i/ta_pohja/tab/tab/clr?page=0&menuid=3">Reaaliaikainen</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 67:
entity was defined here
…ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s -
Line 440, Column 120:
required attribute "ALT" not specified
…/tyoaikatest/all/gifs/menu_none.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 443, Column 129:
required attribute "ALT" not specified
…/tyoaikatest/all/gifs/menu_none.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 446, Column 103:
required attribute "ALT" not specified
…tyoaikatest/all/gifs/menu_minus.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 449, Column 76:
reference to entity "vainomat" for which no system identifier could be generated
…sisummat/tab/tab/clr?page=0&vainomat&menuid=7&omat=519120"><img border="0" srThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 58:
entity was defined here
…/disp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img bor -
Line 449, Column 83:
reference to entity "menuid" for which no system identifier could be generated
…t/tab/tab/clr?page=0&vainomat&menuid=7&omat=519120"><img border="0" src="/tyoThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 67:
entity was defined here
…ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s -
Line 449, Column 90:
reference to entity "omat" for which no system identifier could be generated
…ab/clr?page=0&vainomat&menuid=7&omat=519120"><img border="0" src="/tyoaikatesThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 76:
entity was defined here
…/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoa -
Line 449, Column 156:
required attribute "ALT" not specified
…/tyoaikatest/all/gifs/menu_none.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 449, Column 242:
reference to entity "vainomat" for which no system identifier could be generated
…sisummat/tab/tab/clr?page=0&vainomat&menuid=7&omat=519120">Kuukausisummat</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 58:
entity was defined here
…/disp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img bor -
Line 449, Column 249:
reference to entity "menuid" for which no system identifier could be generated
…t/tab/tab/clr?page=0&vainomat&menuid=7&omat=519120">Kuukausisummat</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 67:
entity was defined here
…ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s -
Line 449, Column 256:
reference to entity "omat" for which no system identifier could be generated
…ab/clr?page=0&vainomat&menuid=7&omat=519120">Kuukausisummat</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 76:
entity was defined here
…/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoa -
Line 452, Column 127:
required attribute "ALT" not specified
…/tyoaikatest/all/gifs/menu_none.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 455, Column 121:
required attribute "ALT" not specified
…/tyoaikatest/all/gifs/menu_none.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 458, Column 104:
required attribute "ALT" not specified
…tyoaikatest/all/gifs/menu_minus.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 461, Column 123:
required attribute "ALT" not specified
…/tyoaikatest/all/gifs/menu_none.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 464, Column 104:
required attribute "ALT" not specified
…tyoaikatest/all/gifs/menu_minus.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 467, Column 79:
reference to entity "menuid" for which no system identifier could be generated
…kaynnistys/tab/tab/clr?page=0&menuid=13"><img border="0" src="/tyoaikatest/alThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 67:
entity was defined here
…ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s -
Line 467, Column 141:
required attribute "ALT" not specified
…/tyoaikatest/all/gifs/menu_none.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 467, Column 230:
reference to entity "menuid" for which no system identifier could be generated
…kaynnistys/tab/tab/clr?page=0&menuid=13">Käynnistys</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 67:
entity was defined here
…ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s -
Line 470, Column 75:
reference to entity "menuid" for which no system identifier could be generated
…tti_lataus/tab/tab/clr?page=0&menuid=14"><img border="0" src="/tyoaikatest/alThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 67:
entity was defined here
…ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s -
Line 470, Column 137:
required attribute "ALT" not specified
…/tyoaikatest/all/gifs/menu_none.gif"></a> <a href="/tyoaikatest/disp/fi/The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 470, Column 222:
reference to entity "menuid" for which no system identifier could be generated
…tti_lataus/tab/tab/clr?page=0&menuid=14">Valmiit</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
-
Line 434, Column 67:
entity was defined here
…ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s -
Line 494, Column 53:
document type does not allow element "INPUT" here; assuming missing "CAPTION" start-tag
<input value="" name="henktyoajanseur" type="hidden"> -
Line 495, Column 4:
document type does not allow element "TR" here
<tr>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 498, Column 4:
document type does not allow element "TR" here
<tr>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 501, Column 4:
document type does not allow element "TR" here
<tr>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 504, Column 4:
document type does not allow element "TR" here
<tr>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 505, Column 217:
end tag for "SELECT" which is not finished
….submit()" name="projteht0"></select></td>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
-
Line 507, Column 4:
document type does not allow element "TR" here
<tr>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 520, Column 4:
document type does not allow element "TR" here
<tr>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 523, Column 4:
document type does not allow element "TR" here
<tr>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 526, Column 4:
document type does not allow element "TR" here
<tr>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 529, Column 4:
document type does not allow element "TR" here
<tr>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 532, Column 4:
document type does not allow element "TR" here
<tr>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 535, Column 8:
end tag for "CAPTION" omitted, but its declaration does not permit this
</table>- 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 494:
start tag was here
><input value="" name="henktyoajanseur" type="hidden"> -
Line 535, Column 8:
end tag for "TABLE" which is not finished
</table>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
-
Line 537, Column 25:
required attribute "ACTION" not specified
<form name="ajaxlocales">The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 542, Column 266:
required attribute "ALT" not specified
…oaikatest/all/gifs/delete_small.gif"></a></span>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 549, Column 197:
required attribute "ALT" not specified
…ll/gifs/delete_small.gif" border="0"> Sulje</a>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 554, Column 138:
required attribute "ALT" not specified
…src="/tyoaikatest/all/gifs/save.gif"> Tallenna</a></td><td><a href="/tyoThe attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 554, Column 296:
required attribute "ALT" not specified
…c="/tyoaikatest/all/gifs/return.gif"> Palaa</a></td>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 569, Column 21:
required attribute "ACTION" not specified
<form name="kaytarv">The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 570, Column 95:
end tag for "SELECT" which is not finished
…yer_kaytarv')" name="arvot"></select><input name="kentta" type="hidden"><inpuMost likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
