David Dorward <dorward@yahoo.com> wrote:

I meant validation tool, but ty anyway. I'll have to look up HTML
4.01 Strict and see what it means. Thanks.

--
http://www.ren-prod-inc.com/hug_soft...action=contact

"hug" <contact_info@sig_line.clickit> wrote in message
news:sk4fs1du75ff20uiik5tp1e60ntfkhdpc4@4ax.com...
Cool. I feel popular now :-)

The W3 validator is not perfect but it is useful and it works.

In message <r2ocs1lgdqnjhejva00k6koc2moija11j6@4ax.com>, hug
<contact_info@sig_line.clickit> writes
http://www.htmlvalidator.com/

--
Craig Cockburn ("coburn"). http://www.SiliconGlen.com/
Please sign the Spam Petition: http://www.siliconglen.com/spampetition/
Home to the first online guide to Scotland, founded 1994.
Scottish FAQ, weddings, website design, stop spam and more!

Craig Cockburn <craig@siliconglen.com> wrote:

Thanks.

--
http://www.ren-prod-inc.com/hug_soft...action=contact

Craig Cockburn wrote:

It has a bit of a dodgy rep. I'd avoid it myself.
http://groups.google.com/group/comp....a9665070809b4f


--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is

In message <dqa9p4$678$1$8302bc10@news.demon.co.uk>, David Dorward
<dorward@yahoo.com> writes

--
Craig Cockburn ("coburn"). http://www.SiliconGlen.com/
Please sign the Spam Petition: http://www.siliconglen.com/spampetition/
Home to the first online guide to Scotland, founded 1994.
Scottish FAQ, weddings, website design, stop spam and more!

Craig Cockburn wrote:

There are a number of issues raised there. Certainly I'm not heard of any of
them being resolved, but I don't follow its development closely (since it
doesn't run on my platform and costs a lot more then the alternatives).

--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is

This is a subject that has always facinated me a bit.. Seems to be a point
of pride to a lot of folks. I've never been able to figure out what the
big deal is, except as a little mental masturbation...

For instance, if you run Google's home page through http://validator.w3.org/
, you will see that it finds 50 validation errors. www.yahoo.com has 252
errors, and whatdoyouknow, www.microsoft.com passes..

So.... it's apparently important to MS and not important to Yahoo and
Google, who with all their resources, could run the errors down and fix at
least most of them in a day or so..

Personally, I never worry about it, except as an easy check to see if I've
closed all the tags in a table, etc..

Interesting subject, tho'

Bruce



"hug" <contact_info@sig_line.clickit> wrote in message
news:vpgcs1topqa0qvfbkmk86054tilaabrvkk@4ax.com...

In message <NGdyf.2512$Hd4.32@newsread1.news.pas.earthlink.ne t>, BruceB
<dontwriteme@tshirts.nu> writes

Validator message export for "http://www.microsoft.com":
Generated by CSE HTML Validator Professional v7.01
(http://www.htmlvalidator.com/)

1. Message in line 9 at character 35: (Grouped->Search Engine) This
description meta tag contains 4 commas. Some search engines may think
this indicates a keyword list, consider it spam, and penalize your
listing. AI Internet Solutions recommends using no more than three
commas in the description meta tag.

2. Message in line 12 at character 2: (Grouped->Search Engine) [111] Tip
- A good title is very important for search engine listings. Use many
keywords and search terms in your title tag but make it readable. It
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>.

3. Message in line 12 at character 8: (Grouped->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.

4. Message in line 14 at character 2: (Grouped->General Compatibility)
[5] Style sheet information is supported by Internet Explorer 3.0+,
Netscape 4.0+, and most newer browsers such as Firefox and Opera 3.5+.
Older browsers may not use style information. Furthermore, browsers that
do support style sheets may support them differently and to different
degrees than other browsers that also support style sheets. Using style
sheets may also cause style related incompatibility problems between
different browsers.

5. Message in line 14 at character 2: (Accessibility->Section 508
Accessibility Standards) Documents must be organized so they are
readable without requiring an associated style sheet [Section 1194.22
(d)]. This means that when a document is rendered without its associated
style sheet(s) that it is still possible to read it. This message is
displayed only once.

6. Message in line 14 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 1)) Documents should be organized
so they can be read without style sheets [P1, 6.1]. This means that when
a document is rendered without its associated style sheet(s) that it is
still possible to read it. This message is displayed only once.

