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 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
Line:char | Type | Message Description |
---|---|---|
Message (Web Content Accessibility Guidelines 1.0) [ACCESSIBILITY] | [73] WCAG 1.0 accessibility checking is disabled. | |
Message (Section 508 Accessibility Standards) [ACCESSIBILITY] | [73] Section 508 accessibility checking is disabled. | |
5:2 | Message (Search Engine) | Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: <title>Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows</title>. AI Internet Solutions also recommends that the "title" tag be the first tag inside the "head" section. |
5:8 | Message (Search Engine) | [8] This document's title contains only 2 words. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable. |
8:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers. |
11:3 | 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. |
22:4 | 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. |
23:2 | Message | [41] The "div" tag has no attributes. Attributes are normally used with the "div" element to provide functionality. |
24:2 | Message | [41] The "div" tag has no attributes. Attributes are normally used with the "div" element to provide functionality. |
25:2 | Message | [41] The "div" tag has no attributes. Attributes are normally used with the "div" element to provide functionality. |
26:2 | Message | [41] The "div" tag has no attributes. Attributes are normally used with the "div" element to provide functionality. |
30:2 | Message | [41] The "div" tag has no attributes. Attributes are normally used with the "div" element to provide functionality. |
30:113 | 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. |
31:22 | 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). |
31:22 | Message (Good Style) | [7] The "height" and "width" attributes should be used with the "img" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. |
31:22 | 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. |
33:2 | Error | This table doesn't appear to have the same number of cells in each of its 2 rows. Number of cells in each row, starting with the first row: 1, 2. Note that for the purposes of this message, a table cell with a "colspan" or "rowspan" value greater than 1 is considered to be multiple cells. <table border="0"> |
33:2 | 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. |
33: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. |
35:6 | Error | The "th" tag must have an end tag (</th>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <th rowspan="2" scope="col"><table border="2" align="center" bordercolor="#FFCC66"> |
35:35 | 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. |
35:52 | 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. |
35:67 | Message (Microsoft Internet Explorer) | [1] The "bordercolor", "bordercolordark", and "bordercolorlight" attributes for the "table" element are not HTML or XHTML attributes and are currently only supported by Internet Explorer. For instance, Netscape 4.0 does not support these attributes. You've used at least one of these attributes in this "table" tag. |
38:13 | Error | The attribute "w" does not have a value. All attributes must have a value. This is required for XHTML/XML documents or if the option to require attribute values is enabled. <th w scope="col"><div align="center"> Number of earthquakes </div></th> |
38:13 | Error | The "w" attribute is not valid for the "th" element. Some valid attributes for this element are: "abbr", "align", "axes", "axis", "background", "bgcolor", "bordercolor", "bordercolordark", "bordercolorlight", "char", "charoff", "class", "colspan", "contenteditable", "dir", "gradangle", "gradcolor", "headers", "height", "hidefocus", "id", "lang", "language", "nowrap", "onactivate", "onbeforecopy", "onbeforecut", "onbeforepaste", "onclick", "oncontextmenu", "oncopy", "oncut", "ondblclick", "ondeactivate", "ondrag", "ondragend", "ondragenter", "ondragleave", "ondragover", "ondragstart", "ondrop", "onfilterchange", "onfocusin", "onfocusout", "onhelp", "onkeydown", "onkeypress", "onkeyup", "onmousedown", "onmouseenter", "onmouseleave", "onmousemove", "onmouseout", "onmouseover", "onmouseup", "onmousewheel", "onmove", "onmoveend", "onmovestart", "onpaste", "onpropertychange", "onselectstart", "rowspan", "scope", "style", "title", "transparency", "unselectable", "valign", "width", "xml:lang", and "xml:space". <th w scope="col"><div align="center"> Number of earthquakes </div></th> |
101:6 | Error | The "th" element cannot be used here. It is nested in another "th" tag and cannot be nested. Has the previous "th" element been ended? This element may be contained in "tr". This element may not be contained in "td" and "th". <th scope="col"><div align="left"><img src="GIS/last_world.jpg" border="0" usemap="#Map" /> |
101:41 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "img" element. The "alt" attribute is critical for accessibility. It lets authors specify equivalent text to serve as content when the image cannot be seen or displayed. Use alt="" when alternate text is not appropriate, such as when images are intended to format a page (such as spacer images). |
101:41 | Message (Good Style) | [7] The "height" and "width" attributes should be used with the "img" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. |
103:12 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
104:12 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
105:12 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
106:12 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
107:12 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
108:12 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
109:12 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
110:10 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
111:10 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
112:10 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
115:24 | 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). |
116:24 | 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). |
129:4 | Error | The end tag for "th" (opened in line 35) should appear before the end tag for "tr" (nesting error). </tr> |
Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options. | |
Comment | You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options. | |
Comment | Possibly misspelled words (8, 8 unique): Chiara (1x), coseismic (1x), EEE (1x), EEEs (1x), GIS (1x), Giulianelli (1x), INQUA (1x), Spernanzoni (1x). Complete list. | |
Comment | XHTML 1.0 Transitional document detected. | |
Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration. | |
Comment (Search Engine) | [113] Random Search Engine Tip #16 - Don't use "&id=" as a parameter in URLs as some search engines like Google won't include these URLs in their listings. | |
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 | 5872 bytes; 4.1s@14.4Kbps, 2.0s@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.04s, 6 errors, 15 warnings, 20 messages, 13 validator comments, 145 lines, 140 tags (123 closed), 0 document comments, 52 entities, 406 programs run. |
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. | |
6: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. |
6:8 | Message (Search Engine) | [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable. |
9:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers. |
16:4 | 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. |
18:2 | 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. |
18: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. |
20:22 | 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. |
20:72 | Message (Microsoft Internet Explorer) | [1] The "bordercolor", "bordercolordark", and "bordercolorlight" attributes for the "table" element are not HTML or XHTML attributes and are currently only supported by Internet Explorer. For instance, Netscape 4.0 does not support these attributes. You've used at least one of these attributes in this "table" tag. |
22:13 | 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. |
24:13 | Message (Deprecated) | [9] The "bgcolor" attribute for the "th" and "th" elements is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Consider using the "background-color" CSS property instead of the "bgcolor" attribute. |
31:26 | Error | The "a" tag must have an end tag (</a>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <td height="44"><a target = "_self" href="earthquake.asp?eq=TU19990817 " > TU19990817*</td> |
31:52 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
31:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
31:97 | Error | The end tag for "a" (opened in line 31) should appear before the end tag for "td" (nesting error). <td height="44"><a target = "_self" href="earthquake.asp?eq=TU19990817 " > TU19990817*</td> |
32:14 | 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. |
32:14 | 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. |
48:9 | Error | The "a" element cannot be used here. It is nested in another "a" tag and cannot be nested. Has the previous "a" element been ended? This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "a", "button", and "table". <p><a href="javascript: history.go(-1)">BACK</a></p> |
128:21 | 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). |
128:21 | 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. |
205:2 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options. | |
Comment | You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options. | |
Comment | Possibly misspelled words (5, 5 unique): foreshock (1x), GR (1x), Marmara (1x), Spernanzoni (1x), yyyymmdd (1x). Complete list. | |
Comment | XHTML 1.0 Transitional document detected. | |
Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration. | |
Comment (Search Engine) | [113] Random Search Engine Tip #16 - Don't use "&id=" as a parameter in URLs as some search engines like Google won't include these URLs in their listings. | |
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 | 5274 bytes; 3.7s@14.4Kbps, 1.8s@28.8, 1.1s@50, 0.8s@64, 0.4s@128, 0.1s@384, 0.1s@512, 0.1s@768, 0.0s@1.5Mbps, 0.0s@10Mbps. | |
Comment | 0.04s, 3 errors, 5 warnings, 14 messages, 13 validator comments, 207 lines, 205 tags (195 closed), 0 document comments, 153 entities, 592 programs run. |
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. | |
6: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. |
6:8 | Message (Search Engine) | [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable. |
9:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers. |
17:4 | 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. |
22:2 | 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. |
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:8 | 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. |
24:9 | Message (Deprecated) | [9] The "height" and "width" attributes for the "td" and "th" elements are deprecated in HTML 4.01 and XHTML in favor of using style sheets. |
25:8 | 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. |
25:72 | Message (Microsoft Internet Explorer) | [1] The "bordercolor", "bordercolordark", and "bordercolorlight" attributes for the "table" element are not HTML or XHTML attributes and are currently only supported by Internet Explorer. For instance, Netscape 4.0 does not support these attributes. You've used at least one of these attributes in this "table" tag. |
29:17 | 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: #FFFF33". |
36:60 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
36:60 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
36:109 | Error | The end tag for "a" (opened in line 36) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=CO19700926m " > CO19700926m * </td> |
36:17 | 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. |
36:17 | 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. |
45:60 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
45:60 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
45:109 | Error | The end tag for "a" (opened in line 45) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=CO19791212m " > CO19791212m * </td> |
54:60 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
54:60 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
54:109 | Error | The end tag for "a" (opened in line 54) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=CO19830331m " > CO19830331m * </td> |
63:60 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
63:60 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
63:109 | Error | The end tag for "a" (opened in line 63) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=CO19921018m " > CO19921018m * </td> |
72:60 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
72:60 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
72:109 | Error | The end tag for "a" (opened in line 72) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=CO19930721m " > CO19930721m * </td> |
81:60 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
81:60 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
81:109 | Error | The end tag for "a" (opened in line 81) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=CO19940606m " > CO19940606m * </td> |
90:60 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
90:60 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
90:109 | Error | The end tag for "a" (opened in line 90) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=CO19950119m " > CO19950119m * </td> |
99:60 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
99:60 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
99:107 | Error | The end tag for "a" (opened in line 99) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=CO19950208 " > CO19950208 * </td> |
108:60 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
108:60 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
108:107 | Error | The end tag for "a" (opened in line 108) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=CO19990125 " > CO19990125 * </td> |
117:60 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
117 | 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. <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=CO20001108m " > CO20001108m * </td> |
Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options. | |
Comment | You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options. | |
Comment | Possibly misspelled words (39, 15 unique): Bahía (1x), Calima (1x), Cauca (1x), COLOMBIA (1x), EQs (1x), Murindó (1x), Popayán (1x), Páez (1x), Rondón (1x), Solano (1x), Tauramena (1x), Tumaco (1x), Enriquez (9x), Lalinde (9x), Pulido (9x). 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 | XHTML 1.0 Transitional document detected. | |
Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration. | |
Comment (Search Engine) | [113] Random Search Engine Tip #11 - Avoid using JavaScript to insert tags and content into web pages. Don't use JavaScript to link to other documents. Search Engines don't run JavaScript. It's also a bad idea because it should not be assumed that JavaScript is available (and turned on) in the user's browser. | |
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 | 8963 bytes; 6.2s@14.4Kbps, 3.1s@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, 10 errors, 20 warnings, 14 messages, 14 validator comments, 185 lines, 134 tags (114 closed), 0 document comments, 1 entity, 394 programs run. |
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. | |
6: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. |
6:8 | Message (Search Engine) | [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable. |
9:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers. |
16:4 | 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. |
18: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. |
20:10 | Message (Good Style) | Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute. |
23:13 | 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: #FFFF33". |
30:30 | Error | The "a" tag must have an end tag (</a>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=GR20030814m " > GR20030814m*</td> |
30:56 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
30:56 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
30:103 | Error | The end tag for "a" (opened in line 30) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=GR20030814m " > GR20030814m*</td> |
30:13 | 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. |
30:13 | 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. |
38:9 | Error | The "a" element cannot be used here. It is nested in another "a" tag and cannot be nested. Has the previous "a" element been ended? This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "a", "button", and "table". <p><a href="javascript: history.go(-1)"></a><strong>Earthquake Code</strong>: it is the primary key (univocal) for the table “Earthquake” It is composed by 11 digits:<br /> |
44:9 | Error | The "a" element cannot be used here. It is nested in another "a" tag and cannot be nested. Has the previous "a" element been ended? This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "a", "button", and "table". <p><a href="javascript: history.go(-1)">BACK </a> </p></td> |
45:10 | 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). |
45:10 | 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. |
Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options. | |
Comment | You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options. | |
Comment | Possibly misspelled words (9, 9 unique): Ath (1x), foreshock (1x), Ganas (1x), GR (1x), GREECE (1x), Lefkada (1x), Papathanassiou (1x), Pavlides (1x), yyyymmdd (1x). Complete list. | |
Comment | XHTML 1.0 Transitional document detected. | |
Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration. | |
Comment (Search Engine) | [113] Random Search Engine Tip #11 - Avoid using JavaScript to insert tags and content into web pages. Don't use JavaScript to link to other documents. Search Engines don't run JavaScript. It's also a bad idea because it should not be assumed that JavaScript is available (and turned on) in the user's browser. | |
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 | 2289 bytes; 1.6s@14.4Kbps, 0.8s@28.8, 0.5s@50, 0.4s@64, 0.2s@128, 0.1s@384, 0.0s@512, 0.0s@768, 0.0s@1.5Mbps, 0.0s@10Mbps. | |
Comment | 0.02s, 4 errors, 4 warnings, 11 messages, 13 validator comments, 52 lines, 48 tags (38 closed), 0 document comments, 5 entities, 117 programs run. |
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. | |
6: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. |
6:8 | Message (Search Engine) | [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable. |
9:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers. |
16:6 | 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. |
19: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. |
21:10 | Message (Good Style) | Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute. |
21:59 | Message (Microsoft Internet Explorer) | [1] The "bordercolor", "bordercolordark", and "bordercolorlight" attributes for the "table" element are not HTML or XHTML attributes and are currently only supported by Internet Explorer. For instance, Netscape 4.0 does not support these attributes. You've used at least one of these attributes in this "table" tag. |
25:13 | 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: #FFFF33". |
32:13 | 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. |
32:13 | 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. |
34:4 | Error | The "a" tag must have an end tag (</a>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <a target = "_self" href="earthquake.asp?eq=IT16880605m " > IT16880605m |
34:30 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
34:30 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
36:5 | Error | The end tag for "a" (opened in line 34) should appear before the end tag for "td" (nesting error). *</td> |
47:4 | Error | The "a" tag must have an end tag (</a>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <a target = "_self" href="earthquake.asp?eq=IT16940905m " > IT16940905m |
47:30 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
47:30 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
49:5 | Error | The end tag for "a" (opened in line 47) should appear before the end tag for "td" (nesting error). *</td> |
60:4 | Error | The "a" tag must have an end tag (</a>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <a target = "_self" href="earthquake.asp?eq=IT18050726m " > IT18050726m |
60:30 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
60:30 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
62:5 | Error | The end tag for "a" (opened in line 60) should appear before the end tag for "td" (nesting error). *</td> |
73:4 | Error | The "a" tag must have an end tag (</a>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <a target = "_self" href="earthquake.asp?eq=IT19300723m " > IT19300723m |
73:30 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
73:30 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
75:5 | Error | The end tag for "a" (opened in line 73) should appear before the end tag for "td" (nesting error). *</td> |
86:4 | Error | The "a" tag must have an end tag (</a>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <a target = "_self" href="earthquake.asp?eq=IT19801123m " > IT19801123m |
86:30 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
86:30 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
88:5 | Error | The end tag for "a" (opened in line 86) should appear before the end tag for "td" (nesting error). *</td> |
97:11 | Error | The "a" element cannot be used here. It is nested in another "a" tag and cannot be nested. Has the previous "a" element been ended? This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "a", "button", and "table". <p><a href="javascript: history.go(-1)"></a></p> |
99:13 | 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). |
99:13 | 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. |
106:2 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
107:2 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
108:2 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
109:2 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
110:2 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
118:5 | Error | The "a" element cannot be used here. It is nested in another "a" tag and cannot be nested. Has the previous "a" element been ended? This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "a", "button", and "table". <p><a href="javascript: history.go(-1)">BACK </a> </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 | Possibly misspelled words (30, 12 unique): Basilicata (1x), foreshock (1x), GR (1x), ITALY (1x), Molise (1x), Sannio (1x), yyyymmdd (1x), Irpinia (3x), E.Esposito (5x), L.Guerrieri (5x), Porfido (5x), Vittori (5x). Complete list. | |
Comment | XHTML 1.0 Transitional document detected. | |
Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration. | |
Comment (Search Engine) | [113] Random Search Engine Tip #11 - Avoid using JavaScript to insert tags and content into web pages. Don't use JavaScript to link to other documents. Search Engines don't run JavaScript. It's also a bad idea because it should not be assumed that JavaScript is available (and turned on) in the user's browser. | |
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 | 4248 bytes; 3.0s@14.4Kbps, 1.5s@28.8, 0.8s@50, 0.7s@64, 0.3s@128, 0.1s@384, 0.1s@512, 0.1s@768, 0.0s@1.5Mbps, 0.0s@10Mbps. | |
Comment | 0.02s, 12 errors, 17 warnings, 12 messages, 13 validator comments, 120 lines, 91 tags (73 closed), 0 document comments, 6 entities, 239 programs run. |
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. | |
6: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. |
6:8 | Message (Search Engine) | [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable. |
9:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers. |
16:4 | 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. |
19: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. |
21:10 | Message (Good Style) | Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute. |
21:27 | Message (Microsoft Internet Explorer) | [1] The "bordercolor", "bordercolordark", and "bordercolorlight" attributes for the "table" element are not HTML or XHTML attributes and are currently only supported by Internet Explorer. For instance, Netscape 4.0 does not support these attributes. You've used at least one of these attributes in this "table" tag. |
25:13 | 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: #FFFF33". |
32:62 | Error | The "a" tag must have an end tag (</a>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <td nowrap="nowrap" height="28"><div align="center"><a target = "_self" href="earthquake.asp?eq=JP19950117 " > JP19950117 * </div> </td> |
32:88 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
32:88 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
32:135 | Error | The end tag for "a" (opened in line 32) should appear before the end tag for "div" (nesting error). <td nowrap="nowrap" height="28"><div align="center"><a target = "_self" href="earthquake.asp?eq=JP19950117 " > JP19950117 * </div> </td> |
32:13 | 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. |
32:13 | 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. |
32:29 | 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. |
41:62 | Error | The "a" tag must have an end tag (</a>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <td nowrap="nowrap" height="28"><div align="center"><a target = "_self" href="earthquake.asp?eq=JP20041023m " > JP20041023m * </div> </td> |
41:88 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
41:88 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
41:137 | Error | The end tag for "a" (opened in line 41) should appear before the end tag for "div" (nesting error). <td nowrap="nowrap" height="28"><div align="center"><a target = "_self" href="earthquake.asp?eq=JP20041023m " > JP20041023m * </div> </td> |
50:11 | Error | The "a" element cannot be used here. It is nested in another "a" tag and cannot be nested. Has the previous "a" element been ended? This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "a", "button", and "table". <p><a href="javascript: history.go(-1)"></a><strong>Earthquake Code</strong>: it is the primary key (univocal) for the table “Earthquake” It is composed by 11 digits:<br /> |
56:11 | Error | The "a" element cannot be used here. It is nested in another "a" tag and cannot be nested. Has the previous "a" element been ended? This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "a", "button", and "table". <p><a href="javascript: history.go(-1)">BACK </a> </p> |
66:10 | 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). |
66:10 | Message (Good Style) | [7] The "height" and "width" attributes should be used with the "img" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. |
66:10 | 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. |
Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options. | |
Comment | You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options. | |
Comment | Possibly misspelled words (12, 8 unique): foreshock (1x), GR (1x), JAPAN (1x), yyyymmdd (1x), Azuma (2x), Hyogo (2x), Niigata (2x), Ota (2x). Complete list. | |
Comment | XHTML 1.0 Transitional document detected. | |
Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration. | |
Comment (Search Engine) | [113] Random Search Engine Tip #11 - Avoid using JavaScript to insert tags and content into web pages. Don't use JavaScript to link to other documents. Search Engines don't run JavaScript. It's also a bad idea because it should not be assumed that JavaScript is available (and turned on) in the user's browser. | |
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 | 3440 bytes; 2.4s@14.4Kbps, 1.2s@28.8, 0.7s@50, 0.5s@64, 0.3s@128, 0.1s@384, 0.1s@512, 0.0s@768, 0.0s@1.5Mbps, 0.0s@10Mbps. | |
Comment | 0.02s, 6 errors, 6 warnings, 14 messages, 13 validator comments, 75 lines, 87 tags (75 closed), 0 document comments, 14 entities, 234 programs run. |
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. | |
6: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. |
6:8 | Message (Search Engine) | [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable. |
9:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers. |
16:4 | 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. |
18:2 | 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. |
18: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. |
20:22 | 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. |
20:72 | Message (Microsoft Internet Explorer) | [1] The "bordercolor", "bordercolordark", and "bordercolorlight" attributes for the "table" element are not HTML or XHTML attributes and are currently only supported by Internet Explorer. For instance, Netscape 4.0 does not support these attributes. You've used at least one of these attributes in this "table" tag. |
22:13 | 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. |
24:13 | Message (Deprecated) | [9] The "bgcolor" attribute for the "th" and "th" elements is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Consider using the "background-color" CSS property instead of the "bgcolor" attribute. |
31:52 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
31:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
31:99 | Error | The end tag for "a" (opened in line 31) should appear before the end tag for "td" (nesting error). <td height="44"><a target = "_self" href="earthquake.asp?eq=PE15860710M " > PE15860710M*</td> |
32:14 | 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. |
32:14 | 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. |
42:52 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
42:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
42:99 | Error | The end tag for "a" (opened in line 42) should appear before the end tag for "td" (nesting error). <td height="44"><a target = "_self" href="earthquake.asp?eq=PE16041124M " > PE16041124M*</td> |
53:52 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
53:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
53:99 | Error | The end tag for "a" (opened in line 53) should appear before the end tag for "td" (nesting error). <td height="44"><a target = "_self" href="earthquake.asp?eq=PE16871020M " > PE16871020M*</td> |
64:52 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
64:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
64:99 | Error | The end tag for "a" (opened in line 64) should appear before the end tag for "td" (nesting error). <td height="44"><a target = "_self" href="earthquake.asp?eq=PE17461029M " > PE17461029M*</td> |
75:52 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
75:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
75:99 | Error | The end tag for "a" (opened in line 75) should appear before the end tag for "td" (nesting error). <td height="44"><a target = "_self" href="earthquake.asp?eq=PE18680813M " > PE18680813M*</td> |
86:52 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
86:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
86:99 | Error | The end tag for "a" (opened in line 86) should appear before the end tag for "td" (nesting error). <td height="44"><a target = "_self" href="earthquake.asp?eq=PE18770510M " > PE18770510M*</td> |
97:52 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
97:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
97:99 | Error | The end tag for "a" (opened in line 97) should appear before the end tag for "td" (nesting error). <td height="44"><a target = "_self" href="earthquake.asp?eq=PE19400524M " > PE19400524M*</td> |
108:52 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
108:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
108:99 | Error | The end tag for "a" (opened in line 108) should appear before the end tag for "td" (nesting error). <td height="44"><a target = "_self" href="earthquake.asp?eq=PE19420824M " > PE19420824M*</td> |
119:52 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
119:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
119:99 | Error | The end tag for "a" (opened in line 119) should appear before the end tag for "td" (nesting error). <td height="44"><a target = "_self" href="earthquake.asp?eq=PE19461110M " > PE19461110M*</td> |
130:52 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
130 | 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. <td height="44"><a target = "_self" href="earthquake.asp?eq=PE19500521M " > PE19500521M*</td> |
Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options. | |
Comment | You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options. | |
Comment | Possibly misspelled words (54, 13 unique): CAJATAMBO (1x), CALLAO (1x), CAÑETE (1x), IQUIQUE (1x), LIMA (1x), NAZCA (1x), PALLASCA (1x), TACNA (1x), GEOFISICO (9x), INSTITUTO (9x), Vilcapoma (9x), Zamudio (9x), PERU (10x). 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 | XHTML 1.0 Transitional document detected. | |
Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration. | |
Comment (Search Engine) | [113] Random Search Engine Tip #11 - Avoid using JavaScript to insert tags and content into web pages. Don't use JavaScript to link to other documents. Search Engines don't run JavaScript. It's also a bad idea because it should not be assumed that JavaScript is available (and turned on) in the user's browser. | |
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 | 16354 bytes; 11.4s@14.4Kbps, 5.7s@28.8, 3.3s@50, 2.6s@64, 1.3s@128, 0.4s@384, 0.3s@512, 0.2s@768, 0.1s@1.5Mbps, 0.0s@10Mbps. | |
Comment | 0.04s, 10 errors, 20 warnings, 13 messages, 14 validator comments, 368 lines, 138 tags (118 closed), 0 document comments, 0 entities, 402 programs run. |
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. | |
6: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. |
6:8 | Message (Search Engine) | [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable. |
11:4 | 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. |
12:2 | 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. |
12: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. |
14:22 | 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. |
14:71 | Message (Microsoft Internet Explorer) | [1] The "bordercolor", "bordercolordark", and "bordercolorlight" attributes for the "table" element are not HTML or XHTML attributes and are currently only supported by Internet Explorer. For instance, Netscape 4.0 does not support these attributes. You've used at least one of these attributes in this "table" tag. |
18:13 | 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: #FFFF33". |
25:30 | Error | The "a" tag must have an end tag (</a>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=RU19950527m " > RU19950527m*</td> |
25:56 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
25:56 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
25:103 | Error | The end tag for "a" (opened in line 25) should appear before the end tag for "td" (nesting error). <td nowrap="nowrap"><a target = "_self" href="earthquake.asp?eq=RU19950527m " > RU19950527m*</td> |
25:13 | 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. |
25:13 | 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. |
34:22 | 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:22 | 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. |
43:5 | Error | The "a" element cannot be used here. It is nested in another "a" tag and cannot be nested. Has the previous "a" element been ended? This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "a", "button", and "table". <p><a href="javascript: history.go(-1)">BACK</a></p> |
46:27 | Warning | [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "area" element. This attribute lets authors specify alternate text to serve as content when the element cannot be rendered or accessed normally. For example, this attribute is critical for visually impaired users and user agents that cannot display images and image maps. |
Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options. | |
Comment | You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options. | |
Comment | Possibly misspelled words (10, 10 unique): A.N.Ovsyuchenko (1x), E.A.Rogozhin (1x), foreshock (1x), GR (1x), Neftegorsk (1x), R.E.Tatevossian (1x), RUSSIA (1x), S.S.Arefiev (1x), Sakhalin (1x), yyyymmdd (1x). Complete list. | |
Comment | XHTML 1.0 Transitional document detected. | |
Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration. | |
Comment (Search Engine) | [113] Random Search Engine Tip #11 - Avoid using JavaScript to insert tags and content into web pages. Don't use JavaScript to link to other documents. Search Engines don't run JavaScript. It's also a bad idea because it should not be assumed that JavaScript is available (and turned on) in the user's browser. | |
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 | 2098 bytes; 1.5s@14.4Kbps, 0.7s@28.8, 0.4s@50, 0.3s@64, 0.2s@128, 0.1s@384, 0.0s@512, 0.0s@768, 0.0s@1.5Mbps, 0.0s@10Mbps. | |
Comment | 0.02s, 3 errors, 4 warnings, 13 messages, 13 validator comments, 48 lines, 42 tags (32 closed), 0 document comments, 5 entities, 112 programs run. |
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. | |
6: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. |
6:8 | Message (Search Engine) | [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable. |
9:2 | Warning | In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers. |
16:4 | 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. |
17:2 | 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. |
17: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. |
19:22 | 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. |
19:71 | Message (Microsoft Internet Explorer) | [1] The "bordercolor", "bordercolordark", and "bordercolorlight" attributes for the "table" element are not HTML or XHTML attributes and are currently only supported by Internet Explorer. For instance, Netscape 4.0 does not support these attributes. You've used at least one of these attributes in this "table" tag. |
23:13 | 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: #FFFF33". |
30:40 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
30:40 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
30:81 | Error | The end tag for "a" (opened in line 30) should appear before the end tag for "td" (nesting error). <td><a target = "_self" href="earthquake.asp?eq=SP1100bp " > SP1100bp*</td> |
40:40 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
40:40 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
40:85 | Error | The end tag for "a" (opened in line 40) should appear before the end tag for "td" (nesting error). <td><a target = "_self" href="earthquake.asp?eq=SP18040825 " > SP18040825*</td> |
49:40 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
49:40 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
49:85 | Error | The end tag for "a" (opened in line 49) should appear before the end tag for "td" (nesting error). <td><a target = "_self" href="earthquake.asp?eq=SP18290321 " > SP18290321*</td> |
58:40 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
58:40 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
58:85 | Error | The end tag for "a" (opened in line 58) should appear before the end tag for "td" (nesting error). <td><a target = "_self" href="earthquake.asp?eq=SP18510515 " > SP18510515*</td> |
67:40 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
67:40 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
67:85 | Error | The end tag for "a" (opened in line 67) should appear before the end tag for "td" (nesting error). <td><a target = "_self" href="earthquake.asp?eq=SP18630610 " > SP18630610*</td> |
77:40 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
77:40 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
77:85 | Error | The end tag for "a" (opened in line 77) should appear before the end tag for "td" (nesting error). <td><a target = "_self" href="earthquake.asp?eq=SP18841225 " > SP18841225*</td> |
86:40 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
86:40 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
86:85 | Error | The end tag for "a" (opened in line 86) should appear before the end tag for "td" (nesting error). <td><a target = "_self" href="earthquake.asp?eq=SP19560419 " > SP19560419*</td> |
96:40 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
96:40 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
96:85 | Error | The end tag for "a" (opened in line 96) should appear before the end tag for "td" (nesting error). <td><a target = "_self" href="earthquake.asp?eq=SP19990202 " > SP19990202*</td> |
106:40 | Warning | Using space characters in URLs may cause problems. If spaces must be used in URLs, then they should be encoded as "%20" (without the quotes). However, avoid spaces in URLs whenever possible and consider using the underscore character (_) instead of space characters in directory names and filenames. |
106:40 | Warning | [33] The "href" attribute has a value that has leading or trailing space characters. These spaces should probably be removed. |
106:85 | Error | The end tag for "a" (opened in line 106) should appear before the end tag for "td" (nesting error). <td><a target = "_self" href="earthquake.asp?eq=SP20050129 " > SP20050129*</td> |
116:22 | 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). |
116:22 | Message (Search Engine) | [8] Alt text is often used by search engines. Use this to your advantage (but do it appropriately). Furthermore, alt text is critical for accessibility. For these reasons and others, it is highly recommended that appropriate alt text be specified using the "alt" attribute. This message is displayed only once. |
121 | 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. <area shape="circle" coords="452,280,11" href="earthquake.asp?eq=SP1100bp" /><area shape="circle" coords="513,312,11" href="earthquake.asp?eq=SP18290321" /> |
Comment (Accessibility Tips) [ACCESSIBILITY] | This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options. | |
Comment | You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options. | |
Comment | Possibly misspelled words (41, 33 unique): Albolote (1x), Alicante (1x), Bardají (1x), Dalias (1x), Díaz (1x), Fetiche (1x), Gimènez (1x), Huercal (1x), J.Lario (1x), J.M.Azanon (1x), Jordi (1x), Lario (1x), López (1x), Mallorca (1x), Martínez (1x), Mula (1x), Overa (1x), P.Alfaro (1x), Paca (1x), Pascua (1x), Pérez (1x), Rey (1x), Rodríguez (1x), SPAIN (1x), T.Bardajì (1x), Torrevieja (1x), Albacete (2x), Almería (2x), Granada (2x), Murcia (2x), Silva (2x), Tobarra (2x), P.G.Silva (3x). 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 | XHTML 1.0 Transitional document detected. | |
Comment | [24] The XHTML recommendation strongly encourages that an XML declaration be used as the first line (line 1) of every XHTML document. For example, for XHTML and WML documents, something similar to <?xml version="1.0" encoding="UTF-8"?> or simply <?xml version="1.0"?> should be the first line. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. However, in practice, correctly using an XML declaration may cause problems, such as triggering Internet Explorer 6's "quirks" mode (which causes non-standards compliant rendering). Because of this, consider not using an XML declaration. | |
Comment (Search Engine) | [113] Random Search Engine Tip #11 - Avoid using JavaScript to insert tags and content into web pages. Don't use JavaScript to link to other documents. Search Engines don't run JavaScript. It's also a bad idea because it should not be assumed that JavaScript is available (and turned on) in the user's browser. | |
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 | 6069 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, 10 errors, 20 warnings, 11 messages, 14 validator comments, 138 lines, 122 tags (106 closed), 0 document comments, 0 entities, 320 programs run. |
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 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