# [707] 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/Monitoraggio/monitoraggio.asp (22), [and 20 warnings]
- http://www.apat.gov.it/Monitoraggio/quadro_normativo.asp (14), [and 20 warnings]
- http://www.apat.gov.it/museo/ (1), [and 2 warnings]
- http://www.apat.gov.it/museo/_Guida.htm (5), [and 0 warnings]
- http://www.apat.gov.it/museo/__Brochure.htm (3), [and 0 warnings]
- http://www.apat.gov.it/museo/__Filmato_museo.htm (1), [and 0 warnings]
- http://www.apat.gov.it/museo/__attesa_museo.htm (1), [and 0 warnings]
- http://www.apat.gov.it/museo/__museigeopaleo%20italiani.htm (3), [and 20 warnings]
- http://www.apat.gov.it/museo/__pubblicazioni.htm (3), [and 1 warning]
- http://www.apat.gov.it/museo/__stage.htm (19), [and 3 warnings]

### 2. Documents that have warnings

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

## Validation Reports

### http://www.apat.gov.it/Monitoraggio/monitoraggio.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.
3: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> ... </html> section is being validated.
4: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.
12: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.
16:3 | Warning | [32] This document should be given a title by using the "title" element in the document's "head" section. HTML 4.01 and XHTML require exactly one "title" element for each document.
18: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".
22: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.
22: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.
28: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.
31: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.
31: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).
34: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).
34: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.
41: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">
42:2 | Warning | [56] The "p" tag is contained in a "p" tag that was opened in line 40. This is against the HTML specification and may cause problems with some browsers.
44:50 | 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: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.
46: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.
47: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>
62: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".
66:2 | Error | The end tag for "body" (opened in line 41) should appear before the end tag for "p" (nesting error). </p>
76:28 | 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.
76:61 | 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.
76:61 | Error (General) [CSS] | The font family name "&quot" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
76:67 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
76:55 | Message (General) [CSS] | The following typeface may not be available on a significant number of browsers: "&quot". Also, check the spelling of the typeface name.
82:28 | 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.
82:61 | 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.
82:61 | Error (General) [CSS] | The font family name "&quot" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
82:67 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
86 | Error | This line contains part of a quoted string that spans more than one line (not recommended) or a quoted string (like an attribute value) that is missing the start or end quotation mark. Check this line for improperly quoted attribute values that may be missing a start or end quotation mark. As currently configured, HTML Validator requires that all quoted strings be contained on one line and have start and end quotation marks. Note that because of inconsistent handling by user agents, it is not recommended that attribute values contain line breaks. <p style="margin-top:5.0pt;margin-right:72.0pt;margin-bottom:5.0pt;margin-left:
90:28 | 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.
90:61 | 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.
90:61 | Error (General) [CSS] | The font family name "&quot" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
90:67 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
94:28 | 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.
94:61 | 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.
94:61 | Error (General) [CSS] | The font family name "&quot" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
94:67 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
97:28 | 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.
97:61 | 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.
97:61 | Error (General) [CSS] | The font family name "&quot" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
97:67 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
101:28 | 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.
101:61 | 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.
101:61 | Error (General) [CSS] | The font family name "&quot" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
101:67 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
105 | Error | This line contains part of a quoted string that spans more than one line (not recommended) or a quoted string (like an attribute value) that is missing the start or end quotation mark. Check this line for improperly quoted attribute values that may be missing a start or end quotation mark. As currently configured, HTML Validator requires that all quoted strings be contained on one line and have start and end quotation marks. Note that because of inconsistent handling by user agents, it is not recommended that attribute values contain line breaks. <p style="margin-top:5.0pt;margin-right:72.0pt;margin-bottom:5.0pt;margin-left:
109:28 | 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.
109:61 | 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.
109:67 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
113:67 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
118:67 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. <span style="font-family: Symbol">·<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
135:21 | Message (Deprecated) | [9] The "bgcolor" attribute for the "td" and "th" elements is 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: #CC9933".
141 | 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.
141 | 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.
| 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 | You can allow a quoted string to exist on more than one line by turning on the option to allow multi-line quotes. However, allowing multi-line quotes may make it more difficult to find problems caused by incorrect quoting. This option is in CSE HTML Validator's Validator Engine Options.
| 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 (178, 110 unique): adempimenti (1x), Agenzia (1x), aggiornamento (1x), alle (1x), analisi (1x), APAT (1x), Attività (1x), Autorità (1x), Bacino (1x), che (1x), cittadini (1x), comprende (1x), conformità (1x), ContentHead (1x), cui (1x), dai (1x), DecArea (1x), dell’APAT (1x), dello (1x), disponibili (1x), dissesto (1x), diversi (1x), ecc (1x), effettuati (1x), elaborazioni (1x), es (1x), eterogenee (1x), fornire (1x), informatizzata (1x), informazioni (1x), interessati (1x), Introduzione (1x), istituzioni (1x), l’aggiornamento (1x), metodologia (1x), MSTableType (1x), normativo (1x), operativa (1x), organizzare (1x), organizzati (1x), più (1x), possesso (1x), presso (1x), previsti (1x), progetti (1x), progettisti (1x), Proponenti (1x), protezione (1x), provenienti (1x), pubbliche (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 | 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 (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 | Although not normally necessary, consider including a "meta" tag similar to the following in the "head" section of this document: <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
| 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 | 7267 bytes; 5.0s@14.4Kbps, 2.5s@28.8, 1.5s@50, 1.1s@64, 0.6s@128, 0.2s@384, 0.1s@512, 0.1s@768, 0.0s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.03s, 22 errors, 20 warnings, 15 messages, 16 validator comments, 141 lines, 96 tags (89 closed), 5 document comments, 71 entities, 300 programs run.

[ Summary ] [ To the top ]

### http://www.apat.gov.it/Monitoraggio/quadro_normativo.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.
3: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> ... </html> section is being validated.
4: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.
12: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.
16:3 | Warning | [32] This document should be given a title by using the "title" element in the document's "head" section. HTML 4.01 and XHTML require exactly one "title" element for each document.
18: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".
22: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.
22: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.
28: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.
31: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.
31: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).
34: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).
34: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.
42: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">
43:2 | Warning | [56] The "p" tag is contained in a "p" tag that was opened in line 40. This is against the HTML specification and may cause problems with some browsers.
45:50 | 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.
45: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.
47: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.
48: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>
63: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".
67:2 | Error | The end tag for "body" (opened in line 42) should appear before the end tag for "p" (nesting error). </p>
80 | Error | This line contains part of a quoted string that spans more than one line (not recommended) or a quoted string (like an attribute value) that is missing the start or end quotation mark. Check this line for improperly quoted attribute values that may be missing a start or end quotation mark. As currently configured, HTML Validator requires that all quoted strings be contained on one line and have start and end quotation marks. Note that because of inconsistent handling by user agents, it is not recommended that attribute values contain line breaks. <p style="margin-top:6.0pt;margin-right:72.0pt;margin-bottom:0cm;margin-left:
81:8 | Warning (General) [CSS] | The "margin-bottom" property has already been defined in this style rule. A property should only be defined once per rule.
81:78 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 81. 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.
82:14 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 82. 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 "&#8220;" instead of this character.
82:16 | 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.
83:79 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 83. 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 "&#8221;" instead of this character.
85:3 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 85. 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.
92:28 | 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.
92:28 | Error (General) [CSS] | The font family name "&quot" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. -<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
92:34 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. -<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
92:22 | Message (General) [CSS] | The following typeface may not be available on a significant number of browsers: "&quot". Also, check the spelling of the typeface name.
94:7 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 94. 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.
97:28 | 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.
97:28 | Error (General) [CSS] | The font family name "&quot" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. -<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
97:34 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. -<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
101:28 | 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.
101:28 | Error (General) [CSS] | The font family name "&quot" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. -<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
101:34 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. -<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
105:28 | 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.
105:28 | Error (General) [CSS] | The font family name "&quot" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. -<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
105:34 | Error (Parsing) [CSS] | Bad style format, cannot find the colon separating the style property from its value. -<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
112:36 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 112. 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.
115:50 | 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.
115:50 | Error (General) [CSS] | The font family name "Times New Roman" must be enclosed in quotation marks (single or double) because the name contains spaces, special characters, or doesn't begin with an alphabetic character. <span style="font-size: 12.0pt; font-family: Times New Roman">
117:33 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 117. 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.
118:48 | Warning | At least one character (codepoint) between 128 and 159 (inclusive) was found on line 118. 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.
131:21 | Message (Deprecated) | [9] The "bgcolor" attribute for the "td" and "th" elements is 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: #CC9933".
137 | 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.
| 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 | You can allow a quoted string to exist on more than one line by turning on the option to allow multi-line quotes. However, allowing multi-line quotes may make it more difficult to find problems caused by incorrect quoting. This option is in CSE HTML Validator's Validator Engine Options.
| 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 (222, 140 unique): accelerare (1x), adempimenti (1x), adozione (1x), Agenzia (1x), all’interno (1x), alla (1x), APAT (1x), aree (1x), Assetto (1x), Attività (1x), Attuatori (1x), attuazione (1x), Autonome (1x), Autorità (1x), Banca (1x), brevi (1x), Campania (1x), che (1x), collegate (1x), collocano (1x), colpite (1x), complessivo (1x), conoscitivo (1x), consentisse (1x), ContentHead (1x), costituzione (1x), dalla (1x), Dati (1x), DecArea (1x), definiti (1x), definì (1x), dell’Ambiente (1x), dell’attuazione (1x), dell’impiego (1x), detto (1x), disastri (1x), elevato (1x), Enti (1x), erogati (1x), esso (1x), facilmente (1x), favore (1x), febbraio (1x), finanziamento (1x), fondi (1x), franosi (1x), giugno (1x), già (1x), gli (1x), grado (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 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 (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 | Although not normally necessary, consider including a "meta" tag similar to the following in the "head" section of this document: <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
| 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 | 5978 bytes; 4.2s@14.4Kbps, 2.1s@28.8, 1.2s@50, 0.9s@64, 0.5s@128, 0.2s@384, 0.1s@512, 0.1s@768, 0.0s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.03s, 14 errors, 20 warnings, 16 messages, 15 validator comments, 137 lines, 80 tags (73 closed), 5 document comments, 39 entities, 247 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 #6 - NEVER do anything for the purpose of trying to trick a search engine. Tricks can often be detected or be reported to the search engine by a competitor.
| 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.05s, 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/museo/_Guida.htm

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.
20: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.
24:2 | Error | The "div" tag must have an end tag (</div>) but the end tag was not found. <div class="width">
25:4 | Error | The "div" tag must have an end tag (</div>) but the end tag was not found. <div class="minwidth">
34: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.
73: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.
82: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">
82: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.
82: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:14 | Error | The "dt" tag must have an end tag (</dt>) but the end tag was not found. <dt class="primo"> <a href="index_collezioni.htm">Le collezioni</a> <br>
117:12 | Error | The end tag for "dt" (opened in line 94) should appear before the end tag for "dl" (nesting error). </dl></td>
120:36 | Message (Good Style) | It is usually best not to specify the actual index document name "index.htm". Consider using href="./" instead. Visit http://webtips.dan.info/subdir.html#LinkHome for more information about why this is recommended.
130: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.
130: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.
130:15 | Message (Deprecated) | [9] The "compact", "start", and "type" attributes for the "ol" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the "list-style-type" CSS property instead).
131:40 | Message (General) [CSS] | Found the Microsoft Office property "mso-list". HTML Validator ignores these proprietary properties that begin with "mso-". This message is displayed only once. There may be other proprietary properties.
131:64 | Message (General) [CSS] | Found the property "tab-stops". This is likely a Microsoft proprietary CSS property. HTML Validator ignores this property. This message is displayed only once. There may be other "tab-stops" proprietary properties.
132:20 | 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.
157: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.
158: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 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 (351, 195 unique): accedere (1x), agli (1x), all'interno (1x), alla (1x), altres (1x), attivi (1x), Attivit (1x), automatico (1x), barra (1x), Benvenuto (1x), bloccato (1x), Buona (1x), c'è (1x), Calendario (1x), canale (1x), cioè (1x), classi (1x), colorata (1x), colore (1x), commento (1x), comparire (1x), completa (1x), conferma (1x), conforme (1x), Consenti (1x), consentono (1x), consultazione (1x), contengono (1x), contenute (1x), corpo (1x), corretta (1x), correttamente (1x), costruita (1x), costruito (1x), cui (1x), dedicata (1x), dell'immagine (1x), dell'utente (1x), Denominazione (1x), destinazione (1x), destro (1x), devono (1x), difficolt (1x), dinamiche (1x), disattivare (1x), disattivazione (1x), domanda (1x), dovrà (1x), elementi (1x), eventi (1x). List limited to first 50 unique words.
| Comment | HTML 4.01 Transitional document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #6 - NEVER do anything for the purpose of trying to trick a search engine. Tricks can often be detected or be reported to the search engine by a competitor.
| 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 | 8116 bytes; 5.6s@14.4Kbps, 2.8s@28.8, 1.6s@50, 1.3s@64, 0.6s@128, 0.2s@384, 0.2s@512, 0.1s@768, 0.1s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.04s, 5 errors, 0 warnings, 18 messages, 13 validator comments, 163 lines, 102 tags (80 closed), 26 document comments, 30 entities, 265 programs run.

[ Summary ] [ To the top ]

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

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.
19:2 | 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.
24: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.
38: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.
77: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.
82: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">
82: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.
82: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:14 | Error | The "dt" tag must have an end tag (</dt>) but the end tag was not found. <dt class="primo"> <a href="index_collezioni.htm">Le collezioni</a> <br>
115:12 | Error | The end tag for "dt" (opened in line 94) should appear before the end tag for "dl" (nesting error). </dl>
119:36 | Message (Good Style) | It is usually best not to specify the actual index document name "index.htm". Consider using href="./" instead. Visit http://webtips.dan.info/subdir.html#LinkHome for more information about why this is recommended.
128:145 | 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.
133:16 | 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.
151: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 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 (330, 186 unique): agli (1x), alcune (1x), all'interno (1x), alle (1x), attenzione (1x), attivare (1x), Attivit (1x), ausilio (1x), Benvenuto (1x), buon (1x), c'è (1x), Calendario (1x), canale (1x), caricatore (1x), cartoncino (1x), centro (1x), chiusura (1x), cioè (1x), classi (1x), colori (1x), commenti (1x), commento (1x), completa (1x), consentono (1x), conservate (1x), Contatti (1x), contenente (1x), contengono (1x), contenuti (1x), contestuali (1x), contorno (1x), corpo (1x), corretta (1x), costruita (1x), costruito (1x), dedicata (1x), dell'immagine (1x), dell'utente (1x), delucidazioni (1x), Denominazione (1x), devono (1x), disponga (1x), Dopo (1x), dovrà (1x), durante (1x), elementi (1x), eseguito (1x), estrarre (1x), estremi (1x), eventi (1x). List limited to first 50 unique words.
| Comment | HTML 4.01 Transitional document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #6 - NEVER do anything for the purpose of trying to trick a search engine. Tricks can often be detected or be reported to the search engine by a competitor.
| 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 | 7524 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.04s, 3 errors, 0 warnings, 13 messages, 13 validator comments, 161 lines, 95 tags (82 closed), 25 document comments, 26 entities, 258 programs run.

[ Summary ] [ To the top ]

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

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.
18:2 | 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.
23: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.
37: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.
76: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.
118:36 | Message (Good Style) | It is usually best not to specify the actual index document name "index.htm". Consider using href="./" instead. Visit http://webtips.dan.info/subdir.html#LinkHome for more information about why this is recommended.
122:14 | 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.
137: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 | Possibly misspelled words (281, 155 unique): acquisizione (1x), alle (1x), attendere (1x), ATTENZIONE (1x), Attivit (1x), avviare (1x), Benvenuto (1x), Buona (1x), c'è (1x), Calendario (1x), canale (1x), cartella (1x), caso (1x), chiusura (1x), cioè (1x), classi (1x), commento (1x), completa (1x), consentono (1x), conservate (1x), Contatti (1x), contenente (1x), contengono (1x), contenuti (1x), contestuali (1x), corpo (1x), corretta (1x), costruita (1x), costruito (1x), creata (1x), cui (1x), dal (1x), dell'immagine (1x), dell'utente (1x), delle (1x), Denominazione (1x), devono (1x), dovrà (1x), effettuare (1x), elementi (1x), essere (1x), estrarre (1x), eventi (1x), evitano (1x), fai (1x), ferma (1x), filmati (1x), finestre (1x), fissi (1x), frutiger (1x). List limited to first 50 unique words.
| Comment | HTML 4.01 Transitional document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #6 - NEVER do anything for the purpose of trying to trick a search engine. Tricks can often be detected or be reported to the search engine by a competitor.
| 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 | 6659 bytes; 4.6s@14.4Kbps, 2.3s@28.8, 1.3s@50, 1.0s@64, 0.5s@128, 0.2s@384, 0.1s@512, 0.1s@768, 0.0s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.04s, 1 error, 0 warnings, 12 messages, 12 validator comments, 146 lines, 86 tags (77 closed), 24 document comments, 18 entities, 228 programs run.

[ Summary ] [ To the top ]

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

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:11 | 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.
20: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.
23:2 | 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.
28:2 | 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.
31:11 | 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. This is the last time that this message will be generated. There may be more places where a foreground color was defined without a background color.
34: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.
48: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.
87: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.
92: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">
92: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.
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.
132:36 | Message (Good Style) | It is usually best not to specify the actual index document name "index.htm". Consider using href="./" instead. Visit http://webtips.dan.info/subdir.html#LinkHome for more information about why this is recommended.
134:10 | 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.
138:16 | 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.
155:12 | 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.
174: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 | Possibly misspelled words (379, 220 unique): acquisire (1x), acquisite (1x), adottati (1x), ai (1x), all'avanguardia (1x), alla (1x), allestite (1x), ambienti (1x), angolazioni (1x), appositi (1x), approfondimenti (1x), attesa (1x), Benvenuto (1x), c'è (1x), Calendario (1x), canale (1x), caso (1x), cercate (1x), che (1x), chiusura (1x), ci (1x), cioè (1x), classi (1x), commento (1x), completa (1x), consentono (1x), consone (1x), consultare (1x), consultazione (1x), Contatti (1x), contenente (1x), contengono (1x), contenuti (1x), contestuali (1x), corpo (1x), costruita (1x), costruito (1x), cui (1x), d'Italia (1x), dagli (1x), dedicato (1x), delineati (1x), dell'ex (1x), dell'immagine (1x), dell'utente (1x), Denominazione (1x), descrizione (1x), devono (1x), diversi (1x), dovrà (1x). List limited to first 50 unique words.
| Comment | HTML 4.01 Transitional document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #6 - NEVER do anything for the purpose of trying to trick a search engine. Tricks can often be detected or be reported to the search engine by a competitor.
| 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 | 9218 bytes; 6.4s@14.4Kbps, 3.2s@28.8, 1.8s@50, 1.4s@64, 0.7s@128, 0.2s@384, 0.2s@512, 0.1s@768, 0.1s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.04s, 1 error, 0 warnings, 18 messages, 12 validator comments, 183 lines, 99 tags (80 closed), 25 document comments, 17 entities, 272 programs run.

[ Summary ] [ To the top ]

### http://www.apat.gov.it/museo/__museigeopaleo%20italiani.htm

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.
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.
78: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">
78: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.
78: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.
118:14 | Message (Good Style) | It is usually best not to specify the actual index document name "index.htm". Consider using href="./" instead. Visit http://webtips.dan.info/subdir.html#LinkHome for more information about why this is recommended.
123:16 | 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.
126:29 | 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.
144:69 | Warning | The "strong" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text.
144:77 | Warning | The "em" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text.
166:28 | 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).
169:23 | Message (Deprecated) | [9] The "compact" and "type" attributes for the "UL" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the "list-style-type" CSS property instead of the "type" attribute).
240:20 | 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.
240:20 | 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.
241:34 | 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.
260:34 | 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.
498:34 | 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.
659:34 | 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.
697:18 | 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.
705:42 | Message (Good Style) | It is usually best not to specify the actual index document name "index.html". Consider using href="http://www.naturmuseum.it/" instead. Visit http://webtips.dan.info/subdir.html#LinkHome for more information about why this is recommended.
728:46 | Warning | The "strong" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text.
728:54 | Warning | The "em" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text.
764:34 | 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.
826:34 | 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.
850:23 | 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.
1027:34 | 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.
1036:42 | Message (Good Style) | It is usually best not to specify the actual index document name "index.html". Consider using href="http://www3.unifi.it/msn/" instead. Visit http://webtips.dan.info/subdir.html#LinkHome for more information about why this is recommended. This is the last time that this message will be generated. There may be other links specifying the actual index document name.
1048:18 | 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.
1060:18 | 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.
1092:18 | 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.
1126:18 | 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.
1151:18 | 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.
1179:18 | 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.
1186 | Error | This line contains part of a quoted string that spans more than one line (not recommended) or a quoted string (like an attribute value) that is missing the start or end quotation mark. Check this line for improperly quoted attribute values that may be missing a start or end quotation mark. As currently configured, HTML Validator requires that all quoted strings be contained on one line and have start and end quotation marks. Note that because of inconsistent handling by user agents, it is not recommended that attribute values contain line breaks. <P CLASS=MsoNormal STYLE='margin-right:108.0pt;mso-margin-top-alt:auto;
1186:64 | Message (General) [CSS] | Found the Microsoft Office property "mso-margin-top-alt". HTML Validator ignores these proprietary properties that begin with "mso-". This message is displayed only once. There may be other proprietary properties.
1188:36 | 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.
1205:23 | 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.
1207:18 | 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.
1253:34 | 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.
1271:30 | Warning | The email address or addresses specified in the mailto link "mailto:info@lst-spoleto.it/inizio.html" did not pass a syntax check. Make sure that all email addresses specified are correct and contain valid top-level domains. Details: "info@lst-spoleto.it/inizio.html" contains one or more invalid characters
1282:34 | 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.
1282:193 | 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.
1311:34 | 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.
1372:34 | 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.
1396:18 | 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.
1430:18 | 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.
1569: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.
1577:3 | Error | Somewhere in this document there is a nonexistent internal link to "top" created by using <a href="#top"> ... </a>. This link should be removed or it should link to a location in the document that is specified by <a name="top"> ... </a> or <element id="top"...>. </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 allow a quoted string to exist on more than one line by turning on the option to allow multi-line quotes. However, allowing multi-line quotes may make it more difficult to find problems caused by incorrect quoting. 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 (2126, 786 unique): ACCADEMIA (1x), ADOLFO (1x), AGORDO (1x), AGOSTINO (1x), ALESSANDRIA (1x), ALESSANDRO (1x), ALFEO (1x), ALIGHIERI (1x), all'interno (1x), alle (1x), allestimento (1x), ALLUMIERE (1x), ALPINO (1x), AMICI (1x), ANGELONI (1x), ANTIQUARIUM (1x), AOSTA (1x), APOSTOLICA (1x), AQUILA (1x), ARCHEOLOGIA (1x), ARIELLI (1x), ARMA (1x), ASOLO (1x), ASS.TUR. (1x), ASTI (1x), ATANIA (1x), AURINA (1x), AURONZO (1x), AVENNA (1x), AVENTINO (1x), BAGNI (1x), BALDO (1x), BALDUZZI (1x), BASELICE (1x), Basilicata (1x), BASTIONE (1x), BATTISTA (1x), BELLONA (1x), BELLUNO (1x), BENEVENTO (1x), Benvenuto (1x), BERENGARIO (1x), BESOZZO (1x), BIAGI (1x), BIANDRONNO (1x), BOLCA (1x), BOMBA (1x), BORELLI (1x), BORMIO (1x), BOSCO (1x). List limited to first 50 unique words.
| Comment | HTML 4.01 Transitional document detected.
| Comment (Good Style) | This document is approximately 92779 bytes. Some people may consider this document to be too large. It is generally a good idea to limit the size of HTML and XHTML documents so that they do not contain too much information and also so that they load faster. This message displays for documents over 30,000 bytes.
| Comment (Search Engine) | [113] Random Search Engine Tip #19 - Don't cloak. Cloaking is delivering search engine optimized content to search engine spiders while delivering different content to actual human visitors. Many search engines can detect this type of spam and may even completely ban a site if cloaking is detected.
| 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 | 92779 bytes; 64.4s@14.4Kbps, 32.2s@28.8, 18.6s@50, 14.5s@64, 7.2s@128, 2.4s@384, 1.8s@512, 1.2s@768, 0.6s@1.5Mbps, 0.1s@10Mbps.
| Comment | 0.42s, 3 errors, 20 warnings, 30 messages, 14 validator comments, 1578 lines, 1766 tags (1073 closed), 23 document comments, 114 entities, 4330 programs run.