7. Warning in line 15 at character 1: It is recommended (and common
practice for HTML (not XHTML) documents) that text contained in a
"style" element be enclosed in a comment (<!-- ... -->) for backward
compatibility with pre HTML 3.2 browsers that do not support the "style"
element. This prevents them from actually displaying the element's
content. For example, use something like <style><!-- ... --></style>.

8. Message in line 15 at character 1: (Styles->General Compatibility)
The "@import" directive is an official CSS1 and CSS2 directive and is
supported by newer browsers such as Internet Explorer 4.0+, Netscape
6.0+, and Opera 3.0+ but not by Internet Explorer 3.0- and Netscape
4.x-.

9. Message in line 17 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 1)) Ensure that pages are usable
when scripts, applets, or other programmatic objects are turned off or
not supported (for example, consider using the "noscript" element to
provide functional HTML/text for "script" elements). If this is not
possible, provide equivalent information on an alternative accessible
page [P1, 6.3]. This message is displayed only once.

10. Message in line 17 at character 2: (Accessibility->Section 508
Accessibility Standards) When pages utilize scripting languages to
display content, or to create interface elements, the information
provided by the script shall be identified with functional text that can
be read by assistive technology [Section 1194.22 (l)]. Ensure that all
the programmatic objects and elements on this page conform to this
requirement (for example, consider using the "noscript" element to
provide functional HTML/text for "script" elements). This requirement
helps ensure that user agents that don't support these objects or that
have them turned off will still be able to provide the user with usable
content. This message is displayed only once.

11. Message in line 17 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 1)) All scripts should have a
text equivalent. Consider using the "noscript" element to provide the
text equivalent. The content of the "noscript" element will be rendered
if scripts are turned off or not supported (the Lynx text-only browser
does not support scripts). This message is displayed only once. [P1,
1.1]

12. Message in line 17 at character 2: (Accessibility->Section 508
Accessibility Standards) All scripts must have a text equivalent.
Consider using the "noscript" element to provide the text equivalent.
The content of the "noscript" element will be rendered if scripts are
turned off or not supported (the Lynx text-only browser does not support
scripts). This message is displayed only once. [Section 1194.22 (a)]

13. Message in line 17 at character 2: (Accessibility->Accessibility
Tips) When designing web pages, consider that scripts and programmatic
objects pose potential accessibility problems for users: 1) some user
agents, like the Lynx text-only browser, do not support scripts, 2)
scripts can cause problems with screen readers, 3) some users disable
scripts even though their user agent supports them, and 4) scripts are
sometimes disabled in schools, libraries, and public access places.

14. Message in line 28 at character 2: (Accessibility->Accessibility
Tips) If appropriate, consider using a "caption" element to describe or
identify the nature or purpose of this table. Use this element
immediately after the "table" start tag. Note that the contents of this
element does appear as onscreen text and should not be the same as the
contents of the "summary" attribute. Example captions: "Hamburgers
consumed by each student", "Who spends the most on advertising?". If
this is a layout table, then use the word "layout" in the table's
"summary" attribute and this message will not be displayed.

15. Message in line 28 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 1)) Row and column headers should
be identified for data tables [P1, 5.1]. This table contains no "th"
elements. If it is a data table, then "th" elements should be used to
specify and identify row and/or column header cells. Use "td" elements
to identify data cells. If this is a layout table, then use the word
"layout" in the table's "summary" attribute and this message will not be
displayed.

