
--------------------------------------------------

CSE HTML Validator Professional v6.50 (Registered)
Checking "G:\winbel\winbel.html" (4401 bytes).
File date is 04 July 2004 at 09:49:28.
File checked on 04 July 2004 at 10:15:16.

     Number of lines checked: 76 in 0.88 seconds
      Number of programs run: 162
 Number of lines in document: 123 (61.8% of lines checked)
     Number of lines ignored: 47
Number of character entities: 2
        Number of start tags: 65
          Number of end tags: 41 (63.1% of start tags with end tags)
Number of <% ... %> sections: 0
     Number of HTML comments: 0

Number of validator comments: 12
          Number of messages: 21
            Number of errors: 1 (first in line 107)
          Number of warnings: 0

--------------------------------------------------

   1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">

   2: <HTML>
-------||||

[CSE] Message number 1 for the tag beginning in line 2:2:
The natural primary language of a document should be
identified [P3, 4.3]. Consider using the "lang" and/or (for
XHTML) "xml:lang" attributes with the "html" tag to specify
the language. For example, lang="en" for English or
lang="fr" for French. Note that the language may also be
specified by the web server through HTTP headers in which
case checkpoint 4.3 would be satisfied without the "lang" or
"xml:lang" attributes.

   3: <HEAD><TITLE>General template</TITLE>
-------------------||||||||||||||||