[ Summary ] [ To the top ]

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

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.
19:2 | 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.
23:2 | 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.
27: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.
41: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.
80: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.
85: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">
85: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.
85: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.
99:14 | Error | The "dt" tag must have an end tag (</dt>) but the end tag was not found. <dt class="primo"> <a href="index_collezioni.htm">Le collezioni</a> <br>
119:11 | Error | The end tag for "dt" (opened in line 99) should appear before the end tag for "dl" (nesting error). </dl>
124:36 | Message (Good Style) | It is usually best not to specify the actual index document name "index.htm". Consider using href="./" instead. Visit http://webtips.dan.info/subdir.html#LinkHome for more information about why this is recommended.
129:14 | 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.
134:19 | 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.
179:84 | Warning | The "strong" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text.
189: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 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 (457, 254 unique): alcuni (1x), all'Ufficio (1x), alpi (1x), Amministrazioni (1x), appendice (1x), Aree (1x), articoli (1x), articolo (1x), attori (1x), Benvenuto (1x), Branchiopodi (1x), c'è (1x), calcaree (1x), Calendario (1x), canale (1x), carattere (1x), caso (1x), catalogazione (1x), Cenni (1x), Centri (1x), chiusura (1x), CII (1x), cioè (1x), CIV (1x), classi (1x), colori (1x), commento (1x), compilazione (1x), compito (1x), completa (1x), concentrando (1x), connettiva (1x), consentono (1x), conservata (1x), Contatti (1x), contenente (1x), contengono (1x), contenuti (1x), contestuali (1x), contributori (1x), cooperazione (1x), costituita (1x), costruita (1x), costruito (1x), critica (1x), cui (1x), culturale (1x), dell'immagine (1x), dell'utente (1x), Denominazione (1x). List limited to first 50 unique words.
| Comment | HTML 4.01 Transitional document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #19 - Don't cloak. Cloaking is delivering search engine optimized content to search engine spiders while delivering different content to actual human visitors. Many search engines can detect this type of spam and may even completely ban a site if cloaking is detected.
| 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 | 10087 bytes; 7.0s@14.4Kbps, 3.5s@28.8, 2.0s@50, 1.6s@64, 0.8s@128, 0.3s@384, 0.2s@512, 0.1s@768, 0.1s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.05s, 3 errors, 1 warning, 14 messages, 13 validator comments, 198 lines, 141 tags (114 closed), 25 document comments, 26 entities, 374 programs run.