16. Message in line 28 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 2)) Avoid using tables for layout
unless the table makes sense when linearized (if it doesn't make sense,
then provide an alternative equivalent, which may be a linearized
version) [P2, 5.3]. Also, if a table is used for layout, do not use any
structural markup for the purpose of visual formatting [P2, 5.4]. CSS is
recommended for visual formatting. A linearized table is one that makes
sense when its cells are read in row order. This message is displayed
only once.

17. Message in line 28 at character 2: (Accessibility->Section 508
Accessibility Standards) Row and column headers shall be identified for
data tables [Section 1194.22 (g)]. This table contains no "th" elements.
If it is a data table, then "th" elements must be used to specify and
identify row and/or column header cells. Use "td" elements to identify
data cells. If this is a layout table, then use the word "layout" in the
table's "summary" attribute and this message will not be displayed.

18. Message in line 28 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 3)) Consider using a "summary"
attribute with this "table" tag to provide a summary of the entire
table's purpose and structure for user agents rendering to non-visual
media such as speech and braille. Note that this attribute may not be
widely supported and that the summary text is not displayed on the
screen. [P3, 5.5]

19. Message in line 28 at character 2: (Grouped->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. Warning in line 29 at character 37: The "style" attribute has been
used but a default style sheet language has not been defined (note that
HTML Validator would not see this declaration if it is sent as an HTTP
header by a web server). HTML 4.01 and XHTML require this for valid
documents. For example, include this in the "head" section of your
document to specify "text/css" as the default style sheet language:
<meta http-equiv="Content-Style-Type" content="text/css">. See
http://www.w3.org/TR/html4/present/s...#default-style for more
information. If you are using HTML Validator's integrated editor, then
you can add this from the Tags menu and/or from the Tag Inserter.

21. Message in line 29 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 1)) Row and column headers should
be identified for data tables [P1, 5.1]. This table contains no "th"
elements. If it is a data table, then "th" elements should be used to
specify and identify row and/or column header cells. Use "td" elements
to identify data cells. If this is a layout table, then use the word
"layout" in the table's "summary" attribute and this message will not be
displayed.

22. Message in line 29 at character 2: (Accessibility->Accessibility
Tips) If appropriate, consider using a "caption" element to describe or
identify the nature or purpose of this table. Use this element
immediately after the "table" start tag. Note that the contents of this
element does appear as onscreen text and should not be the same as the
contents of the "summary" attribute. Example captions: "Hamburgers
consumed by each student", "Who spends the most on advertising?". If
this is a layout table, then use the word "layout" in the table's
"summary" attribute and this message will not be displayed.

23. Message in line 29 at character 2: (Accessibility->Section 508
Accessibility Standards) Row and column headers shall be identified for
data tables [Section 1194.22 (g)]. This table contains no "th" elements.
If it is a data table, then "th" elements must be used to specify and
identify row and/or column header cells. Use "td" elements to identify
data cells. If this is a layout table, then use the word "layout" in the
table's "summary" attribute and this message will not be displayed.

24. Message in line 29 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 3)) Consider using a "summary"
attribute with this "table" tag to provide a summary of the entire
table's purpose and structure for user agents rendering to non-visual
media such as speech and braille. Note that this attribute may not be
widely supported and that the summary text is not displayed on the
screen. [P3, 5.5]

25. Message in line 29 at character 37: (Styles->CSS Tips) Use the
inline "style" attribute sparingly. Using this attribute too often can
prevent you from receiving many of the benefits of CSS like easier to
maintain and less cluttered documents. Consider using a single CSS style
sheet instead of relying too much on the "style" attribute. This message
is displayed only once.