[CSE] Message number 2 for the tag beginning in line 3:14:
[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.

   4: <META http-equiv="Content-Style-Type" content="text/css; charset=windows-1252">

   5: <STYLE type="text/css" lang="en">
-------|||||

[CSE] Message number 3 for the tag beginning in line 5:2:
[5] Style sheet information is supported by Internet
Explorer 3.0+, Netscape 4.0+, Opera 3.5+, and most newer
browsers. Older browsers and text browsers (such as Lynx)
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. You should be aware that using style sheets
may cause style related incompatibility problems between
different browsers.

   5: <STYLE type="text/css" lang="en">
-------|||||

[CSE] Message number 4 for the tag beginning in line 5:2:
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.

   5: <STYLE type="text/css" lang="en">
-------|||||

[CSE] Message number 5 for the tag beginning in line 5:2:
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.

   6: <!--
   7: a:hover {color:red}
   8: 
   9: #leftpanel {
  10:  LEFT: 0px; WIDTH: 1px; POSITION: absolute; TOP: 1px}
  11: 
  12: #rightpanel {
  13:  RIGHT: 0px; WIDTH: 1px; POSITION: absolute; TOP: 1px}
  14: 
  15: #content {
  16:  font: bold 12px/18px "Verdana";POSITION: absolute; TOP: 5px}
  17: 
  18: H1 {font:24px Verdana;color:#005073;background-color:#ffffff; border:black 2px solid; padding:5px; width:67%;margin-left:0%;}
  19: 
  20: H2 {font: bold 14px Verdana;color:#000080}
  21: 
  22: .black {color:black; font-size:24px};
  23: 
  24: .head_cell {background-color:#D5E9D7;font-weight:bold}
  25: 
  26: TABLE {
  27:   PADDING: 5px; BACKGROUND-COLOR: #ffffff; border: black 1px solid;border-collapse:collapse;margin:0 10px}
  28: 
  29: TD {
  30:  border:0;border-bottom: black 1px solid; border-right:black 1px solid;
  31:    background-color:#fffded;}
  32: 
  33: .update {font: 12px/15px "Times New Roman";FONT-STYLE: italic;}
  34: 
  35: 
  36: -->
  37: </STYLE>
  38: </HEAD>
  39: 

  40: <BODY bgColor="#EBECF6" style="margin-left:10px">
------------------------------|||||

[CSE] Message number 6 for the tag beginning in line 40:25:
Use the inline "style" attribute sparingly. Using this
attribute too often can prevent you from receiving many of
the benefits of CSS like easier to maintain and less
cluttered documents. Consider using a single CSS style sheet
instead of relying too much on the "style" attribute. This
message is displayed only once.

  41: 
  42: <DIV id=leftpanel><P>&nbsp;</P></DIV>
  43: <DIV id=rightpanel><P>&nbsp;</P></DIV>
  44: <div id="content">
  45: <div style="margin: 0 13px">
  46: <br>

  47:   <h1 style="float:left"><span class="black">WIN</span>chester
--------------------------------||||

[CSE] Message number 7 for the tag beginning in line 47:27:
[5] The "span" element is an official HTML 4.01 and XHTML
element but is not supported by Internet Explorer 2.0-,
Netscape 3.0-, Opera versions prior to 3.5, and most older
browsers.

  48: <span class="black">B</span>usiness
  49: <span class="black">E</span>-<span class="black">L</span>earning
  50: Project<br>
  51: <span class="black">[WINBEL]</span><br>
  52: </h1>
  53: 
  54: <img src="mh555b.jpg" width="90" height="100" alt="Mike Hart" border="1" vspace="0" hspace="30" style="float:right" class="pad_right"/>
  55: 
  56: <br>

  57: <div class="update"><br clear="left">
------------------------------|||||

[CSE] Message number 8 for the tag beginning in line 57:25:
[9] The "clear" attribute is deprecated in HTML 4.01 and
XHTML in favor of using style sheets (use the CSS "clear"
property instead).

  58: <script type="text/javascript">
-------||||||

[CSE] Message number 9 for the tag beginning in line 58:2:
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.

  58: <script type="text/javascript">
-------||||||

[CSE] Message number 10 for the tag beginning in line 58:2:
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]

  58: <script type="text/javascript">
-------||||||

[CSE] Message number 11 for the tag beginning in line 58:2:
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)]

  58: <script type="text/javascript">
-------||||||

[CSE] Message number 12 for the tag beginning in line 58:2:
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.

  58: <script type="text/javascript">
-------||||||

[CSE] Message number 13 for the tag beginning in line 58:2:
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.

  59:   <!--
  60:   months = ['January', 'February', 'March', 'April', 'May', 'June', 'July', 'August', 'September', '  October', 'November', 'December'];
  61:   var theDate = new Date(document.lastModified);
  62:   theDate.setTime((theDate.getTime()+(0000*60*60)) );
  63:   am="am";
  64:   var mymins=theDate.getMinutes(); if (mymins < 10) mymins="0"+mymins;
  65:   var myhours=theDate.getHours();  if (myhours > 11) am="pm";
  66:   if (myhours >12) myhours=myhours-12;
  67:   if (myhours==0) myhours=12;
  68:   with (theDate) {
  69:   document.write("Last updated: "+getDate()+' '+months[getMonth()]+' '+getYear()+' at '+ myhours +
  70:   ':'+mymins+am)
  71:   }
  72: -->
  73:   </script>
  74: </div>
  75: <br clear="right">
  76:  <img src="mch_web.gif"  alt="Web Page: Mike Hart" width="156" height="20" style="float:right" border="1" vspace="8" />
  77: 
  78: <br>
  79: <br clear=all>
  80: <br>
  81: <br>
  82: </div>
  83: 

  84: <TABLE cellpadding="0">
-------|||||

[CSE] Message number 14 for the tag beginning in line 84:2:
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.

  84: <TABLE cellpadding="0">
-------|||||

[CSE] Message number 15 for the tag beginning in line 84:2:
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.

  84: <TABLE cellpadding="0">
-------|||||

[CSE] Message number 16 for the tag beginning in line 84:2:
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.

  84: <TABLE cellpadding="0">
-------|||||

[CSE] Message number 17 for the tag beginning in line 84:2:
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.

  84: <TABLE cellpadding="0">
-------|||||

[CSE] Message number 18 for the tag beginning in line 84:2:
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]

  84: <TABLE cellpadding="0">
-------|||||

[CSE] Message number 19 for the tag beginning in line 84: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.

  84: <TABLE cellpadding="0">
-------|||||

[CSE] Message number 20 for the tag beginning in line 84:2:
[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.

  85: <tr><td colspan="2" class="head_cell">What is WINBEL?</td></tr>
  86: <tr><td>
  87: <p>The WINBEL (WINchester Business E-Learning) project is a research programme which explores the opportunities to enhance business studies education through the application of e-learning technologies.
  88: A variety of approaches have already been addressed including critical examinations of the role of Virtual Learning Environments, the developments of communities of practice, the application of e-learning to work-based learning and the threats to e-learning posed by plagiarism.
  89: </p>
  90: </td></tr>
  91: <tr><td colspan="2" class="head_cell">Who are we?</td></tr>
  92: <tr><td>
  93: We are a group of business academic academics who work in (or are closely associated with) the <a href="http://winchester.ac.uk/bm">Business Management Group</a> at the newly designated <a href="http://winchester.ac.uk">University College, Winchester.</a> teaching on a range of foundation level, undergraduate and postgraduate degree level courses. Members of the team include:
  94: <ul style="margin-left:50px">
  95: <li>Professor Mike Hart [Coordinator]
  96: <li>Eric Bodger
  97: <li>Tim Friesner [University College, Chichester]
  98: <li>Roz Graham
  99: <li>Paul Haslam
 100: <li>Loykie Lominé
 101: <li>David Rush
 102: </ul>
 103: 
 104: </td></tr>
 105: <tr><td colspan="2" class="head_cell">Work published (or projected) to date:</td></tr>
 106: <tr><td>

 107: A document listing current research papers is available <a href="bel_pubs.html">here</a>. All papers are downloadable. The list includes:
--------------------------------------------------------------------------------------||||

[CSE] Error number 1 in line 107:81:
A link should be more descriptive than simply "here". Using
"here" for a link description may cause accessibility
problems. For example, visually impaired users often view a
list of links contained on a page, and links named "click
here" are not useful (imagine viewing a list of links
contained on a page, and there are 10 different links named
"click here", with no other descriptive information).
Furthermore, this may be considered to be bad style.

 108: <ul style="margin-left:50px">
 109: <li>Ten full papers
 110: <li>Four abstracts of papers accepted for forthcoming conferences [November, 2004].
 111: <li>A book chapter commissioned by the Indira Gandhi National Open University, India.
 112: </ul>
 113: </td></tr>
 114: </TABLE>
 115: <br clear=all>

 116: <p>Email enquiries to: <a href="mailto:info@uwin.co.uk">info@uwin.org.uk</a></p>
--------------------------------------||||||||||||||||||||||

[CSE] Message number 21 for the tag beginning in line
116:33:
[6] Email spam is a huge problem nowadays. Be aware that
mailto email addresses are easily harvested for spam lists
by automated programs. You may want to consider alternate,
but less user-friendly, ways of distributing email addresses
if spam is a concern.

 117: <p class="update">mch</p>
 118: 
 119: </div>
 120: </BODY>
 121: </HTML>
 122: 
 123: 

[CSE] Comment number 1:
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.

[CSE] Comment number 2:
HTML 4.01 Transitional document detected.

[CSE] Comment number 3:
[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 and/or from the Tag
Inserter.

[CSE] Comment number 4:
[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 and/or from the Tag Inserter.

[CSE] Comment number 5:
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]

[CSE] Comment number 6:
The "a" element was used 4 times but not one "a" element
contained an "accesskey" attribute. Be sure to provide
keyboard shortcuts for any important links [P3, 9.5].

[CSE] Comment number 7:
An ICRA label (a rating "meta" tag) 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. If you have labelled this document by
rating the section (directory) in which it is found, or if
your site is a personal web space on a large Internet
Service Provider, it is still recommended that you include
the rating "meta" tag on all of your pages for performance
reasons. For more information, please visit
http://www.icra.org/.

[CSE] Comment number 8:
Although not normally necessary, you may want to include a
"meta" tag similar to the following in the "head" section of
your document: <meta http-equiv="Content-Type"
content="text/html; charset=us-ascii">

[CSE] Comment number 9:
[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.

[CSE] Comment number 10:
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.

[CSE] Comment number 11:
4462 bytes; 3.1s@14.4Kbps, 1.5s@28.8, 0.9s@50, 0.7s@64,
0.3s@128, 0.1s@384, 0.1s@512, 0.1s@768, 0.0s@1.5Mbps,
0.0s@10Mbps.

[CSE] Comment number 12:
0.83s, 1 error, 0 warnings, 21 messages, 12 validator
comments, 123 lines, 65 tags (41 closed), 0 document
comments, 2 entities, 162 programs run.

--------------------------------------------------

<HTML> (2) 
| <HEAD> (3) 
| | <TITLE> (3) 
| | </TITLE> (3) 
| | <META> (4) 
| | <STYLE> (5) 
| | </STYLE> (37) 
| </HEAD> (38) 
| <BODY> (40) 
| | <DIV> (42) 
| | | <P> (42) 
| | | | &nbsp; (42) 
| | | </P> (42) 
| | </DIV> (42) 
| | <DIV> (43) 
| | | <P> (43) 
| | | | &nbsp; (43) 
| | | </P> (43) 
| | </DIV> (43) 
| | <div> (44) 
| | | <div> (45) 
| | | | <br> (46) 
| | | | <h1> (47) 
| | | | | <span> (47) 
| | | | | </span> (47) 
| | | | | <span> (48) 
| | | | | </span> (48) 
| | | | | <span> (49) 
| | | | | </span> (49) 
| | | | | <span> (49) 
| | | | | </span> (49) 
| | | | | <br> (50) 
| | | | | <span> (51) 
| | | | | </span> (51) 
| | | | | <br> (51) 
| | | | </h1> (52) 
| | | | <img/> (54) <br> (56) 
| | | | <div> (57) 
| | | | | <br> (57) 
| | | | | <script> (58) 
| | | | | </script> (73) 
| | | | </div> (74) 
| | | | <br> (75) <img/> (76) <br> (78) <br> (79) <br> (80) <br> (81) 
| | | </div> (82) 
| | | <TABLE> (84) 
| | | | <tr> (85) 
| | | | | <td> (85) 
| | | | | </td> (85) 
| | | | </tr> (85) 
| | | | <tr> (86) 
| | | | | <td> (86) 
| | | | | | <p> (87) 
| | | | | | </p> (89) 
| | | | | </td> (90) 
| | | | </tr> (90) 
| | | | <tr> (91) 
| | | | | <td> (91) 
| | | | | </td> (91) 
| | | | </tr> (91) 
| | | | <tr> (92) 
| | | | | <td> (92) 
| | | | | | <a> (93) 
| | | | | | </a> (93) 
| | | | | | <a> (93) 
| | | | | | </a> (93) 
| | | | | | <ul> (94) 
| | | | | | | <li> (95) <li> (96) <li> (97) <li> (98) <li> (99) <li> (100) <li> (101) 
| | | | | | </ul> (102) 
| | | | | </td> (104) 
| | | | </tr> (104) 
| | | | <tr> (105) 
| | | | | <td> (105) 
| | | | | </td> (105) 
| | | | </tr> (105) 
| | | | <tr> (106) 
| | | | | <td> (106) 
| | | | | | <a> (107) 
| | | | | | </a> (107) 
| | | | | | <ul> (108) 
| | | | | | | <li> (109) <li> (110) <li> (111) 
| | | | | | </ul> (112) 
| | | | | </td> (113) 
| | | | </tr> (113) 
| | | </TABLE> (114) 
| | | <br> (115) 
| | | <p> (116) 
| | | | <a> (116) 
| | | | </a> (116) 
| | | </p> (116) 
| | | <p> (117) 
| | | </p> (117) 
| | </div> (119) 
| </BODY> (120) 
</HTML> (121) 