[ Summary ] [ To the top ]

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

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.
20: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.
24:2 | Error | The "div" tag must have an end tag (</div>) but the end tag was not found. <div class="width">
25:4 | Error | The "div" tag must have an end tag (</div>) but the end tag was not found. <div class="minwidth">
26:6 | Error | The "div" tag must have an end tag (</div>) but the end tag was not found. <div class="container">
34: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.
73: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.
77: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">
77: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.
77: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.
84:252 | Error | The "dl" tag must have an end tag (</dl>) but the end tag was not found. <!-- il menu' di navigazione principale &egrave; costruito con una "definition list" in cui i primi livelli sono i <dt> ("definition title") ed i loro sttolivelli sono liste non ordinate all'interno del <dd> ("definition data") --> <dl>
89:14 | Error | The "dt" tag must have an end tag (</dt>) but the end tag was not found. <dt class="primo"> <a href="index_collezioni.htm">Le collezioni</a> <br>
90:16 | Error | The "p" element cannot be used here. It is contained in a "dl" tag that cannot contain it. This element may be contained in "body", "dd", "td", and "th". This element may not be contained in "dl" and "table". <p>&nbsp;</p>
107:4 | Error | The "div" element cannot be used here. It is contained in a "dl" tag that cannot contain it. This element may be contained in "body", "dd", "td", and "th". This element may not be contained in "dl" and "table". <div align="left"><strong><a href="index_eventi.htm" class="ultimo">Calendario eventi</a><span class="Section1"><FONT SIZE="2" FACE="Verdana, Arial, Helvetica, sans-serif"></strong><strong><FONT SIZE="2" FACE="Verdana, Arial, Helvetica, sans-serif"></FONT></strong></div>
107:93 | Error | The "span" tag must have an end tag (</span>) but the end tag was not found. <div align="left"><strong><a href="index_eventi.htm" class="ultimo">Calendario eventi</a><span class="Section1"><FONT SIZE="2" FACE="Verdana, Arial, Helvetica, sans-serif"></strong><strong><FONT SIZE="2" FACE="Verdana, Arial, Helvetica, sans-serif"></FONT></strong></div>
107:116 | 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.
107:116 | Error | The "FONT" tag must have an end tag (</FONT>) but the end tag was not found. <div align="left"><strong><a href="index_eventi.htm" class="ultimo">Calendario eventi</a><span class="Section1"><FONT SIZE="2" FACE="Verdana, Arial, Helvetica, sans-serif"></strong><strong><FONT SIZE="2" FACE="Verdana, Arial, Helvetica, sans-serif"></FONT></strong></div>
107:176 | Error | The end tag for "FONT" (opened in line 107) should appear before the end tag for "strong" (nesting error). <div align="left"><strong><a href="index_eventi.htm" class="ultimo">Calendario eventi</a><span class="Section1"><FONT SIZE="2" FACE="Verdana, Arial, Helvetica, sans-serif"></strong><strong><FONT SIZE="2" FACE="Verdana, Arial, Helvetica, sans-serif"></FONT></strong></div>
107:185 | Warning | The "strong" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text.
107:193 | 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.
107:116 | 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).
111:12 | Error | The "p" element cannot be used here. It is contained in a "dl" tag that cannot contain it. This element may be contained in "body", "dd", "td", and "th". This element may not be contained in "dl" and "table". <p class="primo">&nbsp;</p></td>
115:58 | Message (Good Style) | It is usually best not to specify the actual index document name "index.htm". Consider using href="./" instead. Visit http://webtips.dan.info/subdir.html#LinkHome for more information about why this is recommended.
117:13 | 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.
119:348 | Error | Comments must begin with '<!--' and end with '-->'. In quest&rsquo;area &egrave; possibile consultare gli abstract delle tesi di stage, master e tirocini sviluppate, nell&rsquo;ambito delle sessioni organizzate dal Servizio Educazione e Formazione Ambientale, su specifiche tematiche inerenti le attivit&agrave; espletate dal Servizio Attivit&agrave; Museali dell&rsquo;Agenzia.<![if !supportEmptyParas]>
121:14 | Error | Comments must begin with '<!--' and end with '-->'. <![endif]>
123:555 | Error | Comments must begin with '<!--' and end with '-->'. <p align="justify" class=MsoNormal>Gli argomenti spaziano dallo studio e approfondimento delle collezioni museali (litomineralogiche e paleontologiche) alla ricerca sulle radici e sull'evoluzione del museo nel tempo ('800 - '900), dalle analisi delle strategie di promozione dei servizi museali, al repertorio dei musei in situ ed ex situ in Italia, all'uso di strumenti innovativi per la fruizione delle conoscenze sulla geoconservazione (attraverso un GEODATABASE), alle metodologie di catalogazione per la conservazione dei reperti museali.<![if !supportEmptyParas]>
125:14 | Error | Comments must begin with '<!--' and end with '-->'. <![endif]>
128:41 | 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.
130:19 | 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.
136:19 | Message (Tips) | [6] Using the "nowrap" attribute can create extremely wide cells and can produce unusual results. It can also cause a page to have to be horizontally scrolled. Be careful when using this attribute.
136:19 | Message (Deprecated) | [9] The "nowrap" attribute for the "td" and "th" elements is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Consider using the CSS "white-space: nowrap" instead of the "nowrap" attribute. Note, however, there are issues with the "white-space" property and using the deprecated "nowrap" attribute probably works best.
185:2 | Error | The "div" element cannot be used here. It is contained in a "dl" tag that cannot contain it. This element may be contained in "body", "dd", "td", and "th". This element may not be contained in "dl" and "table". <div class="Footer">
186:4 | Error | The "p" element cannot be used here. It is contained in a "dl" tag that cannot contain it. This element may be contained in "body", "dd", "td", and "th". This element may not be contained in "dl" and "table". <p class="FasciaFooter"></p>
186: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.
187:4 | Error | The "p" element cannot be used here. It is contained in a "dl" tag that cannot contain it. This element may be contained in "body", "dd", "td", and "th". This element may not be contained in "dl" and "table". <p>&nbsp;</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 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 | Comments should be in the '<!-- (comment here) -->' format. However, most browsers will accept '<! ... >' as a comment. If you do not want to use only '<!-- ... -->' comments, then you should turn off strict comments. 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 (453, 233 unique): Agenzia (1x), Alessandro (1x), all'interno (1x), all'uso (1x), ambito (1x), analisi (1x), approfondimento (1x), argomenti (1x), Ausonio (1x), Autore (1x), Benvenuto (1x), c'è (1x), canale (1x), caso (1x), catalogo (1x), Cecili (1x), Cesare (1x), Cesaro (1x), cioè (1x), classi (1x), commento (1x), completa (1x), completo (1x), conoscenza (1x), consentono (1x), consultare (1x), Contatti (1x), contenente (1x), contengono (1x), contenuti (1x), contestuali (1x), contributo (1x), Coreno (1x), corpo (1x), costruita (1x), costruito (1x), Cottanello (1x), creazione (1x), cui (1x), cultura (1x), cura (1x), dalla (1x), dalle (1x), dallo (1x), Daniela (1x), dell'immagine (1x), dell'utente (1x), Denominazione (1x), devono (1x), dintorni (1x). List limited to first 50 unique words.
| Comment | HTML 4.01 Transitional document detected.
| Comment (Search Engine) | [113] Random Search Engine Tip #19 - Don't cloak. Cloaking is delivering search engine optimized content to search engine spiders while delivering different content to actual human visitors. Many search engines can detect this type of spam and may even completely ban a site if cloaking is detected.
| 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 | 10579 bytes; 7.3s@14.4Kbps, 3.7s@28.8, 2.1s@50, 1.7s@64, 0.8s@128, 0.3s@384, 0.2s@512, 0.1s@768, 0.1s@1.5Mbps, 0.0s@10Mbps.
| Comment | 0.05s, 19 errors, 3 warnings, 17 messages, 14 validator comments, 190 lines, 168 tags (142 closed), 28 document comments, 35 entities, 377 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