26. Message in line 30 at character 5: (Grouped->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.

27. Message in line 33 at character 40: (Grouped->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.

28. Message in line 33 at character 40: (Grouped->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.

29. Message in line 34 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 1)) Row and column headers should
be identified for data tables [P1, 5.1]. This table contains no "th"
elements. If it is a data table, then "th" elements should be used to
specify and identify row and/or column header cells. Use "td" elements
to identify data cells. If this is a layout table, then use the word
"layout" in the table's "summary" attribute and this message will not be
displayed.

30. Message in line 34 at character 2: (Accessibility->Accessibility
Tips) If appropriate, consider using a "caption" element to describe or
identify the nature or purpose of this table. Use this element
immediately after the "table" start tag. Note that the contents of this
element does appear as onscreen text and should not be the same as the
contents of the "summary" attribute. Example captions: "Hamburgers
consumed by each student", "Who spends the most on advertising?". If
this is a layout table, then use the word "layout" in the table's
"summary" attribute and this message will not be displayed.

31. Message in line 34 at character 2: (Grouped->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.

32. Message in line 34 at character 2: (Accessibility->Section 508
Accessibility Standards) Row and column headers shall be identified for
data tables [Section 1194.22 (g)]. This table contains no "th" elements.
If it is a data table, then "th" elements must be used to specify and
identify row and/or column header cells. Use "td" elements to identify
data cells. If this is a layout table, then use the word "layout" in the
table's "summary" attribute and this message will not be displayed.

33. Message in line 34 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 3)) Consider using a "summary"
attribute with this "table" tag to provide a summary of the entire
table's purpose and structure for user agents rendering to non-visual
media such as speech and braille. Note that this attribute may not be
widely supported and that the summary text is not displayed on the
screen. [P3, 5.5]

34. Warning in line 35 at character 105: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

35. Message in line 35 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 2)) For scripts, use logical
event handlers instead of device-dependent event handlers [P2, 9.3].
Such device-dependent event handlers (like the "onmouse" handlers) can
cause many accessibility problems because they require a specific device
in order to work. One solution for the "onmouseout" and "onmouseover"
handlers may be to duplicate their functionality by also using the
logical "onblur" and "onfocus" handlers. Consider other solutions for
other device-dependent handlers. This message is displayed only once.

36. Warning in line 37 at character 105: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

37. Message in line 40 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 1)) Row and column headers should
be identified for data tables [P1, 5.1]. This table contains no "th"
elements. If it is a data table, then "th" elements should be used to
specify and identify row and/or column header cells. Use "td" elements
to identify data cells. If this is a layout table, then use the word
"layout" in the table's "summary" attribute and this message will not be
displayed.

38. Message in line 40 at character 2: (Accessibility->Accessibility
Tips) If appropriate, consider using a "caption" element to describe or
identify the nature or purpose of this table. Use this element
immediately after the "table" start tag. Note that the contents of this
element does appear as onscreen text and should not be the same as the
contents of the "summary" attribute. Example captions: "Hamburgers
consumed by each student", "Who spends the most on advertising?". If
this is a layout table, then use the word "layout" in the table's
"summary" attribute and this message will not be displayed.

39. Message in line 40 at character 2: (Accessibility->Section 508
Accessibility Standards) Row and column headers shall be identified for
data tables [Section 1194.22 (g)]. This table contains no "th" elements.
If it is a data table, then "th" elements must be used to specify and
identify row and/or column header cells. Use "td" elements to identify
data cells. If this is a layout table, then use the word "layout" in the
table's "summary" attribute and this message will not be displayed.

40. Message in line 40 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 3)) Consider using a "summary"
attribute with this "table" tag to provide a summary of the entire
table's purpose and structure for user agents rendering to non-visual
media such as speech and braille. Note that this attribute may not be
widely supported and that the summary text is not displayed on the
screen. [P3, 5.5]

