# [700] Batch Wizard Report

Multiple page report: Previous | Summary 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 | Next

## Summary Report (Partial)

### 1. Documents that have errors

- http://www.apat.gov.it/Media/carta_geologica_italia/modello3d_en.asp?path=./shade/cgis923/ (20), [and 1 warning]
- http://www.apat.gov.it/Media/carta_geologica_italia/tavoletta_en.asp?foglio=26A (21), [and 1 warning]
- http://www.apat.gov.it/Monitoraggio/database.asp (5), [and 20 warnings]
- http://www.apat.gov.it/Museo/archeocitest.html (19), [and 10 warnings]
- http://www.apat.gov.it/Museo/graptotesto.html (21), [and 8 warnings]
- http://www.apat.gov.it/Museo/trilobiti.html (21), [and 7 warnings]
- http://www.apat.gov.it/museo (1), [and 2 warnings]
- http://www.apat.gov.it/site/EN-GB/ (2), [and 10 warnings]
- http://www.apat.gov.it/site/EN-GB/APAT/Other/ (1), [and 8 warnings]

### 2. Documents that have warnings

### 3. Documents that have no errors or warnings

- http://www.apat.gov.it/ithaca/regioni.asp?regione

## Validation Reports

### http://www.apat.gov.it/Media/carta_geologica_italia/modello3d_en.asp?path=./shade/cgis923/

