Markup Validation Service

Validation Output: 4 Errors

1. Line 111, Column 19: there is no attribute "WIDTH"

           <td width="70%"><A href="/imaging"><IMG src="http://imaging.mrc-cbu.cam…

   ✉

   You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

   This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

   How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

2. Line 111, Column 115: unclosed start-tag requires SHORTTAG YES

   …IMG src="http://imaging.mrc-cbu.cam.ac.uk/images/cbu_imaging_logo.png"</A></td>

   ✉

   The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

3. Line 111, Column 115: required attribute "ALT" not specified

   …IMG src="http://imaging.mrc-cbu.cam.ac.uk/images/cbu_imaging_logo.png"</A></td>

   ✉

   The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

   Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

4. Line 112, Column 116: unclosed start-tag requires SHORTTAG YES

   …c.uk/"><IMG SRC="http://imaging.mrc-cbu.cam.ac.uk/images/MRC-logo.gif"</a></td>

   ✉

   The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

5. Line 112, Column 116: required attribute "ALT" not specified

   …c.uk/"><IMG SRC="http://imaging.mrc-cbu.cam.ac.uk/images/MRC-logo.gif"</a></td>

   ✉

   The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

   Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

6. Line 120, Column 142: NET-enabling start-tag requires SHORTTAG YES

   …2" src="/wiki/cbuimaging/img/moin-edit.png" title="Edit" width="12" /></a></li>

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

7. Line 121, Column 130: NET-enabling start-tag requires SHORTTAG YES

   …3" src="/wiki/cbuimaging/img/moin-show.png" title="View" width="12" /></a></li>

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

8. Line 122, Column 144: NET-enabling start-tag requires SHORTTAG YES

   …" src="/wiki/cbuimaging/img/moin-diff.png" title="Diffs" width="15" /></a></li>

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

9. Line 123, Column 142: NET-enabling start-tag requires SHORTTAG YES

   …1" src="/wiki/cbuimaging/img/moin-info.png" title="Info" width="12" /></a></li>

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

10. Line 124, Column 162: NET-enabling start-tag requires SHORTTAG YES

    …iki/cbuimaging/img/moin-subscribe.png" title="Subscribe" width="14" /></a></li>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

11. Line 125, Column 138: NET-enabling start-tag requires SHORTTAG YES

    …"13" src="/wiki/cbuimaging/img/moin-raw.png" title="Raw" width="12" /></a></li>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

12. Line 126, Column 146: NET-enabling start-tag requires SHORTTAG YES

    … src="/wiki/cbuimaging/img/moin-print.png" title="Print" width="16" /></a></li>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

13. Line 236, Column 6573: NET-enabling start-tag requires SHORTTAG YES

    …ages/mnitalcor.jpg" title="mnitalcor" /> <span class="anchor" id="line-23"></s…

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

14. Line 263, Column 10: ID "PAGEBOTTOM" already defined

    <div id="pagebottom"></div>

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

15. Line 260, Column 1642: ID "PAGEBOTTOM" first defined here

    …/span><span class="anchor" id="bottom"></span></div><div id="pagebottom"></div>

↑ Top