41. Message in line 40 at character 37: (Grouped->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 the
"bgcolor" attribute, consider using the CSS property "background-color".
Example: style="background-color: #FFFFFF".

42. Warning in line 41 at character 36: It is recommended (and common
practice for HTML (not XHTML) documents) that text contained in a
"script" element be enclosed in a comment (<!-- ... -->) for backward
compatibility with pre HTML 3.2 browsers that do not support the
"script" element. This prevents them from actually displaying the
element's content. For example, use something like <script><!-- ...
--></script>. For maximum compatibility, AI Internet Solutions
recommends putting the script (especially longer scripts) in an external
file and using the "src" attribute to specify the external file.
However, this is not as important for HTML documents as it is for XHTML
documents.

43. Warning in line 41 at character 182: It is recommended (and common
practice for HTML (not XHTML) documents) that text contained in a
"script" element be enclosed in a comment (<!-- ... -->) for backward
compatibility with pre HTML 3.2 browsers that do not support the
"script" element. This prevents them from actually displaying the
element's content. For example, use something like <script><!-- ...
--></script>. For maximum compatibility, AI Internet Solutions
recommends putting the script (especially longer scripts) in an external
file and using the "src" attribute to specify the external file.
However, this is not as important for HTML documents as it is for XHTML
documents.

44. Message in line 41 at character 50: (Grouped->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.

45. Error in line 42 at character 238: (Accessibility->Section 508
Accessibility Standards) The "input" tag has an "id" attribute but it
must be used to explicitly associate this control with a "label" element
using the "label" element's "for" attribute (for="msviDualSearchBox").
When electronic forms are designed to be completed online, the form
shall allow people using assistive technology to access the information,
field elements, and functionality required for completion and submission
of the form, including all directions and cues [Section 1194.22 (n)].
Information attached to controls via the "label" element can be very
useful to users of talking browsers. Note that "id" and "for" values are
case sensitive. Visit
http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels for more
information.

46. Message in line 42 at character 31: (Grouped->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: #FFFFFF".

47. Message in line 42 at character 233: [41] The "div" tag has no
attributes. Attributes are normally used with the "div" element to
provide functionality.

48. Message in line 42 at character 488: (Grouped->General
Compatibility) [5] The "label" element is an official HTML 4.01 and
XHTML element and is supported by Internet Explorer 4.0+, Netscape 6.0+,
and Opera 4+. Note that Netscape 4.7- does not support this element.

49. Message in line 42 at character 624: (Grouped->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.

50. Message in line 44 at character 2: (Accessibility->Web Content
Accessibility Guidelines 1.0 (Priority 3)) Consider using a "summary"
attribute with this "table" tag to provide a summary of the entire
table's purpose and structure for user agents rendering to non-visual
media such as speech and braille. Note that this attribute may not be
widely supported and that the summary text is not displayed on the
screen. [P3, 5.5]

51. Warning in line 46 at character 57: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

52. Warning in line 46 at character 195: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

53. Warning in line 46 at character 331: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

54. Warning in line 46 at character 509: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

55. Warning in line 46 at character 644: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

56. Warning in line 46 at character 814: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

57. Warning in line 46 at character 966: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

58. Warning in line 46 at character 1069: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

59. Warning in line 46 at character 1227: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

60. Warning in line 46 at character 1427: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

61. Warning in line 46 at character 1571: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

62. Warning in line 46 at character 1727: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

63. Warning in line 46 at character 1886: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

64. Warning in line 46 at character 2028: It appears that the attribute
value for "href" may not be in a valid form such as http://, https://,
ftp://, gopher://, nntp://, telnet://, wais://, javascript:, mailto:,
news:, or newsrc:.

65. Error in line 46: 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.

66. Comment: (Accessibility->Accessibility Tips) 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.

67. Comment: (Grouped->Search Engine) If you're concerned about top
search engine rankings, visit http://www.htmlvalidator.com/seo.html

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

69. Comment: Possibly misspelled words (2, 2 unique): Microsoft.com
(1x), Xbox (1x). Complete list.

70. Comment: HTML 4.0 Transitional document detected.

71. Comment: It is recommended that you update this HTML 4.0 document to
HTML 4.01 or to XHTML. Updating to HTML 4.01 can easily be done in most
cases by simply replacing the HTML 4.0 DOCTYPE with an HTML 4.01
DOCTYPE. Updating to XHTML usually requires much more work than simply
changing the DOCTYPE. HTML 4.01 DOCTYPEs and other DOCTYPEs can be
inserted from the Tag Inserter.

72. Comment: (Grouped->Search Engine) [113] Random Search Engine Tip #14
- Provide fresh content on your site from time to time to keep it from
"decaying". Provide quality content. The more quality content on your
site, the better.

73. Comment: (Accessibility->Web Content Accessibility Guidelines 1.0
(Priority 3)) Be sure to provide keyboard shortcuts to important links
(including those in client-side image maps), form controls, and groups
of form controls. This is often done using the "accesskey" attribute.
[P3, 9.5]

74. Comment: (Accessibility->Web Content Accessibility Guidelines 1.0
(Priority 3)) The "a" element was used 18 times but not one "a" tag
contained an "accesskey" attribute. Be sure to provide keyboard
shortcuts for any important links [P3, 9.5].

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

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

77. Comment: 19747 bytes; 13.7s@14.4Kbps, 6.9s@28.8, 3.9s@50, 3.1s@64,
1.5s@128, 0.5s@384, 0.4s@512, 0.3s@768, 0.1s@1.5Mbps, 0.0s@10Mbps.

78. Comment: 0.06s, 2 errors, 20 warnings, 43 messages, 13 validator
comments, 101 lines, 92 tags (67 closed), 2 document comments, 1 entity,
233 programs run.

--
Craig Cockburn ("coburn"). http://www.SiliconGlen.com/
Please sign the Spam Petition: http://www.siliconglen.com/spampetition/
Home to the first online guide to Scotland, founded 1994.
Scottish FAQ, weddings, website design, stop spam and more!

" BruceB" <dontwriteme@tshirts.nu> wrote in message
news:NGdyf.2512$Hd4.32@newsread1.news.pas.earthlin k.net...
It really depends on your point of view. At the end of the day, why use HTML
if you are going to use it in a "non-standard" manner.

Valid HTML has the advantage of being the most likely to "work" on as many
current platforms as possible, but more importantly on future platforms.

If you have coded a hodgepodge of tags, some closed, some not closed then a
new browser appears and takes the world by storm you have to go through all
your code to ensure it is compatible.

Wonders never cease.

Looking at Google's errors for example, the 48 I get from google.co.uk are
pretty mundane. Not having a DOCTYPE, not declaring the type="text/css" for
the stylesheets, not encoding ampersands etc. Obviously Google are aware
that if this turns out to break a modern popular browser then they can edit
their code to accomodate it.

Things like "<a href=/intl/en/about.html>" is strange, I am not sure what
(if any) effect that has on browsers.

Sometimes I use odd browsers to access websites, and there is no faster way
to permanently lose my business than a site failing to allow access. When I
sit on the train and use my phone to access sites, I mentally note ones that
I will never, ever use again if they produce gibberish.

Generally speaking, large sites with lots of coders dont really need to
worry too much about the code that comes out as they have the personell and
resources to fix anything that goes astray.

Producing and testing code for screen readers, mobile devices, different
browsers, different OS, different screen sizes etc., is time consuming and
costly. If you are a big company, more concerned with your site appearing
the same on all platforms then it is a price you are prepared to pay. If you
are a small webdesigner then it may not be.

No idea why MS are "pure" - maybe they are doing it out of spite :-)

Why does that bother you? If you dont want valid code, just use any mark up
you like.

I would never suggest obsession with hunting down obscure mark up errors,
but (especially when you create pages from scratch) it is remarkably easy to
code valid HTML which in turn avoids all manner of problems later down the
line.

Personally, I like to take the easiest, laziest route possible. Creating
valid HTML at the outset, separating logic from content, and style from
content all go miles to making my life easy when it comes to creating sites
or web applications.