Line:char | Type | Message Description
--- | --- | ---
| Message (Web Content Accessibility Guidelines 1.0) [ACCESSIBILITY] | [73] WCAG 1.0 accessibility checking is disabled.
| Message (Section 508 Accessibility Standards) [ACCESSIBILITY] | [73] Section 508 accessibility checking is disabled.
4:2 | Message (Search Engine) | Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: <title>Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows</title>. AI Internet Solutions also recommends that the "title" tag be the first tag inside the "head" section.
14:2 | Message (Microsoft Internet Explorer) [CSS] | [600] The "behavior" CSS property is not an official CSS property and is only supported by Internet Explorer 5.0+. Firefox, Netscape, Opera, and most other browsers do not support this property.
24:40 | Message (General Compatibility) | [5] PNG images are generally well supported in today's browsers EXCEPT for Microsoft Internet Explorer 6.0 and below. IE 6.0 will not render PNG images correctly in certain cases. Because of the popularity of Internet Explorer, you may want to consider using GIF or JPG images instead, especially when using the transparency features of PNG which IE 6.0 does not support well. Fortunately PNG support has been improved in IE 7.0. This message is displayed only once. There may be other PNG images specified in this document.
47:67 | Error | The "summary" attribute has an invalid attribute value "". Try using one of the following values: an alphanumeric string or a string. <table border="0" cellspacing="0" cellpadding="0" summary="" class="TabellaCentrale">
47:10 | Message (Good Style) | Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute.
47:10 | Message (General Compatibility) | [5] The "table" element is an official HTML 4.01 and XHTML element but may not be supported by older or nongraphical browsers. Furthermore, nongraphical browsers that do support tables may not support them the way that you expect. However, most browsers used today should support this element.
48:12 | Error | The "tr" tag must have an end tag (</tr>) but the end tag was not found. <tr>
49:14 | Error | The "td" tag must have an end tag (</td>) but the end tag was not found. <td> <div id="path">&nbsp;</div>
50:35 | Error (HTML 4.0 Compatibility) | [81] The "align" attribute may not be used with the "div" element in a strict HTML 4.0/4.01 document. Instead of align="center", consider using the CSS "text-align: center" instead. <div id="Contenuti" align="center">
50:35 | Message (Deprecated) | [9] The "align" attribute is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of align="center", consider using the CSS "text-align: center" instead.
51:15 | Error | The "id" or "name" attribute value "path" has already been used in this document. A tag's "id" or "name" value ("name" only for certain elements such as "a") must be unique within the document. A tag cannot have an "id" or, with certain elements, a "name" attribute value that has already been used. Note that the "id" values are not case sensitive (except when used to link to an anchor) and that "id" and some "name" attribute values share the same namespace. <div id="path" align="left"> <a href="default_en.htm">Home</a></div>
52:49 | Error (HTML 4.0 Compatibility) | [81] The following attributes may not be used with the "TABLE" element in a strict HTML 4.0/4.01 document: "align", "bgcolor", "bordercolor", "bordercolorlight", "bordercolordark", "height", "hspace", and "vspace". Instead of ALIGN="CENTER", consider using the following CSS to center the table: "margin-left: auto; margin-right: auto". This is the correct CSS way but it may not work with some (mostly older) browsers. Instead of the "BGCOLOR" attribute, consider using the CSS property "background-color". Example: style="background-color: #000000". <TABLE BORDER=0 CELLPADDING=1 CELLSPACING=0 BGCOLOR=#000000 WIDTH="100%" ALIGN="CENTER">
52:57 | Error | The attribute value "#000000" for the "BGCOLOR" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <TABLE BORDER=0 CELLPADDING=1 CELLSPACING=0 BGCOLOR=#000000 WIDTH="100%" ALIGN="CENTER">
52:49 | Message (Deprecated) | [9] The "align" and "bgcolor" attributes for the "TABLE" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of ALIGN="CENTER", consider using the following CSS to center the table: "margin-left: auto; margin-right: auto". This is the correct CSS way but it may not work with some (mostly older) browsers. Instead of the "BGCOLOR" attribute, consider using the CSS property "background-color". Example: style="background-color: #000000".
55:30 | Error | The attribute value "100%" for the "WIDTH" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <TABLE BORDER=0 WIDTH=100% BGCOLOR=#ffffff CELLSPACING=0 CELLPADDING=0>
55:43 | Error | The attribute value "#ffffff" for the "BGCOLOR" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <TABLE BORDER=0 WIDTH=100% BGCOLOR=#ffffff CELLSPACING=0 CELLPADDING=0>
62:10 | Error (HTML 4.0 Compatibility) | [76] The "EMBED" element should not be used in a strict HTML 4.0/4.01 document. Note that you may want to consider using a different DOCTYPE declaration that is more lenient and allows more element, such as an HTML 4.01 transitional DOCTYPE. For example, you may want to use the HTML 4.01 transitional DOCTYPE: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. <EMBED FlashVars="zoomifyImagePath=./shade/cgis923/" SRC="zoomifyViewer.swf" MENU="false" PLUGINSPAGE="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash" WIDTH="100%" HEIGHT="700" NAME="theMovie"></EMBED>
62:16 | Error | The "FlashVars" attribute is not valid for the "EMBED" element. Some valid attributes for this element are: "align", "allowscriptaccess", "alt", "autoplay", "autostart", "base", "bgcolor", "border", "class", "contenteditable", "controls", "frameborder", "height", "hidden", "hidefocus", "hspace", "id", "logo", "loop", "menu", "name", "onactivate", "onbeforecopy", "onbeforecut", "onbeforepaste", "onblur", "onclick", "oncontextmenu", "oncopy", "oncut", "ondblclick", "ondeactivate", "ondrag", "ondragend", "ondragenter", "ondragleave", "ondragover", "ondragstart", "ondrop", "onfilterchange", "onfocus", "onfocusin", "onfocusout", "onhelp", "onkeydown", "onkeypress", "onkeyup", "onmousedown", "onmouseenter", "onmouseleave", "onmousemove", "onmouseout", "onmouseover", "onmouseup", "onmousewheel", "onmove", "onmoveend", "onmovestart", "onpaste", "onpropertychange", "onselectstart", "palette", "play", "pluginspage", "progress", "quality", "salign", "scale", "song", "src", "style", "swliveconnect", "swremote", "swstretchhalign", "swstretchstyle", "swstretchvalign", "title", "type", "units", "unselectable", "volume", "vspace", "width", "wmode", and "xml:space". <EMBED FlashVars="zoomifyImagePath=./shade/cgis923/" SRC="zoomifyViewer.swf" MENU="false" PLUGINSPAGE="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash" WIDTH="100%" HEIGHT="700" NAME="theMovie"></EMBED>
62:10 | Message (General Compatibility) | [5] The "EMBED" element is not an official HTML or XHTML element. Some browsers may not support this element. Consider using the "object" element instead.
69:57 | Error | The attribute value "#FFFFFF" for the "BGCOLOR" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <TABLE BORDER=0 CELLPADDING=1 CELLSPACING=0 BGCOLOR=#FFFFFF WIDTH="100%" ALIGN="CENTER">
72:11 | Error (HTML 4.0 Compatibility) | [81] The "align" attribute may not be used with the "h4" element in a strict HTML 4.0/4.01 document. Instead of align="center", consider using the CSS "text-align: center" instead. <h4 align="center">MAP REALIZED BY THE GEOLOGICAL SURVEY OF ITALY </h4>
72:8 | Message (Good Style) | [7] A heading has been used without previously using the higher heading levels. Some HTML authors consider this bad style. For example, if "h4" is used, then "h1", "h2", and "h3" should have already been used, in that order.
73:23 | Error (HTML 4.0 Compatibility) | [81] The "align" attribute may not be used with the "h5" element in a strict HTML 4.0/4.01 document. Instead of align="center", consider using the CSS "text-align: center" instead. <h5 align="center"><font color="#336600">ITALIAN CARTOGRAPHIC BODY </font></h5>
73:39 | Error (HTML 4.0 Compatibility) | [76] The "font" element should not be used in a strict HTML 4.0/4.01 document. Style sheets should be used instead of this element. Note that you may want to consider using a different DOCTYPE declaration that is more lenient and allows more element, such as an HTML 4.01 transitional DOCTYPE. For example, you may want to use the HTML 4.01 transitional DOCTYPE: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. <h5 align="center"><font color="#336600">ITALIAN CARTOGRAPHIC BODY </font></h5>
73:39 | Message (Deprecated) | [9] The "font" element and all of its attributes are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the "color", "font", "font-family", "font-size", and other CSS font properties instead).
74:23 | Error (HTML 4.0 Compatibility) | [81] The "align" attribute may not be used with the "h6" element in a strict HTML 4.0/4.01 document. Instead of align="center", consider using the CSS "text-align: center" instead. <h6 align="center"><font color="#336600">(LAW 2/2/1960 N.68)</font></h6>
80:97 | Error (HTML 4.0 Compatibility) | [81] The "target" attribute may not be used with the "a" element in a strict HTML 4.0/4.01 document. <Font size="1" face="arial" color="#1A4658">Powered by <a href="http://www.zoomify.com/" target="_blank">Zoomify</a></Font>
82:6 | Error | The end tag for "TR" (opened in line 78) should appear before the end tag for "TABLE" (nesting error). </TABLE>
88:10 | Error | The end tag for "td" (opened in line 49) should appear before the end tag for "table" (nesting error). </table>
100:4 | Warning | [56] The "p" tag is contained in a "p" tag that was opened in line 99. This is against the HTML specification and may cause problems with some browsers.
109:3 | Error | Somewhere in this document there is a nonexistent internal link to "MenuSinistro" created by using <a href="#MenuSinistro"> ... </a>. This link should be removed or it should link to a location in the document that is specified by <a name="MenuSinistro"> ... </a> or <element id="MenuSinistro"...>. </body>
| Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.
| Comment | You can disable all the error messages for improperly quoted attribute values by having HTML Validator ignore and disregard the quotation mark requirements for attribute values. This option is in CSE HTML Validator's Validator Engine Options. However, it is recommended that you leave these error messages enabled and that you properly enclose attribute values in quotation marks.
| Comment | You can use the Quick Quote Tool in the editor to quickly enclose all attribute values in quotation marks.
| Comment | You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options.
| Comment | You have one or more internal links linking to an ID link destination. Browser support for this is currently very poor. Consider using something like <a name="Contenuti"> ... </a> or <a name="Contenuti" id="Contenuti"> ... </a> instead.
| Comment | Possibly misspelled words (17, 13 unique): Curtatone (1x), di (1x), il (1x), ITALIAN (1x), ITALY (1x), ROMA (1x), Salta (1x), SiteMap (1x), utilit (1x), Zoomify (1x), APAT (2x), contenuto (2x), torna (3x). Complete list.
| Comment | HTML 4.01 Strict document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #7 - Each page on a site should have its own unique title. Every title should contain appropriate keywords and search terms that are relevent to the page.
| Comment (Search Engine) | [8] <meta name="description" content="(actual description)"> should be used in the "head" section to provide a brief description of what is contained on this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment (Search Engine) | [8] <meta name="keywords" content="(actual keyword list)"> should be used in the "head" section to provide a list of keywords that are relevent to this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment | An ICRA RDF label was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. It is recommended that every page include an ICRA label. For more information, please visit http://www.icra.org/.
| Comment | [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | 4580 bytes; 3.2s@14.4Kbps, 1.6s@28.8, 0.9s@50, 0.7s@64, 0.4s@128, 0.1s@384, 0.1s@512, 0.1s@768, 0.0s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.03s, 20 errors, 1 warning, 12 messages, 15 validator comments, 110 lines, 78 tags (65 closed), 0 document comments, 6 entities, 209 programs run.

[ Summary ] [ To the top ]

### http://www.apat.gov.it/Media/carta_geologica_italia/tavoletta_en.asp?foglio=26A

Line:char | Type | Message Description
--- | --- | ---
| Message (Web Content Accessibility Guidelines 1.0) [ACCESSIBILITY] | [73] WCAG 1.0 accessibility checking is disabled.
| Message (Section 508 Accessibility Standards) [ACCESSIBILITY] | [73] Section 508 accessibility checking is disabled.
4:2 | Message (Search Engine) | Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: <title>Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows</title>. AI Internet Solutions also recommends that the "title" tag be the first tag inside the "head" section.
26:40 | Message (General Compatibility) | [5] PNG images are generally well supported in today's browsers EXCEPT for Microsoft Internet Explorer 6.0 and below. IE 6.0 will not render PNG images correctly in certain cases. Because of the popularity of Internet Explorer, you may want to consider using GIF or JPG images instead, especially when using the transparency features of PNG which IE 6.0 does not support well. Fortunately PNG support has been improved in IE 7.0. This message is displayed only once. There may be other PNG images specified in this document.
49:67 | Error | The "summary" attribute has an invalid attribute value "". Try using one of the following values: an alphanumeric string or a string. <table border="0" cellspacing="0" cellpadding="0" summary="" class="TabellaCentrale">
49:10 | Message (Good Style) | Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute.
49:10 | Message (General Compatibility) | [5] The "table" element is an official HTML 4.01 and XHTML element but may not be supported by older or nongraphical browsers. Furthermore, nongraphical browsers that do support tables may not support them the way that you expect. However, most browsers used today should support this element.
51:22 | Error (HTML 4.0 Compatibility) | [81] The "align" attribute may not be used with the "div" element in a strict HTML 4.0/4.01 document. Instead of align="center", consider using the CSS "text-align: center" instead. <td><div align="center"><h3>SHEET N.26A - IDRIA</h3></div></td>
51:22 | Message (Deprecated) | [9] The "align" attribute is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of align="center", consider using the CSS "text-align: center" instead.
51:38 | Message (Good Style) | [7] A heading has been used without previously using the higher heading levels. Some HTML authors consider this bad style. For example, if "h4" is used, then "h1", "h2", and "h3" should have already been used, in that order.
57:28 | Error | The "id" or "name" attribute value "path" has already been used in this document. A tag's "id" or "name" value ("name" only for certain elements such as "a") must be unique within the document. A tag cannot have an "id" or, with certain elements, a "name" attribute value that has already been used. Note that the "id" values are not case sensitive (except when used to link to an anchor) and that "id" and some "name" attribute values share the same namespace. <div id="path" align="left"> <a href="default_en.htm">Home</a></div>
59:61 | Error (HTML 4.0 Compatibility) | [81] The following attributes may not be used with the "TABLE" element in a strict HTML 4.0/4.01 document: "align", "bgcolor", "bordercolor", "bordercolorlight", "bordercolordark", "height", "hspace", and "vspace". Instead of ALIGN="CENTER", consider using the following CSS to center the table: "margin-left: auto; margin-right: auto". This is the correct CSS way but it may not work with some (mostly older) browsers. Instead of the "BGCOLOR" attribute, consider using the CSS property "background-color". Example: style="background-color: #ffffff". <TABLE BORDER=0 CELLPADDING=1 CELLSPACING=0 BGCOLOR=#ffffff WIDTH="100%" ALIGN="CENTER">
59:69 | Error | The attribute value "#ffffff" for the "BGCOLOR" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <TABLE BORDER=0 CELLPADDING=1 CELLSPACING=0 BGCOLOR=#ffffff WIDTH="100%" ALIGN="CENTER">
59:61 | Message (Deprecated) | [9] The "align" and "bgcolor" attributes for the "TABLE" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of ALIGN="CENTER", consider using the following CSS to center the table: "margin-left: auto; margin-right: auto". This is the correct CSS way but it may not work with some (mostly older) browsers. Instead of the "BGCOLOR" attribute, consider using the CSS property "background-color". Example: style="background-color: #ffffff".
62:25 | Error (HTML 4.0 Compatibility) | [81] The following attributes may not be used with the "TD" element in a strict HTML 4.0/4.01 document: "background", "bgcolor", "bordercolor", "bordercolorlight", "bordercolordark", "height", "nowrap", and "width". <TD height="20"> <div align="center"><a href=""><b><font color="#FF0000">F.___</font></b>
62:66 | Error | The "href" attribute has an invalid attribute value "". Try using one of the following values: an alphanumeric string or a string. <TD height="20"> <div align="center"><a href=""><b><font color="#FF0000">F.___</font></b>
62:73 | Error (HTML 4.0 Compatibility) | [76] The "font" element should not be used in a strict HTML 4.0/4.01 document. Style sheets should be used instead of this element. Note that you may want to consider using a different DOCTYPE declaration that is more lenient and allows more element, such as an HTML 4.01 transitional DOCTYPE. For example, you may want to use the HTML 4.01 transitional DOCTYPE: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. <TD height="20"> <div align="center"><a href=""><b><font color="#FF0000">F.___</font></b>
62:25 | Message (Deprecated) | [9] The "height" and "width" attributes for the "TD" and "th" elements are deprecated in HTML 4.01 and XHTML in favor of using style sheets.
62:70 | Message (Good Style) | The "strong" element should be used instead of the "b" element when you want to denote strong emphasis. The "b" element should only be used when you want bold typeface but do not want strong emphasis. Many web authors use the "b" element when the "strong" element would be more appropriate.
62:73 | Message (Deprecated) | [9] The "font" element and all of its attributes are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the "color", "font", "font-family", "font-size", and other CSS font properties instead).
81:26 | Error (HTML 4.0 Compatibility) | [76] The "embed" element should not be used in a strict HTML 4.0/4.01 document. Note that you may want to consider using a different DOCTYPE declaration that is more lenient and allows more element, such as an HTML 4.01 transitional DOCTYPE. For example, you may want to use the HTML 4.01 transitional DOCTYPE: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. <embed flashvars="zoomifyImagePath=./fogli/cgis026a/" src="zoomifyViewer.swf" menu="false" pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash" width="100%" height="500"></embed>
81:32 | Error | The "flashvars" attribute is not valid for the "embed" element. Some valid attributes for this element are: "align", "allowscriptaccess", "alt", "autoplay", "autostart", "base", "bgcolor", "border", "class", "contenteditable", "controls", "frameborder", "height", "hidden", "hidefocus", "hspace", "id", "logo", "loop", "menu", "name", "onactivate", "onbeforecopy", "onbeforecut", "onbeforepaste", "onblur", "onclick", "oncontextmenu", "oncopy", "oncut", "ondblclick", "ondeactivate", "ondrag", "ondragend", "ondragenter", "ondragleave", "ondragover", "ondragstart", "ondrop", "onfilterchange", "onfocus", "onfocusin", "onfocusout", "onhelp", "onkeydown", "onkeypress", "onkeyup", "onmousedown", "onmouseenter", "onmouseleave", "onmousemove", "onmouseout", "onmouseover", "onmouseup", "onmousewheel", "onmove", "onmoveend", "onmovestart", "onpaste", "onpropertychange", "onselectstart", "palette", "play", "pluginspage", "progress", "quality", "salign", "scale", "song", "src", "style", "swliveconnect", "swremote", "swstretchhalign", "swstretchstyle", "swstretchvalign", "title", "type", "units", "unselectable", "volume", "vspace", "width", "wmode", and "xml:space". <embed flashvars="zoomifyImagePath=./fogli/cgis026a/" src="zoomifyViewer.swf" menu="false" pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash" width="100%" height="500"></embed>
81:26 | Message (General Compatibility) | [5] The "embed" element is not an official HTML or XHTML element. Some browsers may not support this element. Consider using the "object" element instead.
93:36 | Error | The "href" attribute has an invalid attribute value "". Try using one of the following values: an alphanumeric string or a string. <p><a href=""><b><font color="#FF0000">F.___</font></b></a></p>
98:66 | Error | The "href" attribute has an invalid attribute value "". Try using one of the following values: an alphanumeric string or a string. <TD height="20"> <div align="center"><a href=""><b><font color="#FF0000">F.___</font></b></a></div></TD>
102:69 | Error | The attribute value "#ffffff" for the "BGCOLOR" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <TABLE BORDER=0 CELLPADDING=1 CELLSPACING=0 BGCOLOR=#ffffff WIDTH="100%" ALIGN="CENTER">
104:48 | Error | The attribute value "100%" for the "WIDTH" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <TD> <TABLE BORDER=0 WIDTH=100% BGCOLOR=#ffffff CELLSPACING=0 CELLPADDING=0>
104:61 | Error | The attribute value "#ffffff" for the "BGCOLOR" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <TD> <TABLE BORDER=0 WIDTH=100% BGCOLOR=#ffffff CELLSPACING=0 CELLPADDING=0>
110:38 | Error | The "FlashVars" attribute is not valid for the "EMBED" element. Some valid attributes for this element are: "align", "allowscriptaccess", "alt", "autoplay", "autostart", "base", "bgcolor", "border", "class", "contenteditable", "controls", "frameborder", "height", "hidden", "hidefocus", "hspace", "id", "logo", "loop", "menu", "name", "onactivate", "onbeforecopy", "onbeforecut", "onbeforepaste", "onblur", "onclick", "oncontextmenu", "oncopy", "oncut", "ondblclick", "ondeactivate", "ondrag", "ondragend", "ondragenter", "ondragleave", "ondragover", "ondragstart", "ondrop", "onfilterchange", "onfocus", "onfocusin", "onfocusout", "onhelp", "onkeydown", "onkeypress", "onkeyup", "onmousedown", "onmouseenter", "onmouseleave", "onmousemove", "onmouseout", "onmouseover", "onmouseup", "onmousewheel", "onmove", "onmoveend", "onmovestart", "onpaste", "onpropertychange", "onselectstart", "palette", "play", "pluginspage", "progress", "quality", "salign", "scale", "song", "src", "style", "swliveconnect", "swremote", "swstretchhalign", "swstretchstyle", "swstretchvalign", "title", "type", "units", "unselectable", "volume", "vspace", "width", "wmode", and "xml:space". <EMBED FlashVars="zoomifyImagePath=./fogli/cgis026a/" SRC="zoomifyViewer.swf" MENU="false" PLUGINSPAGE="http://www.macromedia.A?i??????h????avcom/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash" WIDTH="100%" HEIGHT="200"></EMBED>
116:69 | Error | The attribute value "#FFFFFF" for the "BGCOLOR" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <TABLE BORDER=0 CELLPADDING=1 CELLSPACING=0 BGCOLOR=#FFFFFF WIDTH="750" ALIGN="CENTER">
118:60 | Error (HTML 4.0 Compatibility) | [81] The "align" attribute may not be used with the "p" element in a strict HTML 4.0/4.01 document. Instead of align="center", consider using the CSS "text-align: center" instead. <TD align="Center" valign="middle"> <p align="center">&nbsp; </p>
119:42 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "img" element. The "alt" attribute is critical for accessibility. It lets authors specify equivalent text to serve as content when the image cannot be seen or displayed. Use alt="" when alternate text is not appropriate, such as when images are intended to format a page (such as spacer images).
119:42 | Message (Good Style) | [7] The "height" and "width" attributes should be used with the "img" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style.
119:42 | Message (Search Engine) | [8] Alt text is often used by search engines. Use this to your advantage (but do it appropriately). Furthermore, alt text is critical for accessibility. For these reasons and others, it is highly recommended that appropriate alt text be specified using the "alt" attribute. This message is displayed only once.
121:23 | Error (HTML 4.0 Compatibility) | [81] The "align" attribute may not be used with the "h1" element in a strict HTML 4.0/4.01 document. Instead of align="center", consider using the CSS "text-align: center" instead. <h1 align="center">MAP REALIZED BY THE GEOLOGICAL SURVEY OF ITALY </h1>
122:23 | Error (HTML 4.0 Compatibility) | [81] The "align" attribute may not be used with the "h2" element in a strict HTML 4.0/4.01 document. Instead of align="center", consider using the CSS "text-align: center" instead. <h2 align="center"><font color="#336600">ITALIAN CARTOGRAPHIC BODY </font></h2>
123 | Error | Terminating validation due to too many errors. Please correct the previous errors and recheck the document. HTML Validator is currently set to stop after 20 errors. <h3 align="center"><font color="#336600">(LAW 2/2/1960 N.68)</font></h3>
| Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.
| Comment | You can disable all the error messages for improperly quoted attribute values by having HTML Validator ignore and disregard the quotation mark requirements for attribute values. This option is in CSE HTML Validator's Validator Engine Options. However, it is recommended that you leave these error messages enabled and that you properly enclose attribute values in quotation marks.
| Comment | You can use the Quick Quote Tool in the editor to quickly enclose all attribute values in quotation marks.
| Comment | Possibly misspelled words (9, 9 unique): APAT (1x), di (1x), IDRIA (1x), il (1x), ITALIAN (1x), ITALY (1x), Salta (1x), SiteMap (1x), utilit (1x). NOTE: Validation terminated so not all words were checked.
| Comment | You can change the maximum number of error messages to display before the validation is terminated. This option is in CSE HTML Validator's Validator Engine Options.
| Comment | HTML 4.01 Strict document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #7 - Each page on a site should have its own unique title. Every title should contain appropriate keywords and search terms that are relevent to the page.
| Comment (Search Engine) | [8] <meta name="description" content="(actual description)"> should be used in the "head" section to provide a brief description of what is contained on this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment (Search Engine) | [8] <meta name="keywords" content="(actual keyword list)"> should be used in the "head" section to provide a list of keywords that are relevent to this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment | An ICRA RDF label was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. It is recommended that every page include an ICRA label. For more information, please visit http://www.icra.org/.
| Comment | [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | 7528 bytes; 5.2s@14.4Kbps, 2.6s@28.8, 1.5s@50, 1.2s@64, 0.6s@128, 0.2s@384, 0.1s@512, 0.1s@768, 0.1s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.03s, 21 errors, 1 warning, 15 messages, 14 validator comments, 153 lines, 121 tags (92 closed), 0 document comments, 27 entities, 308 programs run.

[ Summary ] [ To the top ]

### http://www.apat.gov.it/Monitoraggio/database.asp

Line:char | Type | Message Description
--- | --- | ---
| Message (Web Content Accessibility Guidelines 1.0) [ACCESSIBILITY] | [73] WCAG 1.0 accessibility checking is disabled.
| Message (Section 508 Accessibility Standards) [ACCESSIBILITY] | [73] Section 508 accessibility checking is disabled.
2:2 | Message | The first tag in the document was out of range. The document has been checked with the assumption that a block of HTML that belongs in a <html><body> ... </body></html> section is being validated.
11:7 | Message (Deprecated) | [9] The "background", "bgcolor", "text", "link", "vlink", and "alink" attributes for the "body" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of the "bgcolor" attribute, consider using the CSS property "background-color". Example: style="background-color: #CCCC99".
16:2 | Message (General Compatibility) | [5] The "table" element is an official HTML 4.01 and XHTML element but may not be supported by older or nongraphical browsers. Furthermore, nongraphical browsers that do support tables may not support them the way that you expect. However, most browsers used today should support this element.
16:63 | Message (General Compatibility) | [5] The "height" attribute for the "table" element is not an official HTML or XHTML attribute and is currently only supported by some versions of Internet Explorer and Netscape. Note that Netscape 6.0+ does not support this attribute.
22:20 | Message (Deprecated) | [9] The "height" and "width" attributes for the "td" and "th" elements are deprecated in HTML 4.01 and XHTML in favor of using style sheets.
25:10 | Message (Deprecated) | [9] The "align" attribute is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of align="center", consider using the CSS "text-align: center" instead.
25:26 | Message (Good Style) | The "strong" element should be used instead of the "b" element when you want to denote strong emphasis. The "b" element should only be used when you want bold typeface but do not want strong emphasis. Many web authors use the "b" element when the "strong" element would be more appropriate.
25:29 | Message (Deprecated) | [9] The "font" element and all of its attributes are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the "color", "font", "font-family", "font-size", and other CSS font properties instead).
28:4 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "img" element. The "alt" attribute is critical for accessibility. It lets authors specify equivalent text to serve as content when the image cannot be seen or displayed. Use alt="" when alternate text is not appropriate, such as when images are intended to format a page (such as spacer images).
28:4 | Message (Search Engine) | [8] Alt text is often used by search engines. Use this to your advantage (but do it appropriately). Furthermore, alt text is critical for accessibility. For these reasons and others, it is highly recommended that appropriate alt text be specified using the "alt" attribute. This message is displayed only once.
36:2 | Error | There may be only one "body" section in an HTML or XHTML document. The "body" element has been used 2 times. <body bgcolor="#CCCC99">
37:2 | Warning | [56] The "p" tag is contained in a "p" tag that was opened in line 34. This is against the HTML specification and may cause problems with some browsers.
39:50 | Message (CSS Tips) [CSS] | Use the inline "style" attribute sparingly. Using this attribute too often can prevent you from receiving many of the benefits of CSS like easier to maintain and less cluttered documents. Consider using a single CSS style sheet instead of relying too much on the "style" attribute. This message is displayed only once.
41:12 | Message (Good Style) | It is usually best not to specify the actual index document name "index.asp". Consider using href="./" instead. Visit http://webtips.dan.info/subdir.html#LinkHome for more information about why this is recommended.
42:70 | Error | The end tag for "a" was found, but "a" was never opened, has been ended too many times, or cannot have an end tag. <font color="#800000">Introduzione</font></span></a></font></span></a> </font>
57:11 | Warning | The "a" tag contains no link text. Though it is not technically required, it is recommended that all "a" elements contain appropriate link text or an appropriate element, like "img".
61:2 | Error | The end tag for "body" (opened in line 36) should appear before the end tag for "p" (nesting error). </p>
68:8 | Message (Deprecated) | [9] Even though the "center" element is deprecated in HTML 4.01 and XHTML, real-world circumstances may make using this element better than using CSS in some situations. Using CSS may be more complex and may not easily (or at all) give the desired effect of centering blocks like forms and tables. However, AI Internet Solutions still recommends using CSS whenever reasonably possible.
68:8 | Message (Deprecated) | [9] The "center" element is deprecated in HTML 4.01 and XHTML in favor of using style sheets (to center text use the CSS "text-align: center" instead or align="center" where "align" is not deprecated). Another option is to use <div style="text-align: center">...</div> instead of <center>...</center>, but this may not center tables. The "center" element may become obsolete and unsupported in the future.
72:4 | Message | [41] The "div" tag has no attributes. Attributes are normally used with the "div" element to provide functionality.
76:276 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:572 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:759 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:1036 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:1222 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:1473 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:1684 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:1881 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:2085 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:2240 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:2386 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:2573 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:2738 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:2887 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:3112 | Error | A quoted string (like an attribute value) cannot be immediately followed by text. It must be followed by a space or by the end of the tag. Is there a missing space character? <p align="center"><b><font face="Verdana" color="#996600">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font></b><b><font face="Verdana" color="#996600">&nbsp;&nbsp;</font></b><map name="FPMap0" id=FPMap0 ><area shape="poly" href="javascript:invia('01')" alt=Piemonte coords="10, 26, 9, 30, 6, 33, 9, 37, 7, 40, 7, 43, 9, 45, 14, 47, 16, 47, 19, 46, 21, 41, 27, 41, 30, 40, 31, 37, 28, 34, 26, 34, 24, 30, 29, 29, 25, 21, 26, 18, 24, 13, 21, 15, 19, 19, 20, 23, 18, 27, 10, 26" title="Piemonte"><area shape="poly" href="javascript:invia('02')" alt="Valle D'Aosta" coords="8, 21, 10, 20, 13, 20, 16, 19, 18, 19, 20, 22, 19, 24, 17, 26, 12, 25, 11, 26, 9, 24, 7, 22" title="Valle d'Aosta" ><area shape="poly" href="javascript:invia('03')" alt=Lombardia coords="26, 19, 25, 22, 28, 28, 25, 31, 26, 35, 31, 38, 36, 33, 41, 36, 52, 36, 50, 32, 46, 27, 47, 23, 44, 19, 44, 17, 46, 13, 41, 11, 39, 14, 35, 14, 33, 11, 32, 16, 29, 19, 26, 17" title="Lombardia"><area shape="poly" href="javascript:invia('04')" alt="Trentino Alto Adige" coords="44, 10, 46, 6, 49, 9, 54, 4, 60, 3, 61, 7, 59, 12, 58, 17, 50, 24, 46, 20, 44, 16, 45, 8" title="Trentino Alto Adige"><area shape="poly" href="javascript:invia('05')" alt=Veneto coords="62, 8, 65, 13, 64, 20, 66, 22, 68, 22, 70, 24, 69, 25, 64, 28, 61, 30, 64, 35, 63, 37, 59, 34, 55, 37, 52, 35, 47, 28, 47, 22, 51, 23, 57, 18, 62, 10" title="Veneto"><area shape="poly" href="javascript:invia('06')" alt="Friuli Venezia Giulia" coords="76, 26, 72, 24, 70, 24, 68, 20, 65, 21, 63, 18, 65, 15, 64, 11, 68, 10, 75, 12, 72, 16, 75, 20, 75, 23, 78, 26" title="Friuli Venezia Giulia"><area shape="poly" href="javascript:invia('07')" alt=Liguria coords="14, 47, 16, 49, 14, 53, 19, 51, 23, 46, 27, 43, 31, 46, 38, 50, 36, 43, 29, 39, 24, 41, 19, 43, 18, 46, 14, 47" title="Liguria"><area shape="poly" href="javascript:invia('09')" alt=Toscana coords="36, 45, 41, 53, 44, 62, 41, 68, 46, 67, 52, 74, 53, 76, 58, 68, 61, 61, 59, 59, 62, 55, 53, 47, 49, 50, 38, 43, 37, 50" title="Toscana"><area shape="poly" href="javascript:invia('10')" alt=Umbria coords="62, 55, 60, 60, 60, 61, 58, 68, 63, 73, 71, 69, 69, 63, 68, 58, 62, 55" title="Umbria"><area shape="poly" href="javascript:invia('11')" alt=Marche coords="61, 55, 66, 57, 70, 67, 73, 69, 78, 67, 76, 57, 67, 50, 61, 52" title="Marche"><area shape="poly" href="javascript:invia('12')" alt=Lazio coords="57, 68, 52, 75, 62, 85, 67, 90, 77, 92, 81, 87, 80, 84, 76, 84, 70, 78, 73, 75, 70, 70, 64, 73, 58, 68" title="Lazio"><area shape="poly" href="javascript:invia('13')" alt=Abruzzo coords="77, 66, 72, 72, 72, 75, 70, 78, 77, 85, 81, 86, 84, 81, 90, 79, 82, 73, 78, 64" title="Abruzzo" ><area shape="poly" href="javascript:invia('14')" alt=Molise coords="80, 87, 84, 88, 88, 90, 93, 83, 91, 81, 87, 77, 85, 83, 81, 83" title="Molise"><area shape="poly" href="javascript:invia('15')" alt=Campania coords="76, 93, 81, 87, 87, 90, 90, 87, 95, 93, 97, 95, 93, 98, 97, 101, 99, 105, 99, 108, 98, 110, 95, 110, 91, 107, 89, 102, 85, 102, 85, 98, 80, 98, 78, 93" title="Campania"><area shape="poly" href="javascript:invia('16')"alt=Puglia coords="89, 88, 93, 82, 102, 80, 104, 81, 99, 87, 104, 89, 114, 92, 122, 98, 129, 104, 127, 111, 122, 104, 111, 101, 108, 97, 106, 97, 101, 94, 96, 93, 90, 88" title="Puglia"><area shape="poly" href="javascript:invia('17')" alt=Basilicata coords="95, 94, 93, 98, 97, 101, 100, 104, 99, 108, 103, 110, 110, 107, 112, 101, 108, 99, 103, 95, 102, 93, 95, 93" title="Basilicata" ><area shape="poly" href="javascript:invia('18')" alt=Calabria coords="98, 109, 104, 124, 104, 127, 100, 131, 102, 134, 99, 136, 100, 141, 102, 141, 110, 134, 109, 129, 111, 126, 116, 126, 116, 120, 115, 117, 107, 114, 107, 113, 110, 110, 107, 106, 103, 111, 99, 107, 98, 111" title="Calabria"><area shape="poly" href="javascript:invia('19')" alt=Sicilia coords="97, 138, 94, 148, 95, 150, 97, 154, 96, 155, 94, 157, 94, 160, 91, 161, 84, 153, 81, 155, 64, 145, 67, 138, 70, 139, 73, 137, 77, 140, 80, 140, 89, 140, 91, 136, 98, 137" title="Sicilia" ><area shape="poly" href="javascript:invia('20')" alt=Sardegna coords="18, 95, 17, 99, 19, 104, 21, 107, 18, 109, 21, 112, 19, 122, 22, 126, 27, 124, 29, 122, 33, 122, 35, 119, 34, 108, 34, 106, 36, 102, 34, 94, 30, 91, 23, 96, 17, 97" title="Sardegna"><area shape="poly" href="javascript:invia('08')" alt="Emilia Romagna" coords="28, 40, 32, 37, 35, 32, 43, 37, 53, 36, 55, 37, 60, 35, 63, 37, 61, 40, 63, 44, 62, 46, 66, 49, 60, 53, 55, 51, 52, 46, 48, 49, 31, 41" title="Emilia Romagna"></map><IMG id=Italia style="border-style:inset; border-width:3px; WIDTH: 135px; HEIGHT: 162px; padding-left:4px; padding-right:4px; padding-top:1px; padding-bottom:1px" width="135" height="162" src="MiniItalia2.gif" useMap=#FPMap0 border=5 NAME="display"><b><font face="Verdana" color="#996600">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
76:3123 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:3362 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76:3561 | Warning | The value for the "coords" attribute contains spaces when it should not. It should be a comma separated list of length values (integers or percentages). For polygons, the value for the "coords" attribute should be in the following format: "x1,y1,x2,y2,x3,y3,...,xN,yN". Note that the first x,y coordinate should be the same as the last. When they're not the same, the user agent should infer an additional coordinate pair to close the polygon.
76 | Error | Terminating validation due to too many warnings. Please correct the previous warnings and recheck the document. HTML Validator is currently set to stop after 20 warnings. <p align="center"><b><font face="Verdana" color="#996600">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font></b><b><font face="Verdana" color="#996600">&nbsp;&nbsp;</font></b><map name="FPMap0" id=FPMap0 ><area shape="poly" href="javascript:invia('01')" alt=Piemonte coords="10, 26, 9, 30, 6, 33, 9, 37, 7, 40, 7, 43, 9, 45, 14, 47, 16, 47, 19, 46, 21, 41, 27, 41, 30, 40, 31, 37, 28, 34, 26, 34, 24, 30, 29, 29, 25, 21, 26, 18, 24, 13, 21, 15, 19, 19, 20, 23, 18, 27, 10, 26" title="Piemonte"><area shape="poly" href="javascript:invia('02')" alt="Valle D'Aosta" coords="8, 21, 10, 20, 13, 20, 16, 19, 18, 19, 20, 22, 19, 24, 17, 26, 12, 25, 11, 26, 9, 24, 7, 22" title="Valle d'Aosta" ><area shape="poly" href="javascript:invia('03')" alt=Lombardia coords="26, 19, 25, 22, 28, 28, 25, 31, 26, 35, 31, 38, 36, 33, 41, 36, 52, 36, 50, 32, 46, 27, 47, 23, 44, 19, 44, 17, 46, 13, 41, 11, 39, 14, 35, 14, 33, 11, 32, 16, 29, 19, 26, 17" title="Lombardia"><area shape="poly" href="javascript:invia('04')" alt="Trentino Alto Adige" coords="44, 10, 46, 6, 49, 9, 54, 4, 60, 3, 61, 7, 59, 12, 58, 17, 50, 24, 46, 20, 44, 16, 45, 8" title="Trentino Alto Adige"><area shape="poly" href="javascript:invia('05')" alt=Veneto coords="62, 8, 65, 13, 64, 20, 66, 22, 68, 22, 70, 24, 69, 25, 64, 28, 61, 30, 64, 35, 63, 37, 59, 34, 55, 37, 52, 35, 47, 28, 47, 22, 51, 23, 57, 18, 62, 10" title="Veneto"><area shape="poly" href="javascript:invia('06')" alt="Friuli Venezia Giulia" coords="76, 26, 72, 24, 70, 24, 68, 20, 65, 21, 63, 18, 65, 15, 64, 11, 68, 10, 75, 12, 72, 16, 75, 20, 75, 23, 78, 26" title="Friuli Venezia Giulia"><area shape="poly" href="javascript:invia('07')" alt=Liguria coords="14, 47, 16, 49, 14, 53, 19, 51, 23, 46, 27, 43, 31, 46, 38, 50, 36, 43, 29, 39, 24, 41, 19, 43, 18, 46, 14, 47" title="Liguria"><area shape="poly" href="javascript:invia('09')" alt=Toscana coords="36, 45, 41, 53, 44, 62, 41, 68, 46, 67, 52, 74, 53, 76, 58, 68, 61, 61, 59, 59, 62, 55, 53, 47, 49, 50, 38, 43, 37, 50" title="Toscana"><area shape="poly" href="javascript:invia('10')" alt=Umbria coords="62, 55, 60, 60, 60, 61, 58, 68, 63, 73, 71, 69, 69, 63, 68, 58, 62, 55" title="Umbria"><area shape="poly" href="javascript:invia('11')" alt=Marche coords="61, 55, 66, 57, 70, 67, 73, 69, 78, 67, 76, 57, 67, 50, 61, 52" title="Marche"><area shape="poly" href="javascript:invia('12')" alt=Lazio coords="57, 68, 52, 75, 62, 85, 67, 90, 77, 92, 81, 87, 80, 84, 76, 84, 70, 78, 73, 75, 70, 70, 64, 73, 58, 68" title="Lazio"><area shape="poly" href="javascript:invia('13')" alt=Abruzzo coords="77, 66, 72, 72, 72, 75, 70, 78, 77, 85, 81, 86, 84, 81, 90, 79, 82, 73, 78, 64" title="Abruzzo" ><area shape="poly" href="javascript:invia('14')" alt=Molise coords="80, 87, 84, 88, 88, 90, 93, 83, 91, 81, 87, 77, 85, 83, 81, 83" title="Molise"><area shape="poly" href="javascript:invia('15')" alt=Campania coords="76, 93, 81, 87, 87, 90, 90, 87, 95, 93, 97, 95, 93, 98, 97, 101, 99, 105, 99, 108, 98, 110, 95, 110, 91, 107, 89, 102, 85, 102, 85, 98, 80, 98, 78, 93" title="Campania"><area shape="poly" href="javascript:invia('16')"alt=Puglia coords="89, 88, 93, 82, 102, 80, 104, 81, 99, 87, 104, 89, 114, 92, 122, 98, 129, 104, 127, 111, 122, 104, 111, 101, 108, 97, 106, 97, 101, 94, 96, 93, 90, 88" title="Puglia"><area shape="poly" href="javascript:invia('17')" alt=Basilicata coords="95, 94, 93, 98, 97, 101, 100, 104, 99, 108, 103, 110, 110, 107, 112, 101, 108, 99, 103, 95, 102, 93, 95, 93" title="Basilicata" ><area shape="poly" href="javascript:invia('18')" alt=Calabria coords="98, 109, 104, 124, 104, 127, 100, 131, 102, 134, 99, 136, 100, 141, 102, 141, 110, 134, 109, 129, 111, 126, 116, 126, 116, 120, 115, 117, 107, 114, 107, 113, 110, 110, 107, 106, 103, 111, 99, 107, 98, 111" title="Calabria"><area shape="poly" href="javascript:invia('19')" alt=Sicilia coords="97, 138, 94, 148, 95, 150, 97, 154, 96, 155, 94, 157, 94, 160, 91, 161, 84, 153, 81, 155, 64, 145, 67, 138, 70, 139, 73, 137, 77, 140, 80, 140, 89, 140, 91, 136, 98, 137" title="Sicilia" ><area shape="poly" href="javascript:invia('20')" alt=Sardegna coords="18, 95, 17, 99, 19, 104, 21, 107, 18, 109, 21, 112, 19, 122, 22, 126, 27, 124, 29, 122, 33, 122, 35, 119, 34, 108, 34, 106, 36, 102, 34, 94, 30, 91, 23, 96, 17, 97" title="Sardegna"><area shape="poly" href="javascript:invia('08')" alt="Emilia Romagna" coords="28, 40, 32, 37, 35, 32, 43, 37, 53, 36, 55, 37, 60, 35, 63, 37, 61, 40, 63, 44, 62, 46, 66, 49, 60, 53, 55, 51, 52, 46, 48, 49, 31, 41" title="Emilia Romagna"></map><IMG id=Italia style="border-style:inset; border-width:3px; WIDTH: 135px; HEIGHT: 162px; padding-left:4px; padding-right:4px; padding-top:1px; padding-bottom:1px" width="135" height="162" src="MiniItalia2.gif" useMap=#FPMap0 border=5 NAME="display"><b><font face="Verdana" color="#996600">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.
| Comment | You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options.
| Comment | Possibly misspelled words (48, 45 unique): Abruzzo (1x), Adige (1x), ai (1x), Attività (1x), Banca (1x), Basilicata (1x), Calabria (1x), Campania (1x), ContentHead (1x), D'Aosta (1x), Dati (1x), DecArea (1x), degli (1x), finanziati (1x), Friuli (1x), Giulia (1x), interesse (1x), interventi (1x), Introduzione (1x), l'area (1x), Lazio (1x), Liguria (1x), Lombardia (1x), Marche (1x), Molise (1x), MSTableType (1x), normativo (1x), Piemonte (1x), Puglia (1x), Quadro (1x), regione (1x), Ricerca (1x), Selezionare (1x), sensi (1x), Sicilia (1x), Toscana (1x), Trentino (1x), Umbria (1x), urgenti (1x), Valle (1x), Veneto (1x), Venezia (1x), di (2x), MONITORAGGIO (2x), MSCellType (2x). NOTE: Validation terminated so not all words were checked.
| Comment | You can change the maximum number of warning messages to display before the validation is terminated. This option is in CSE HTML Validator's Validator Engine Options.
| Comment | HTML document detected.
| Comment | [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | 19310 bytes; 13.4s@14.4Kbps, 6.7s@28.8, 3.9s@50, 3.0s@64, 1.5s@128, 0.5s@384, 0.4s@512, 0.3s@768, 0.1s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.03s, 5 errors, 20 warnings, 16 messages, 9 validator comments, 157 lines, 84 tags (52 closed), 5 document comments, 52 entities, 291 programs run.

[ Summary ] [ To the top ]

### http://www.apat.gov.it/Museo/archeocitest.html

Line:char | Type | Message Description
--- | --- | ---
| Message (Web Content Accessibility Guidelines 1.0) [ACCESSIBILITY] | [73] WCAG 1.0 accessibility checking is disabled.
| Message (Section 508 Accessibility Standards) [ACCESSIBILITY] | [73] Section 508 accessibility checking is disabled.
2:1 | Warning | [24] A document type declaration should normally appear as the second line for XHTML documents (the first line should be an XML declaration). For example, for XHTML 1.0 Strict documents, <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> should be the second line (or the first line if there is no XML declaration). For XHTML 1.0 Transitional documents, the line should be <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd">. For XHTML 1.0 Frameset documents, the line should be <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN" "DTD/xhtml1-frameset.dtd">. Although the XHTML recommendation requires this line, most browsers probably ignore it. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
2:1 | Error | The "xmlns:w" attribute is not valid for the "html" element. Some valid attributes for this element are: "dir", "lang", "version", and "xmlns". xmlns:w="urn:schemas-microsoft-com:office:word"
6:2 | Error | The "meta" tag must be closed by either adding a slash to the end of the tag if proper (<meta ... />) (empty element shorthand) or using a separate end tag (</meta>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <meta http-equiv=Content-Type content="text/html; charset=windows-1252">
6:18 | Error | The attribute value "Content-Type" for the "http-equiv" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta http-equiv=Content-Type content="text/html; charset=windows-1252">
7:2 | Error | The "meta" tag must be closed by either adding a slash to the end of the tag if proper (<meta ... />) (empty element shorthand) or using a separate end tag (</meta>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <meta name=ProgId content=Word.Document>
7:12 | Error | The attribute value "ProgId" for the "name" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=ProgId content=Word.Document>
7:27 | Error | The attribute value "Word.Document" for the "content" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=ProgId content=Word.Document>
8:2 | Error | The "meta" tag must be closed by either adding a slash to the end of the tag if proper (<meta ... />) (empty element shorthand) or using a separate end tag (</meta>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <meta name=Generator content="Microsoft Word 9">
8:12 | Error | The attribute value "Generator" for the "name" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=Generator content="Microsoft Word 9">
9:2 | Error | The "meta" tag must be closed by either adding a slash to the end of the tag if proper (<meta ... />) (empty element shorthand) or using a separate end tag (</meta>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <meta name=Originator content="Microsoft Word 9">
9:12 | Error | The attribute value "Originator" for the "name" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=Originator content="Microsoft Word 9">
10:2 | Error | The "link" tag must be closed by either adding a slash to the end of the tag if proper (<link ... />) (empty element shorthand) or using a separate end tag (</link>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <link rel=File-List href="./archeocitest_new_file/filelist.xml">
10:11 | Error | The attribute value "File-List" for the "rel" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <link rel=File-List href="./archeocitest_new_file/filelist.xml">
11:2 | Message (Search Engine) | Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: <title>Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows</title>. AI Internet Solutions also recommends that the "title" tag be the first tag inside the "head" section.
11:8 | Message (Search Engine) | [8] This document's title contains only 2 words. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable.
17:2 | Warning | HTML 4.01 and XHTML require the "type" attribute for the "style" element to specify the style sheet language. For example, use type="text/css". Note that many browsers may work without this attribute but it is highly recommended that it be used.
18:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers.
21:3 | Message (General) [CSS] | Found the Microsoft Office property "mso-style-parent". HTML Validator ignores these proprietary properties that begin with "mso-". This message is displayed only once. There may be other proprietary properties.
23:2 | Warning (General) [CSS] | The "margin" shorthand property and the "margin-bottom" property have both been used. The "margin" shorthand property already defines the following properties: "margin-bottom", "margin-left", "margin-right", and "margin-top". Therefore, the "margin-bottom" property has been defined twice. Consider using only the "margin" shorthand property.
26:15 | Warning (General) [CSS] | It is recommended that a generic font family name be specified as the last font family name. If the preceding font family names are not available then the browser should fall back to the generic font family name. The generic font family names are serif, sans-serif, cursive, fantasy, and monospace. Be sure not to use quotes around generic font family names.
30:15 | Warning (General) [CSS] | It is recommended that a generic font family name be specified as the last font family name. If the preceding font family names are not available then the browser should fall back to the generic font family name. The generic font family names are serif, sans-serif, cursive, fantasy, and monospace. Be sure not to use quotes around generic font family names.
33:3 | Message (General Compatibility) [CSS] | [603] The "size" CSS property is an official CSS2 (but not CSS1) property and is not supported by Internet Explorer and Netscape. This includes Internet Explorer 6.0- and Netscape 6.2-.
35:2 | Error (General) [CSS] | The "mso-header-margin" property is not a recognized style property for @page blocks. Is it misspelled? mso-header-margin:35.4pt;
36:2 | Error (General) [CSS] | The "mso-footer-margin" property is not a recognized style property for @page blocks. Is it misspelled? mso-footer-margin:35.4pt;
37:2 | Error (General) [CSS] | The "mso-paper-source" property is not a recognized style property for @page blocks. Is it misspelled? mso-paper-source:0;}
39:3 | Message (General Compatibility) [CSS] | [603] The "page" CSS property is an official CSS2 (but not CSS1) property but is not currently supported by Internet Explorer, Netscape, and Opera. This includes Internet Explorer 6.0-, Netscape 6.2-, and Opera 6.0-.
44:12 | Error | The attribute value "IT" for the "lang" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <body lang=IT style='tab-interval:35.4pt' bgcolor="#FFFFFF">
44:22 | Error (General) [CSS] | The "tab-interval" property is not a recognized style property. Is it misspelled? <body lang=IT style='tab-interval:35.4pt' bgcolor="#FFFFFF">
44:15 | Message (General) [CSS] | The "style" attribute has been used but a default style sheet language has not been defined (note that HTML Validator would not see this declaration if it is sent as an HTTP header by a web server). HTML 4.01 and XHTML require this for correct documents. However, for all practical purposes, leaving it out is very unlikely to cause problems. If you still want to define a default style sheet language, then include this in the "head" section of your document to specify "text/css" as the default style sheet language: <meta http-equiv="Content-Style-Type" content="text/css" />. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. Because this issue is very unlikely to cause problems, consider ignoring or disabling this message. See http://www.w3.org/TR/html4/present/styles.html#default-style for more information.
44:15 | Message (CSS Tips) [CSS] | Use the inline "style" attribute sparingly. Using this attribute too often can prevent you from receiving many of the benefits of CSS like easier to maintain and less cluttered documents. Consider using a single CSS style sheet instead of relying too much on the "style" attribute. This message is displayed only once.
44:43 | Message (Deprecated) | [9] The "background", "bgcolor", "text", "link", "vlink", and "alink" attributes for the "body" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of the "bgcolor" attribute, consider using the CSS property "background-color". Example: style="background-color: #FFFFFF".
45:12 | Error | The attribute value "Section1" for the "class" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <div class=Section1> <b><font face="Verdana, Arial, Helvetica, sans-serif">ARCHEOCIATINE</font></b><font face="Verdana, Arial, Helvetica, sans-serif"><span style='font-size:13.5pt'></span></font><font face="Verdana, Arial, Helvetica, sans-serif"><span style='font-size:13.5pt'></span></font>
45:101 | Warning | The "font" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text.
45:197 | Warning | The "font" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text.
45:23 | Message (Good Style) | The "strong" element should be used instead of the "b" element when you want to denote strong emphasis. The "b" element should only be used when you want bold typeface but do not want strong emphasis. Many web authors use the "b" element when the "strong" element would be more appropriate.
45:26 | Message (Deprecated) | [9] The "font" element and all of its attributes are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the "color", "font", "font-family", "font-size", and other CSS font properties instead).
46:4 | Error | The "hr" tag must be closed by either adding a slash to the end of the tag if proper (<hr ... />) (empty element shorthand) or using a separate end tag (</hr>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <hr>
47:4 | Warning | The "font" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text.
53:69 | Message (Good Style) | The "em" element (for emphasized text) or the "cite" element (for citations) may be more appropriate than the "i" element. Use the "i" element only if text is in italics by convention. Many web authors use the "i" element when the "em" element would be more appropriate.
57:32 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 57. These codepoints are commonly found in Windows character sets like Windows-1252 but may not work for everyone, especially those not using Windows. Consider using "&#8217;" instead of this character.
| Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.
| Comment | You can disable all the error messages for improperly quoted attribute values by having HTML Validator ignore and disregard the quotation mark requirements for attribute values. This option is in CSE HTML Validator's Validator Engine Options. However, it is recommended that you leave these error messages enabled and that you properly enclose attribute values in quotation marks.
| Comment | You can use the Quick Quote Tool in the editor to quickly enclose all attribute values in quotation marks.
| Comment | You may want to turn off 128-159 character checking if you're sure that these characters will be interpreted and displayed properly by the visiting user agents. This option is in CSE HTML Validator's Validator Engine Options.
| Comment | Possibly misspelled words (119, 97 unique): acque (1x), alla (1x), apparati (1x), assunto (1x), basse (1x), bentoniche (1x), calcarei (1x), calcareo (1x), calde (1x), calice (1x), causa (1x), completamente (1x), comunemente (1x), conica (1x), cono (1x), considerati (1x), costa (1x), costituiti (1x), costruire (1x), dall’apice (1x), della (1x), detto (1x), distribuirsi (1x), endif (1x), Esse (1x), esterna (1x), estinti (1x), fissate (1x), fondali (1x), fondo (1x), formando (1x), formato (1x), fossili (1x), funzione (1x), gte (1x), guida (1x), hanno (1x), inferiore (1x), interna (1x), Intervallum (1x), linee (1x), litogenetica (1x), loro (1x), lungo (1x), marini (1x), marino (1x), medio (1x), meno (1x), mso (1x), nelle (1x). List limited to first 50 unique words.
| Comment | XHTML document detected.
| Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration.
| Comment (Search Engine) | [113] Random Search Engine Tip #7 - Each page on a site should have its own unique title. Every title should contain appropriate keywords and search terms that are relevent to the page.
| Comment (Search Engine) | [8] <meta name="description" content="(actual description)" /> should be used in the "head" section to provide a brief description of what is contained on this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment (Search Engine) | [8] <meta name="keywords" content="(actual keyword list)" /> should be used in the "head" section to provide a list of keywords that are relevent to this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment | An ICRA RDF label was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. It is recommended that every page include an ICRA label. For more information, please visit http://www.icra.org/.
| Comment | [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | 2946 bytes; 2.0s@14.4Kbps, 1.0s@28.8, 0.6s@50, 0.5s@64, 0.2s@128, 0.1s@384, 0.1s@512, 0.0s@768, 0.0s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.01s, 19 errors, 10 warnings, 13 messages, 15 validator comments, 66 lines, 32 tags (26 closed), 1 document comment, 2 entities, 78 programs run.

[ Summary ] [ To the top ]

### http://www.apat.gov.it/Museo/graptotesto.html

Line:char | Type | Message Description
--- | --- | ---
| Message (Web Content Accessibility Guidelines 1.0) [ACCESSIBILITY] | [73] WCAG 1.0 accessibility checking is disabled.
| Message (Section 508 Accessibility Standards) [ACCESSIBILITY] | [73] Section 508 accessibility checking is disabled.
2:1 | Warning | [24] A document type declaration should normally appear as the second line for XHTML documents (the first line should be an XML declaration). For example, for XHTML 1.0 Strict documents, <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> should be the second line (or the first line if there is no XML declaration). For XHTML 1.0 Transitional documents, the line should be <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd">. For XHTML 1.0 Frameset documents, the line should be <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN" "DTD/xhtml1-frameset.dtd">. Although the XHTML recommendation requires this line, most browsers probably ignore it. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
3:1 | Error | The "xmlns:w" attribute is not valid for the "html" element. Some valid attributes for this element are: "dir", "lang", "version", and "xmlns". xmlns:w="urn:schemas-microsoft-com:office:word"
7:2 | Error | The "meta" tag must be closed by either adding a slash to the end of the tag if proper (<meta ... />) (empty element shorthand) or using a separate end tag (</meta>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <meta http-equiv=Content-Type content="text/html; charset=windows-1252">
7:18 | Error | The attribute value "Content-Type" for the "http-equiv" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta http-equiv=Content-Type content="text/html; charset=windows-1252">
8:12 | Error | The attribute value "ProgId" for the "name" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=ProgId content=Word.Document>
8:27 | Error | The attribute value "Word.Document" for the "content" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=ProgId content=Word.Document>
9:12 | Error | The attribute value "Generator" for the "name" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=Generator content="Microsoft Word 9">
10:12 | Error | The attribute value "Originator" for the "name" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=Originator content="Microsoft Word 9">
11:11 | Error | The attribute value "File-List" for the "rel" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <link rel=File-List href="./graptotesto_new_file/filelist.xml">
12:11 | Error | The attribute value "Edit-Time-Data" for the "rel" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <link rel=Edit-Time-Data href="./graptotesto_new_file/editdata.mso">
21:2 | Message (Search Engine) | Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: <title>Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows</title>. AI Internet Solutions also recommends that the "title" tag be the first tag inside the "head" section.
21:8 | Message (Search Engine) | [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable.
27:2 | Warning | HTML 4.01 and XHTML require the "type" attribute for the "style" element to specify the style sheet language. For example, use type="text/css". Note that many browsers may work without this attribute but it is highly recommended that it be used.
28:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers.
31:3 | Message (General) [CSS] | Found the Microsoft Office property "mso-style-parent". HTML Validator ignores these proprietary properties that begin with "mso-". This message is displayed only once. There may be other proprietary properties.
33:2 | Warning (General) [CSS] | The "margin" shorthand property and the "margin-bottom" property have both been used. The "margin" shorthand property already defines the following properties: "margin-bottom", "margin-left", "margin-right", and "margin-top". Therefore, the "margin-bottom" property has been defined twice. Consider using only the "margin" shorthand property.
36:15 | Warning (General) [CSS] | It is recommended that a generic font family name be specified as the last font family name. If the preceding font family names are not available then the browser should fall back to the generic font family name. The generic font family names are serif, sans-serif, cursive, fantasy, and monospace. Be sure not to use quotes around generic font family names.
40:15 | Warning (General) [CSS] | It is recommended that a generic font family name be specified as the last font family name. If the preceding font family names are not available then the browser should fall back to the generic font family name. The generic font family names are serif, sans-serif, cursive, fantasy, and monospace. Be sure not to use quotes around generic font family names.
43:3 | Message (General Compatibility) [CSS] | [603] The "size" CSS property is an official CSS2 (but not CSS1) property and is not supported by Internet Explorer and Netscape. This includes Internet Explorer 6.0- and Netscape 6.2-.
45:2 | Error (General) [CSS] | The "mso-header-margin" property is not a recognized style property for @page blocks. Is it misspelled? mso-header-margin:35.4pt;
46:2 | Error (General) [CSS] | The "mso-footer-margin" property is not a recognized style property for @page blocks. Is it misspelled? mso-footer-margin:35.4pt;
47:2 | Error (General) [CSS] | The "mso-paper-source" property is not a recognized style property for @page blocks. Is it misspelled? mso-paper-source:0;}
49:3 | Message (General Compatibility) [CSS] | [603] The "page" CSS property is an official CSS2 (but not CSS1) property but is not currently supported by Internet Explorer, Netscape, and Opera. This includes Internet Explorer 6.0-, Netscape 6.2-, and Opera 6.0-.
60:15 | Error | The attribute value "#FFFFFF" for the "bgcolor" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <body bgcolor=#FFFFFF lang=IT style='tab-interval:35.4pt'>
60:28 | Error | The attribute value "IT" for the "lang" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <body bgcolor=#FFFFFF lang=IT style='tab-interval:35.4pt'>
60:38 | Error (General) [CSS] | The "tab-interval" property is not a recognized style property. Is it misspelled? <body bgcolor=#FFFFFF lang=IT style='tab-interval:35.4pt'>
60:7 | Message (Deprecated) | [9] The "background", "bgcolor", "text", "link", "vlink", and "alink" attributes for the "body" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of the "bgcolor" attribute, consider using the CSS property "background-color". Example: style="background-color: #FFFFFF".
60:31 | Message (General) [CSS] | The "style" attribute has been used but a default style sheet language has not been defined (note that HTML Validator would not see this declaration if it is sent as an HTTP header by a web server). HTML 4.01 and XHTML require this for correct documents. However, for all practical purposes, leaving it out is very unlikely to cause problems. If you still want to define a default style sheet language, then include this in the "head" section of your document to specify "text/css" as the default style sheet language: <meta http-equiv="Content-Style-Type" content="text/css" />. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. Because this issue is very unlikely to cause problems, consider ignoring or disabling this message. See http://www.w3.org/TR/html4/present/styles.html#default-style for more information.
60:31 | Message (CSS Tips) [CSS] | Use the inline "style" attribute sparingly. Using this attribute too often can prevent you from receiving many of the benefits of CSS like easier to maintain and less cluttered documents. Consider using a single CSS style sheet instead of relying too much on the "style" attribute. This message is displayed only once.
61:2 | Message (Deprecated) | [9] The "font" element and all of its attributes are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the "color", "font", "font-family", "font-size", and other CSS font properties instead).
61:53 | Message (Good Style) | The "strong" element should be used instead of the "b" element when you want to denote strong emphasis. The "b" element should only be used when you want bold typeface but do not want strong emphasis. Many web authors use the "b" element when the "strong" element would be more appropriate.
66:4 | Message (Deprecated) | [9] The "align" attribute is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of align="left", consider using the CSS "text-align: left" instead.
67:15 | Message (Good Style) | [7] Underlining text may confuse your visitors because most browsers use underlining to emphasize hyperlinks.
67:15 | Message (Deprecated) | [9] The "u" element is deprecated in HTML 4.01 and XHTML in favor of using style sheets ("text-decoration: underline").
74:53 | Error | Found an invalid character reference "&#146;". Characters between 128 and 159 (inclusive) are typically Microsoft specific and are reserved for control characters in the standard Internet character sets. They are undefined in HTML and illegal in XHTML. Therefore they should not be used in HTML/XHTML documents. Consider using "&#8217;" instead. If, for some reason, you still want to use character references 128-159, then you can set an option to allow them in the Validator Engine Options. in cui ogni dentello, detto Idroteca, costituiva l&#146;abitacolo di ciascun polipo.
78:50 | Error | Found an invalid character reference "&#146;". Characters between 128 and 159 (inclusive) are typically Microsoft specific and are reserved for control characters in the standard Internet character sets. They are undefined in HTML and illegal in XHTML. Therefore they should not be used in HTML/XHTML documents. Consider using "&#8217;" instead. If, for some reason, you still want to use character references 128-159, then you can set an option to allow them in the Validator Engine Options. e una vita temporale molto breve, ha permesso l&#146;utilizzo di questi fossili come
79:10 | Message (Good Style) | The "em" element (for emphasized text) or the "cite" element (for citations) may be more appropriate than the "i" element. Use the "i" element only if text is in italics by convention. Many web authors use the "i" element when the "em" element would be more appropriate.
82:4 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "img" element. The "alt" attribute is critical for accessibility. It lets authors specify equivalent text to serve as content when the image cannot be seen or displayed. Use alt="" when alternate text is not appropriate, such as when images are intended to format a page (such as spacer images).
82:4 | Message (Search Engine) | [8] Alt text is often used by search engines. Use this to your advantage (but do it appropriately). Furthermore, alt text is critical for accessibility. For these reasons and others, it is highly recommended that appropriate alt text be specified using the "alt" attribute. This message is displayed only once.
83:7 | Error | The attribute value "333" for the "width" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. width=333 height=255 id="_x0000_i1025" src=nomgrapt1.jpg></font></p>\
83:18 | Error | The attribute value "255" for the "height" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. width=333 height=255 id="_x0000_i1025" src=nomgrapt1.jpg></font></p>\
83:26 | Warning | An "id" attribute value should not begin with an underscore character, even though this may work in most browsers. Disable this message if you want to allow these values to begin with underscore characters. Disabling this message may be helpful for ASP.NET generated pages which often incorrectly start these values with underscores.
83:44 | Error | The attribute value "nomgrapt1.jpg" for the "src" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. width=333 height=255 id="_x0000_i1025" src=nomgrapt1.jpg></font></p>\
89 | Error | Terminating validation due to too many errors. Please correct the previous errors and recheck the document. HTML Validator is currently set to stop after 20 errors. </html>
| Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.
| Comment | You can disable all the error messages for improperly quoted attribute values by having HTML Validator ignore and disregard the quotation mark requirements for attribute values. This option is in CSE HTML Validator's Validator Engine Options. However, it is recommended that you leave these error messages enabled and that you properly enclose attribute values in quotation marks.
| Comment | You can use the Quick Quote Tool in the editor to quickly enclose all attribute values in quotation marks.
| Comment | Possibly misspelled words (159, 115 unique): abitacolo (1x), allungato (1x), altri (1x), ampia (1x), anche (1x), animali (1x), antichi (1x), argillosi (1x), bastoncello (1x), Cambriano (1x), Carbonifero (1x), che (1x), chitinoso (1x), ciascun (1x), ciascuna (1x), cioè (1x), colonie (1x), completamente (1x), conoscenza (1x), considerati (1x), cordati (1x), corrispondenza (1x), costituite (1x), costituiva (1x), costruiti (1x), dal (1x), definire (1x), degli (1x), della (1x), delle (1x), dentellato (1x), dentello (1x), detta (1x), detto (1x), distribuzione (1x), diversi (1x), ebbe (1x), esoscheletro (1x), essere (1x), estinsero (1x), evolutiva (1x), fondi (1x), fra (1x), generale (1x), grandissima (1x), guida (1x), idmap (1x), Idroteca (1x), intermedia (1x), invertebrati (1x). List limited to first 50 unique words. NOTE: Validation terminated so not all words were checked.
| Comment | You can change the maximum number of error messages to display before the validation is terminated. This option is in CSE HTML Validator's Validator Engine Options.
| Comment | XHTML document detected.
| Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration.
| Comment (Search Engine) | [113] Random Search Engine Tip #7 - Each page on a site should have its own unique title. Every title should contain appropriate keywords and search terms that are relevent to the page.
| Comment (Search Engine) | [8] <meta name="description" content="(actual description)" /> should be used in the "head" section to provide a brief description of what is contained on this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment (Search Engine) | [8] <meta name="keywords" content="(actual keyword list)" /> should be used in the "head" section to provide a list of keywords that are relevent to this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment | An ICRA RDF label was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. It is recommended that every page include an ICRA label. For more information, please visit http://www.icra.org/.
| Comment | [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | 3674 bytes; 2.6s@14.4Kbps, 1.3s@28.8, 0.7s@50, 0.6s@64, 0.3s@128, 0.1s@384, 0.1s@512, 0.0s@768, 0.0s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.02s, 21 errors, 8 warnings, 17 messages, 15 validator comments, 89 lines, 29 tags (20 closed), 4 document comments, 2 entities, 91 programs run.

[ Summary ] [ To the top ]

### http://www.apat.gov.it/Museo/trilobiti.html

Line:char | Type | Message Description
--- | --- | ---
| Message (Web Content Accessibility Guidelines 1.0) [ACCESSIBILITY] | [73] WCAG 1.0 accessibility checking is disabled.
| Message (Section 508 Accessibility Standards) [ACCESSIBILITY] | [73] Section 508 accessibility checking is disabled.
1:2 | Warning | [65] This document's DOCTYPE matches a recognized DOCTYPE but without a perfect case sensitivity match. It may not be valid. Note that DOCTYPEs are treated as being case sensitive. See the description of flag 65 in the documentation for more information and the list of recognized DOCTYPEs.
4:1 | Error | The "xmlns:w" attribute is not valid for the "html" element. Some valid attributes for this element are: "dir", "lang", "version", and "xmlns". xmlns:w="urn:schemas-microsoft-com:office:word"
8:18 | Error | The attribute value "Content-Type" for the "http-equiv" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
9:12 | Error | The attribute value "ProgId" for the "name" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=ProgId content=Word.Document>
9:27 | Error | The attribute value "Word.Document" for the "content" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=ProgId content=Word.Document>
10:12 | Error | The attribute value "Generator" for the "name" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=Generator content="Microsoft Word 9">
11:12 | Error | The attribute value "Originator" for the "name" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <meta name=Originator content="Microsoft Word 9">
12:11 | Error | The attribute value "File-List" for the "rel" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <link rel=File-List href="./trilobiti_new_file/filelist.xml">
13:11 | Error | The attribute value "Edit-Time-Data" for the "rel" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <link rel=Edit-Time-Data href="./trilobiti_new_file/editdata.mso">
22:2 | Message (Search Engine) | Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: <title>Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows</title>. AI Internet Solutions also recommends that the "title" tag be the first tag inside the "head" section.
22:8 | Message (Search Engine) | [8] This document's title contains only 2 words. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable.
28:2 | Warning | HTML 4.01 and XHTML require the "type" attribute for the "style" element to specify the style sheet language. For example, use type="text/css". Note that many browsers may work without this attribute but it is highly recommended that it be used.
29:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers.
61:15 | Error | The attribute value "white" for the "bgcolor" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <body bgcolor=white lang=IT style='tab-interval:35.4pt'>
61:26 | Error | The attribute value "IT" for the "lang" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <body bgcolor=white lang=IT style='tab-interval:35.4pt'>
61:7 | Message (Deprecated) | [9] The "background", "bgcolor", "text", "link", "vlink", and "alink" attributes for the "body" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of the "bgcolor" attribute, consider using the CSS property "background-color". Example: style="background-color: white".
61:29 | Message (General) [CSS] | The "style" attribute has been used but a default style sheet language has not been defined (note that HTML Validator would not see this declaration if it is sent as an HTTP header by a web server). HTML 4.01 and XHTML require this for correct documents. However, for all practical purposes, leaving it out is very unlikely to cause problems. If you still want to define a default style sheet language, then include this in the "head" section of your document to specify "text/css" as the default style sheet language: <meta http-equiv="Content-Style-Type" content="text/css" />. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. Because this issue is very unlikely to cause problems, consider ignoring or disabling this message. See http://www.w3.org/TR/html4/present/styles.html#default-style for more information.
61:29 | Message (CSS Tips) [CSS] | Use the inline "style" attribute sparingly. Using this attribute too often can prevent you from receiving many of the benefits of CSS like easier to maintain and less cluttered documents. Consider using a single CSS style sheet instead of relying too much on the "style" attribute. This message is displayed only once.
62:12 | Error | The attribute value "Section1" for the "class" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <div class=Section1> <b><font face="Verdana, Arial, Helvetica, sans-serif">TRILOBITI</font></b>
62:23 | Message (Good Style) | The "strong" element should be used instead of the "b" element when you want to denote strong emphasis. The "b" element should only be used when you want bold typeface but do not want strong emphasis. Many web authors use the "b" element when the "strong" element would be more appropriate.
62:26 | Message (Deprecated) | [9] The "font" element and all of its attributes are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the "color", "font", "font-family", "font-size", and other CSS font properties instead).
63:14 | Error | The attribute value "MsoNormal" for the "class" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <div class=MsoNormal align=center style='text-align:center'>
63:30 | Error | The attribute value "center" for the "align" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <div class=MsoNormal align=center style='text-align:center'>
63:24 | Message (Deprecated) | [9] The "align" attribute is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of align="center", consider using the CSS "text-align: center" instead.
64:14 | Error | The attribute value "2" for the "size" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <hr size=2 width="100%" align=center>
64:35 | Error | The attribute value "center" for the "align" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <hr size=2 width="100%" align=center>
64:9 | Message (Deprecated) | [9] The "align", "noshade", "size", and "width" attributes for the "hr" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets. Consider using the "width" CSS property in place of the "width" attribute.
87:40 | Message (Good Style) | The "em" element (for emphasized text) or the "cite" element (for citations) may be more appropriate than the "i" element. Use the "i" element only if text is in italics by convention. Many web authors use the "i" element when the "em" element would be more appropriate.
92:4 | Message (General Compatibility) | [5] The "table" element is an official HTML 4.01 and XHTML element but may not be supported by older or nongraphical browsers. Furthermore, nongraphical browsers that do support tables may not support them the way that you expect. However, most browsers used today should support this element.
94:11 | Message (Deprecated) | [9] The "height" and "width" attributes for the "td" and "th" elements are deprecated in HTML 4.01 and XHTML in favor of using style sheets.
95:28 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "img" element. The "alt" attribute is critical for accessibility. It lets authors specify equivalent text to serve as content when the image cannot be seen or displayed. Use alt="" when alternate text is not appropriate, such as when images are intended to format a page (such as spacer images).
95:38 | Error | The attribute value "339" for the "width" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <p align="center"><img width=339 height=268 id="_x0000_i1026" src=glabella1.jpg border=2></p>
95:49 | Error | The attribute value "268" for the "height" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <p align="center"><img width=339 height=268 id="_x0000_i1026" src=glabella1.jpg border=2></p>
95:57 | Warning | An "id" attribute value should not begin with an underscore character, even though this may work in most browsers. Disable this message if you want to allow these values to begin with underscore characters. Disabling this message may be helpful for ASP.NET generated pages which often incorrectly start these values with underscores.
95:75 | Error | The attribute value "glabella1.jpg" for the "src" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <p align="center"><img width=339 height=268 id="_x0000_i1026" src=glabella1.jpg border=2></p>
95:96 | Error | The attribute value "2" for the "border" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <p align="center"><img width=339 height=268 id="_x0000_i1026" src=glabella1.jpg border=2></p>
95:28 | Message (Search Engine) | [8] Alt text is often used by search engines. Use this to your advantage (but do it appropriately). Furthermore, alt text is critical for accessibility. For these reasons and others, it is highly recommended that appropriate alt text be specified using the "alt" attribute. This message is displayed only once.
101:28 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "img" element. The "alt" attribute is critical for accessibility. It lets authors specify equivalent text to serve as content when the image cannot be seen or displayed. Use alt="" when alternate text is not appropriate, such as when images are intended to format a page (such as spacer images).
101:38 | Error | The attribute value "371" for the "width" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. <p align="center"><img width=371 height=264 id="_x0000_i1027" src=torax1.jpg border=2></p>
101:57 | Warning | An "id" attribute value should not begin with an underscore character, even though this may work in most browsers. Disable this message if you want to allow these values to begin with underscore characters. Disabling this message may be helpful for ASP.NET generated pages which often incorrectly start these values with underscores.
101 | Error | Terminating validation due to too many errors. Please correct the previous errors and recheck the document. HTML Validator is currently set to stop after 20 errors. <p align="center"><img width=371 height=264 id="_x0000_i1027" src=torax1.jpg border=2></p>
| Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.
| Comment | You can disable all the error messages for improperly quoted attribute values by having HTML Validator ignore and disregard the quotation mark requirements for attribute values. This option is in CSE HTML Validator's Validator Engine Options. However, it is recommended that you leave these error messages enabled and that you properly enclose attribute values in quotation marks.
| Comment | You can use the Quick Quote Tool in the editor to quickly enclose all attribute values in quotation marks.
| Comment | Possibly misspelled words (197, 135 unique): adattati (1x), ambientali (1x), ambienti (1x), anni (1x), anteriore (1x), appendici (1x), appiattito (1x), assenti (1x), bentonici (1x), bocca (1x), camminavano (1x), cefalopodi (1x), completamente (1x), comunque (1x), condizioni (1x), considerati (1x), contribuirono (1x), convesso (1x), corpo (1x), costituiti (1x), crescita (1x), cruziane (1x), dalle (1x), degli (1x), dei (1x), dell'esocheletro (1x), delle (1x), depositi (1x), deriva (1x), detti (1x), Devoniano (1x), dimensioni (1x), disposizione (1x), durante (1x), fa (1x), fango (1x), fini (1x), fondo (1x), fossero (1x), frequenti (1x), gruppo (1x), guida (1x), idmap (1x), impronte (1x), indicano (1x), L'accrescimento (1x), l'Era (1x), lasciate (1x), laterali (1x), Le (1x). List limited to first 50 unique words. NOTE: Validation terminated so not all words were checked.
| Comment | You can change the maximum number of error messages to display before the validation is terminated. This option is in CSE HTML Validator's Validator Engine Options.
| Comment | It is recommended that you update this HTML 4.0 document to HTML 4.01 or to XHTML. Updating to HTML 4.01 can easily be done in most cases by simply replacing the HTML 4.0 DOCTYPE with an HTML 4.01 DOCTYPE. Updating to XHTML usually requires much more work than simply changing the DOCTYPE. HTML 4.01 DOCTYPEs and other DOCTYPEs can be inserted from the Tag Inserter.
| Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration.
| Comment (Search Engine) | [113] Random Search Engine Tip #7 - Each page on a site should have its own unique title. Every title should contain appropriate keywords and search terms that are relevent to the page.
| Comment (Search Engine) | [8] <meta name="description" content="(actual description)" /> should be used in the "head" section to provide a brief description of what is contained on this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment (Search Engine) | [8] <meta name="keywords" content="(actual keyword list)" /> should be used in the "head" section to provide a list of keywords that are relevent to this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment | An ICRA RDF label was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. It is recommended that every page include an ICRA label. For more information, please visit http://www.icra.org/.
| Comment | [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | 4851 bytes; 3.4s@14.4Kbps, 1.7s@28.8, 1.0s@50, 0.8s@64, 0.4s@128, 0.1s@384, 0.1s@512, 0.1s@768, 0.0s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.02s, 21 errors, 7 warnings, 15 messages, 15 validator comments, 114 lines, 45 tags (28 closed), 4 document comments, 2 entities, 136 programs run.

[ Summary ] [ To the top ]

### http://www.apat.gov.it/museo

Line:char | Type | Message Description
--- | --- | ---
| Message (Web Content Accessibility Guidelines 1.0) [ACCESSIBILITY] | [73] WCAG 1.0 accessibility checking is disabled.
| Message (Section 508 Accessibility Standards) [ACCESSIBILITY] | [73] Section 508 accessibility checking is disabled.
15:2 | Message (Microsoft Internet Explorer) [CSS] | [600] The "behavior" CSS property is not an official CSS property and is only supported by Internet Explorer 5.0+. Firefox, Netscape, Opera, and most other browsers do not support this property.
17:10 | Message (Good Style) [CSS] | When a foreground color is defined, it is recommended that a background color also be defined (by using the "background" or "background-color" property). This helps to avoid conflict with user-defined style sheets and to improve accessibility.
18:10 | Message (Good Style) [CSS] | When a foreground color is defined, it is recommended that a background color also be defined (by using the "background" or "background-color" property). This helps to avoid conflict with user-defined style sheets and to improve accessibility.
21:2 | Message (Search Engine) | Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: <title>Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows</title>. AI Internet Solutions also recommends that the "title" tag be the first tag inside the "head" section.
35:16 | Message (General Compatibility) | [5] PNG images are generally well supported in today's browsers EXCEPT for Microsoft Internet Explorer 6.0 and below. IE 6.0 will not render PNG images correctly in certain cases. Because of the popularity of Internet Explorer, you may want to consider using GIF or JPG images instead, especially when using the transparency features of PNG which IE 6.0 does not support well. Fortunately PNG support has been improved in IE 7.0. This message is displayed only once. There may be other PNG images specified in this document.
74:35 | Message (Tips) | [6] Email spam is a huge problem nowadays. Be aware that mailto email addresses are easily harvested for spam lists by automated programs. Consider alternate, but less user-friendly, ways of distributing email addresses if spam is a concern.
81:61 | Error | The "summary" attribute has an invalid attribute value "". Try using one of the following values: an alphanumeric string or a string. <table border="0" cellspacing="0" cellpadding="0" summary="" class="TabellaCentrale">
81:4 | Message (Good Style) | Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute.
81:4 | Message (General Compatibility) | [5] The "table" element is an official HTML 4.01 and XHTML element but may not be supported by older or nongraphical browsers. Furthermore, nongraphical browsers that do support tables may not support them the way that you expect. However, most browsers used today should support this element.
126:45 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 126. These codepoints are commonly found in Windows character sets like Windows-1252 but may not work for everyone, especially those not using Windows. Consider using "&#8217;" instead of this character.
126:18 | Message (Deprecated) | [9] The "align" attribute is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of align="justify", consider using the CSS "text-align: justify" instead.
127:206 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 127. These codepoints are commonly found in Windows character sets like Windows-1252 but may not work for everyone, especially those not using Windows. Consider using "&#8217;" instead of this character.
148:16 | Message | [41] The "div" tag has no attributes. Attributes are normally used with the "div" element to provide functionality.
152:16 | Message | The "p" element is empty. Consider removing this element if it is not needed. If you are wanting to add additional margin space between elements, consider using the "margin" CSS properties like "margin", "margin-top", and "margin-bottom" instead. Paragraph elements should be used to denote paragraphs and not for presentational formatting.
170:20 | Message (Deprecated) | [9] The "font" element and all of its attributes are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the "color", "font", "font-family", "font-size", and other CSS font properties instead).
176:14 | Message | [41] The "div" tag has no attributes. Attributes are normally used with the "div" element to provide functionality.
181:16 | Message | The "p" element is empty. Consider removing this element if it is not needed. If you are wanting to add additional margin space between elements, consider using the "margin" CSS properties like "margin", "margin-top", and "margin-bottom" instead. Paragraph elements should be used to denote paragraphs and not for presentational formatting.
204:14 | Message | [41] The "div" tag has no attributes. Attributes are normally used with the "div" element to provide functionality.
208:16 | Message | The "p" element is empty. Consider removing this element if it is not needed. If you are wanting to add additional margin space between elements, consider using the "margin" CSS properties like "margin", "margin-top", and "margin-bottom" instead. Paragraph elements should be used to denote paragraphs and not for presentational formatting.
231:10 | Message | The "p" element is empty. Consider removing this element if it is not needed. If you are wanting to add additional margin space between elements, consider using the "margin" CSS properties like "margin", "margin-top", and "margin-bottom" instead. Paragraph elements should be used to denote paragraphs and not for presentational formatting.
250:4 | Message | The "p" element is empty. Consider removing this element if it is not needed. If you are wanting to add additional margin space between elements, consider using the "margin" CSS properties like "margin", "margin-top", and "margin-bottom" instead. Paragraph elements should be used to denote paragraphs and not for presentational formatting.
| Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.
| Comment | You have one or more internal links linking to an ID link destination. Browser support for this is currently very poor. Consider using something like <a name="Contenuti"> ... </a> or <a name="Contenuti" id="Contenuti"> ... </a> instead.
| Comment | You may want to turn off 128-159 character checking if you're sure that these characters will be interpreted and displayed properly by the visiting user agents. This option is in CSE HTML Validator's Validator Engine Options.
| Comment | Possibly misspelled words (581, 280 unique): accesso (1x), acquisire (1x), aderire (1x), agli (1x), all'interno (1x), alla (1x), alle (1x), appartengono (1x), arco (1x), Aristotelem (1x), attesa (1x), Attivit (1x), attività (1x), attualmente (1x), aut (1x), Benvenuto (1x), c'è (1x), Calendario (1x), campioni (1x), canale (1x), caratterizzato (1x), Carta (1x), censimento (1x), cioè (1x), classi (1x), coinvolgimento (1x), Collezione (1x), Colonna (1x), commento (1x), complesso (1x), completa (1x), considerevole (1x), Consulta (1x), Contatti (1x), contenuti (1x), contestuali (1x), coprono (1x), corpo (1x), cospicuo (1x), costituito (1x), costruita (1x), costruito (1x), creazione (1x), cui (1x), custodisce (1x), d’arte (1x), d’Italia (1x), d'Italia (1x), dal (1x), decorativi (1x). List limited to first 50 unique words.
| Comment | HTML 4.01 Transitional document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #7 - Each page on a site should have its own unique title. Every title should contain appropriate keywords and search terms that are relevent to the page.
| Comment (Search Engine) | [8] <meta name="description" content="(actual description)"> should be used in the "head" section to provide a brief description of what is contained on this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment (Search Engine) | [8] <meta name="keywords" content="(actual keyword list)"> should be used in the "head" section to provide a list of keywords that are relevent to this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment | An ICRA RDF label was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. It is recommended that every page include an ICRA label. For more information, please visit http://www.icra.org/.
| Comment | [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | 12625 bytes; 8.8s@14.4Kbps, 4.4s@28.8, 2.5s@50, 2.0s@64, 1.0s@128, 0.3s@384, 0.2s@512, 0.2s@768, 0.1s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.06s, 1 error, 2 warnings, 20 messages, 13 validator comments, 260 lines, 133 tags (121 closed), 64 document comments, 12 entities, 342 programs run.

[ Summary ] [ To the top ]

### http://www.apat.gov.it/site/EN-GB/

Line:char | Type | Message Description
--- | --- | ---
| Message (Web Content Accessibility Guidelines 1.0) [ACCESSIBILITY] | [73] WCAG 1.0 accessibility checking is disabled.
| Message (Section 508 Accessibility Standards) [ACCESSIBILITY] | [73] Section 508 accessibility checking is disabled.
5:2 | Message (Search Engine) | Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: <title>Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows</title>. AI Internet Solutions also recommends that the "title" tag be the first tag inside the "head" section.
5:8 | Message (Search Engine) | [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable.
49:2 | Message (General Compatibility) | [5] The "table" element is an official HTML 4.01 and XHTML element but may not be supported by older or nongraphical browsers. Furthermore, nongraphical browsers that do support tables may not support them the way that you expect. However, most browsers used today should support this element.
52:35 | Message (General Compatibility) | [5] PNG images are generally well supported in today's browsers EXCEPT for Microsoft Internet Explorer 6.0 and below. IE 6.0 will not render PNG images correctly in certain cases. Because of the popularity of Internet Explorer, you may want to consider using GIF or JPG images instead, especially when using the transparency features of PNG which IE 6.0 does not support well. Fortunately PNG support has been improved in IE 7.0. This message is displayed only once. There may be other PNG images specified in this document.
114:3 | Message (Good Style) | Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute.
116:8 | Message (Deprecated) | [9] The "height" and "width" attributes for the "td" and "th" elements are deprecated in HTML 4.01 and XHTML in favor of using style sheets.
126:43 | Warning | An "href", "id", or "name" attribute should normally be used with the "a" element. If one of these attributes are being set with a script, then consider the accessibility issues of requiring scripting. Disable this message if you do not want to check for this.
148:43 | Warning | An "href", "id", or "name" attribute should normally be used with the "a" element. If one of these attributes are being set with a script, then consider the accessibility issues of requiring scripting. Disable this message if you do not want to check for this.
173:43 | Warning | An "href", "id", or "name" attribute should normally be used with the "a" element. If one of these attributes are being set with a script, then consider the accessibility issues of requiring scripting. Disable this message if you do not want to check for this.
188:43 | Warning | An "href", "id", or "name" attribute should normally be used with the "a" element. If one of these attributes are being set with a script, then consider the accessibility issues of requiring scripting. Disable this message if you do not want to check for this.
203:43 | Warning | An "href", "id", or "name" attribute should normally be used with the "a" element. If one of these attributes are being set with a script, then consider the accessibility issues of requiring scripting. Disable this message if you do not want to check for this.
224:2 | Warning | The "h2" header element contains no text. Header elements are important and should contain appropriate header text.
224:16 | Warning | [56] The "P" tag is contained in a "p" tag that was opened in line 224. This is against the HTML specification and may cause problems with some browsers.
228:386 | Error | [47] The "ul" element must directly contain at least one "li" element. <P>APAT is gathering adhesions to participate on voluntary base to the jobs and spontaneous proposals of activity and events on the topic. The firms wanting to promote their image through the logo of the Year, can write to the address&nbsp; <A href="mailto:IYPE_Italia@apat.it">IYPE_Italia@apat.it</A> <BR><BR></P></p><div class="hrSalta"><hr /></div><div class="Continua PaddingTop"><ul></ul></div><div class="hrSalta"><hr /></div>
228:251 | Message (Tips) | [6] Email spam is a huge problem nowadays. Be aware that mailto email addresses are easily harvested for spam lists by automated programs. Consider alternate, but less user-friendly, ways of distributing email addresses if spam is a concern.
235:3 | Message (Good Style) | Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute.
242:184 | Warning | The "h3" header element contains no text. Header elements are important and should contain appropriate header text.
246:175 | Warning | The "h3" header element contains no text. Header elements are important and should contain appropriate header text.
259:2 | Warning | [56] The "DIV" tag is contained in a "p" tag that was opened in line 256. This is against the HTML specification and may cause problems with some browsers.
259:2 | Message | [41] The "DIV" tag has no attributes. Attributes are normally used with the "DIV" element to provide functionality.
300:3 | Error | Somewhere in this document there is a nonexistent internal link to "menu" created by using <a href="#menu"> ... </a>. This link should be removed or it should link to a location in the document that is specified by <a name="menu"> ... </a> or <element id="menu"...>. </body>
| Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.
| Comment | Possibly misspelled words (52, 40 unique): Agenzia (1x), alla (1x), Altre (1x), behavior.css (1x), BodyTotale (1x), Centro (1x), Cleanair (1x), Contiene (1x), dell'Ambiente (1x), di (1x), endif (1x), ESI (1x), FAO (1x), Giancarlo (1x), INQUA (1x), italian (1x), Italiana (1x), Italiano (1x), IYPE (1x), lte (1x), MenuLeft (1x), menuSx (1x), navigazione (1x), Primo (1x), primoPianoTabella (1x), Protezione (1x), PÃ³voa (1x), Sei (1x), Servizi (1x), SiteMap (1x), stylesheet (1x), Tecnici (1x), utilit (1x), Vai (1x), Varzim (1x), Versione (1x), Viglione (1x), BeginNoIndex (2x), EndNoIndex (2x), APAT (11x). Complete list.
| Comment | HTML 4.01 Transitional document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #7 - Each page on a site should have its own unique title. Every title should contain appropriate keywords and search terms that are relevent to the page.
| Comment (Search Engine) | [8] <meta name="description" content="(actual description)"> should be used in the "head" section to provide a brief description of what is contained on this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment (Search Engine) | [8] <meta name="keywords" content="(actual keyword list)"> should be used in the "head" section to provide a list of keywords that are relevent to this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment | An ICRA RDF label was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. It is recommended that every page include an ICRA label. For more information, please visit http://www.icra.org/.
| Comment | [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | 12676 bytes; 8.8s@14.4Kbps, 4.4s@28.8, 2.5s@50, 2.0s@64, 1.0s@128, 0.3s@384, 0.2s@512, 0.2s@768, 0.1s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.07s, 2 errors, 10 warnings, 11 messages, 11 validator comments, 301 lines, 225 tags (181 closed), 20 document comments, 19 entities, 537 programs run.

[ Summary ] [ To the top ]

### http://www.apat.gov.it/site/EN-GB/APAT/Other/

Line:char | Type | Message Description
--- | --- | ---
| Message (Web Content Accessibility Guidelines 1.0) [ACCESSIBILITY] | [73] WCAG 1.0 accessibility checking is disabled.
| Message (Section 508 Accessibility Standards) [ACCESSIBILITY] | [73] Section 508 accessibility checking is disabled.
5:2 | Message (Search Engine) | Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: <title>Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows</title>. AI Internet Solutions also recommends that the "title" tag be the first tag inside the "head" section.
5:8 | Message (Search Engine) | [8] This document's title contains only 2 words. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable.
49:2 | Message (General Compatibility) | [5] The "table" element is an official HTML 4.01 and XHTML element but may not be supported by older or nongraphical browsers. Furthermore, nongraphical browsers that do support tables may not support them the way that you expect. However, most browsers used today should support this element.
52:35 | Message (General Compatibility) | [5] PNG images are generally well supported in today's browsers EXCEPT for Microsoft Internet Explorer 6.0 and below. IE 6.0 will not render PNG images correctly in certain cases. Because of the popularity of Internet Explorer, you may want to consider using GIF or JPG images instead, especially when using the transparency features of PNG which IE 6.0 does not support well. Fortunately PNG support has been improved in IE 7.0. This message is displayed only once. There may be other PNG images specified in this document.
117:3 | Message (Good Style) | Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute.
119:8 | Message (Deprecated) | [9] The "height" and "width" attributes for the "td" and "th" elements are deprecated in HTML 4.01 and XHTML in favor of using style sheets.
129:43 | Warning | An "href", "id", or "name" attribute should normally be used with the "a" element. If one of these attributes are being set with a script, then consider the accessibility issues of requiring scripting. Disable this message if you do not want to check for this.
151:43 | Warning | An "href", "id", or "name" attribute should normally be used with the "a" element. If one of these attributes are being set with a script, then consider the accessibility issues of requiring scripting. Disable this message if you do not want to check for this.
176:43 | Warning | An "href", "id", or "name" attribute should normally be used with the "a" element. If one of these attributes are being set with a script, then consider the accessibility issues of requiring scripting. Disable this message if you do not want to check for this.
191:43 | Warning | An "href", "id", or "name" attribute should normally be used with the "a" element. If one of these attributes are being set with a script, then consider the accessibility issues of requiring scripting. Disable this message if you do not want to check for this.
206:43 | Warning | An "href", "id", or "name" attribute should normally be used with the "a" element. If one of these attributes are being set with a script, then consider the accessibility issues of requiring scripting. Disable this message if you do not want to check for this.
226:5 | Message (Good Style) | Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute.
229:56 | Warning | The "h1" header element contains no text. Header elements are important and should contain appropriate header text.
252:16 | Warning | [75] The "href" attribute specifies an internal link that may not be wanted. An internal link name should usually follow the # character, but it doesn't in this case. However, if the top of the current document is being referenced, then this message should be ignored because an internal link name is not needed.
252:22 | Warning | The "a" tag contains no link text. Though it is not technically required, it is recommended that all "a" elements contain appropriate link text or an appropriate element, like "img".
273:3 | Error | Somewhere in this document there is a nonexistent internal link to "menu" created by using <a href="#menu"> ... </a>. This link should be removed or it should link to a location in the document that is specified by <a name="menu"> ... </a> or <element id="menu"...>. </body>
| Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.
| Comment | Possibly misspelled words (38, 28 unique): Agenzia (1x), alla (1x), behavior.css (1x), BodyTotale (1x), centro (1x), contiene (1x), dell'Ambiente (1x), di (1x), endif (1x), italian (1x), Italiana (1x), Italiano (1x), lte (1x), MenuLeft (1x), menuSx (1x), navigazione (1x), Protezione (1x), Sei (1x), Servizi (1x), SiteMap (1x), stylesheet (1x), Tecnici (1x), utilit (1x), Vai (1x), Versione (1x), BeginNoIndex (3x), EndNoIndex (3x), APAT (7x). Complete list.
| Comment | HTML 4.01 Transitional document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #7 - Each page on a site should have its own unique title. Every title should contain appropriate keywords and search terms that are relevent to the page.
| Comment (Search Engine) | [8] <meta name="description" content="(actual description)"> should be used in the "head" section to provide a brief description of what is contained on this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment (Search Engine) | [8] <meta name="keywords" content="(actual keyword list)"> should be used in the "head" section to provide a list of keywords that are relevent to this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter.
| Comment | An ICRA RDF label was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. It is recommended that every page include an ICRA label. For more information, please visit http://www.icra.org/.
| Comment | [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
| Comment | 7966 bytes; 5.5s@14.4Kbps, 2.8s@28.8, 1.6s@50, 1.2s@64, 0.6s@128, 0.2s@384, 0.2s@512, 0.1s@768, 0.1s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.05s, 1 error, 8 warnings, 9 messages, 11 validator comments, 275 lines, 141 tags (126 closed), 17 document comments, 7 entities, 358 programs run.

[ Summary ] [ To the top ]

Multiple page report: Previous | Summary 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 | Next