ESOK-hanke 2006-2011

Foxability - Test results

Test results

Test results

Test subject: http://www.lut.fi/fi/index.html

Statistics for the evaluated page

Total tests: 64

TestsPercentTotalPercent
Total passed:4570.31%4511.60%
-Passed with remarks:2132.81%4812.37%
Failed:1421.88%27169.85%
Warnings:57.81%246.19%
Total:64100.00%388100.00%

WCAG1.0

Guideline 1

(show module information)

1.1 - Elements have text equivalents. (45)

(hide test results)
  1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="JavaScript" type="text/javascript"> <!-- // -------------------------------------- .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  2. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="VBScript" type="text/vbscript"> <!-- // Visual basic helper required to detect Fla .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  3. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="JavaScript1.1" type="text/javascript"> <!-- // Detect Client Browser type var isIE .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  4. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- function MenuOver (tdObj, buttonNro) { if (!document.getElemen .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  5. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/Scripts/AC_RunActiveContent.js" type="text/javascript"></script> .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  6. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/Scripts/AC_OETags.js" type="text/javascript"></script> .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  7. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/pic05.jpg" alt="" height="176" width="51"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  8. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/pic01.jpg" alt="" height="96" width="172"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  9. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/pic02.jpg" alt="" height="96" width="88"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  10. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/pic03.jpg" alt="" height="96" width="256"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  11. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/1x11pixel.gif" alt="" height="11" width="1"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  12. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/bg04.gif" alt="" height="20" width="1"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  13. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/1x1pixel.gif" alt="" height="1" width="5"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  14. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/1x1pixel.gif" alt="" height="1" width="5"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  15. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> var hasReqestedVersion = DetectFlashVer (8, 0, 0); if (hasReqested .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  16. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/687x1pixel.gif" alt="" height="1" width="687"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  17. Failed, alt attribute not found. Error was found from IMG element code: <img src="/hakuopas/images/lut_energia_banneri_3.jpg" border="0" hspace="2"> .
    • Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
  18. Failed, alt attribute is empty. Error was found from IMG element code: <img id="menuItem1" src="/lut_images/main2/menuItem01.jpg" style="border: 0px none ;" alt="" height= .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  19. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/promootiolinkki_off.gif" alt="" name="Promootio" style="border: 0px none ;" bo .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  20. Failed, alt attribute is empty. Error was found from IMG element code: <img id="menuItem2" src="/lut_images/main2/menuItem02.jpg" style="border: 0px none ;" alt="" height= .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  21. Failed, alt attribute is empty. Error was found from IMG element code: <img id="menuItem3" src="/lut_images/main2/menuItem03.jpg" style="border: 0px none ;" alt="" height= .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  22. Failed, alt attribute is empty. Error was found from IMG element code: <img id="menuItem4" src="/lut_images/main2/menuItem04.jpg" style="border: 0px none ;" alt="" height= .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  23. Failed, alt attribute is empty. Error was found from IMG element code: <img id="menuItem5" src="/lut_images/main2/menuItem05.jpg" style="border: 0px none ;" alt="" height= .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  24. Failed, alt attribute is empty. Error was found from IMG element code: <img id="menuItem8" src="/lut_images/main2/menuItem08.jpg" style="border: 0px none ;" alt="" height= .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  25. Failed, alt attribute may not consist completely out of whitespaces. Error was found from IMG element code: <img src="/lut_images/main2/title_news.jpg" alt=" " height="37" width="258"> .
    • Insert descriptive text alternative. For example: alt="Some fava beans and a nice chianti."
  26. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/table_bottom.jpg" alt="" height="28" width="258"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  27. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/title_press.jpg" alt="" height="37" width="258"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  28. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/table_bottom.jpg" alt="" height="28" width="258"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  29. Failed, alt attribute not found. Error was found from IMG element code: <img src="/lut_images/main2/nuoli2.gif" height="12" width="10"> .
    • Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
  30. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/title_events.jpg" alt="" height="37" width="258"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  31. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/line.gif" alt="" height="1" width="246"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  32. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/line.gif" alt="" height="1" width="246"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  33. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/line.gif" alt="" height="1" width="246"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  34. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/line.gif" alt="" height="1" width="246"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  35. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/line.gif" alt="" height="1" width="246"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  36. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/table_bottom.jpg" alt="" height="28" width="258"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  37. Failed, alt attribute not found. Error was found from IMG element code: <img src="/lut_images/main2/nuoli2.gif" height="12" width="10"> .
    • Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
  38. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/tunnustusta_image.jpg" alt="" height="37" width="258"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  39. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/main2/table_bottom.jpg" alt="" height="28" width="258"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  40. Failed, alt attribute not found. Error was found from IMG element code: <img src="/lut_images/main2/nuoli2.gif" height="12" width="10"> .
    • Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
  41. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/palkki2.gif" alt="" height="1" width="3"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  42. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/lty_logo.gif" style="border-width: 0px;" alt="" height="62" width="193"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  43. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/lut_images/palkki.gif" alt="" height="5" width="2"> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  44. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="http://eu1.snoobi.com/snoop.php?tili=lut_fi"></script> .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  45. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="http://eu1.snoobi.com/snoop2.php?tili=lut_fi&amp;page_name=&amp; .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
Test result
Failed

1.2 - A serverside Image map without an alternative textlink

    Test result
    Passed

    1.3 - Auditory descriptions for visual tracks.

    (hide test results)
    1. Remark, until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
    Test result
    Passed

    1.4 - Equivalent alternatives for time based multimedia.

    (hide test results)
    1. Remark, for any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.
    Test result
    Passed

    1.5 - Client-side image map links need to have text equivalents

      Test result
      Passed

      Guideline 2

      (show module information)

      2.1 - Information is conveyed even without colors.

      (hide test results)
      1. Remark, ensure that all information conveyed with color is also available without color, for example from context or markup.
      Test result
      Passed

      2.2 - Colors are visible. (3)

      (hide test results)
      1. Failed, the color difference of rgb(0, 0, 0) and rgb(156, 63, 93) is too low. Error was found from TD element code: <td style="width: 111px; background-image: url(/lut_images/main2/pic06.jpg); background-color: rgb(1 .
        • Change the colors so that they have higher color difference.
      2. Failed, the brightness difference of rgb(0, 0, 0) and rgb(156, 63, 93) is too low. Error was found from TD element code: <td style="width: 111px; background-image: url(/lut_images/main2/pic06.jpg); background-color: rgb(1 .
        • Change the colors so that they have higher brightness difference.
      3. Failed, the color difference of rgb(0, 0, 0) and rgb(255, 102, 0) is too low. Error was found from TD element code: <td style="background-image: url(/lut_images/main2/pic07.jpg);" align="left" bgcolor="#ff6600" valig .
        • Change the colors so that they have higher color difference.
      Test result
      Failed

      Guideline 3

      (show module information)

      3.1 - MathML

        Test result
        Passed

        3.2 - Formal grammars.

        (hide test results)
        1. Failed, proper DTD URL not found. Error was found from HTML element code: <html><head><title>Lappeenrannan teknillinen yliopisto</title> <meta http-equiv="Content-Type" co .
          • Try: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd" >
        Test result
        Failed

        3.3 - Proper font stylings. (18)

        (hide test results)
        1. Failed, deprecated element found. Error was found from FONT element code: <font color="#ffffff">OPISKELU</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        2. Failed, deprecated element found. Error was found from FONT element code: <font color="#ffffff">TUTKIMUS</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        3. Failed, deprecated element found. Error was found from FONT element code: <font color="#ffffff">PALVELUT</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        4. Failed, deprecated element found. Error was found from FONT element code: <font color="#ffffff">YLIOPISTO LYHYESTI</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        5. Failed, deprecated element found. Error was found from FONT element code: <font color="#ffffff">YKSIKÖT</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        6. Failed, deprecated element found. Error was found from FONT element code: <font color="#ffffff">LINKIT</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        7. Failed, deprecated element found. Error was found from FONT element code: <font color="#ffffff">in English</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        8. Failed, deprecated element found. Error was found from FONT element code: <font color="#ffffff">Sivukartta</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        9. Failed, deprecated element found. Error was found from FONT element code: <font color="#ffffff">Palaute</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        10. Failed, deprecated element found. Error was found from FONT element code: <font color="#ffffff">Henkilökunnalle</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        11. Failed, deprecated element found. Error was found from B element code: <b><a href="/php/EventCal.php?lang=FIN&amp;id=553">5.5.2008 klo 18:00</a></b> .
          • You will achieve much richer effect using stylesheets or you can use <strong> instead of <b>. CSS example: strong { font-weight: bolder; }
        12. Failed, deprecated element found. Error was found from B element code: <b><a href="/php/EventCal.php?lang=FIN&amp;id=363">16.5.2008</a></b> .
          • You will achieve much richer effect using stylesheets or you can use <strong> instead of <b>. CSS example: strong { font-weight: bolder; }
        13. Failed, deprecated element found. Error was found from B element code: <b><a href="/php/EventCal.php?lang=FIN&amp;id=548">23.5.2008 klo 12:00</a></b> .
          • You will achieve much richer effect using stylesheets or you can use <strong> instead of <b>. CSS example: strong { font-weight: bolder; }
        14. Failed, deprecated element found. Error was found from B element code: <b><a href="/php/EventCal.php?lang=FIN&amp;id=436">30.5.2008 klo 15:00</a></b> .
          • You will achieve much richer effect using stylesheets or you can use <strong> instead of <b>. CSS example: strong { font-weight: bolder; }
        15. Failed, deprecated element found. Error was found from B element code: <b><a href="/php/EventCal.php?lang=FIN&amp;id=552">3.6. - 4.6. 2008</a></b> .
          • You will achieve much richer effect using stylesheets or you can use <strong> instead of <b>. CSS example: strong { font-weight: bolder; }
        16. Failed, deprecated element found. Error was found from FONT element code: <font class="smalltext" size="2">NORDI:n vuosittainen seminaari </font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        17. Failed, deprecated element found. Error was found from FONT element code: <font color="#cccccc">W3C:n HTML-standardi (HTML 4, CSS 2), Selaimet: MSIE 5+, Netscape 6+, Opera 5+ .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        18. Failed, deprecated element found. Error was found from FONT element code: <font color="#cccccc">Content Bakery Oy</font> .
          • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
        Test result
        Failed

        3.4 - Relative over absolute. (60)

        (hide test results)
        1. Failed, absolute size definition found. td:"font-size: 10pt". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        2. Failed, absolute size definition found. .smalltext_error:"font-size: 8pt". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        3. Failed, absolute size definition found. .newsbg:"font-size: 10px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        4. Failed, absolute size definition found. .frontpage_lmenu:"width: 180px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        5. Failed, absolute size definition found. .frontpage_lmenu:"padding-left: 21px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        6. Failed, absolute size definition found. .frontpage_lmenu2:"width: 150px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        7. Failed, absolute size definition found. .frontpage_lmenu2:"padding-left: 40px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        8. Failed, absolute size definition found. .frontpage_bg:"width: 23px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        9. Failed, absolute size definition found. .frontpage_content:"padding-left: 15px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        10. Failed, absolute size definition found. .frontpage_content:"padding-right: 13px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        11. Failed, absolute size definition found. .frontpage_content2:"padding-left: 15px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        12. Failed, absolute size definition found. .frontpage_content2:"padding-right: 15px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        13. Failed, absolute size definition found. .frontpage_content3:"padding-left: 19px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        14. Failed, absolute size definition found. .frontpage_content3:"padding-right: 15px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        15. Failed, absolute size definition found. .frontpage_events:"border-left: 6px none". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        16. Failed, absolute size definition found. .frontpage_events:"padding-left: 6px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        17. Failed, absolute size definition found. .frontpage_events:"padding-right: 6px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        18. Failed, absolute size definition found. .frontpage_event_text:"padding: 6px 9px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        19. Failed, absolute size definition found. .frontpage_event_text:"font-size: 10px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        20. Failed, absolute size definition found. .frontpage_news td:"font-size: 10px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        21. Failed, absolute size definition found. .frontpage_news td.data:"padding-top: 7px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        22. Failed, absolute size definition found. .frontpage_news td.data:"padding-bottom: 5px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        23. Failed, absolute size definition found. .frontpage_news td.img:"padding-top: 5px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        24. Failed, absolute size definition found. .matemfysiikkaotsikko:"font-size: 12pt". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        25. Failed, absolute size definition found. @media screen:".left_menu_table { width: 150px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        26. Failed, absolute size definition found. @media screen:"font-size: 10px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        27. Failed, absolute size definition found. @media screen:"font-size: 10px". Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        28. Failed, absolute size definition found. td:"width: 111px". Error was found from TD element code: <td style="width: 111px; background-image: url(/lut_images/main2/pic06.jpg); background-color: rgb(1 .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        29. Failed, absolute size definition found. select:"font-size: 10px". Error was found from SELECT element code: <select name="redirect" style="font-family: Verdana,Arial,Helvetica; font-style: normal; font-varian .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        30. Failed, absolute size definition found. select:"height: 18px". Error was found from SELECT element code: <select name="redirect" style="font-family: Verdana,Arial,Helvetica; font-style: normal; font-varian .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        31. Failed, absolute size definition found. select:"width: 140px". Error was found from SELECT element code: <select name="redirect" style="font-family: Verdana,Arial,Helvetica; font-style: normal; font-varian .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        32. Failed, absolute size definition found. td:"padding-left: 20px". Error was found from TD element code: <td class="otsikko" style="padding-left: 20px; font-size: 18px;" width="100%">Lappeenrannan teknilli .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        33. Failed, absolute size definition found. td:"font-size: 18px". Error was found from TD element code: <td class="otsikko" style="padding-left: 20px; font-size: 18px;" width="100%">Lappeenrannan teknilli .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        34. Failed, absolute size definition found. a:"left: 735px ! important". Error was found from a element code: <a style="left: 735px ! important; top: 0px ! important;" title="Click here to block this object wit .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        35. Failed, absolute size definition found. td:"padding-top: 14px". Error was found from TD element code: <td style="padding-top: 14px;"><a href="http://www.lut.fi/promootio/index.html" onmouseout="MM_swapI .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        36. Failed, absolute size definition found. td:"padding-top: 14px". Error was found from TD element code: <td style="padding-top: 14px;"><a href="http://www.lut.fi/fi/kirjasto/index.html" onmouseover="retur .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        37. Failed, absolute size definition found. td:"padding-top: 14px". Error was found from TD element code: <td style="padding-top: 14px;"><a href="http://www.lut.fi/fi/opiskelu/nykyiset_opiskelijat/weboodi.h .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        38. Failed, absolute size definition found. td:"padding-top: 14px". Error was found from TD element code: <td style="padding-top: 14px;"><a href="http://www.lut.fi/fi/oppimiskeskus/opetusteknologiapalvelut/ .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        39. Failed, absolute size definition found. td:"padding-top: 14px". Error was found from TD element code: <td style="padding-top: 14px;"><a href="https://webmail.lut.fi/" onmouseover="return MenuOver (this, .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        40. Failed, absolute size definition found. td:"padding-top: 14px". Error was found from TD element code: <td style="padding-top: 14px;"><a href="http://www.lut.fi/fi/oppimiskeskus/fuksipussi/index.html" on .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        41. Failed, absolute size definition found. table:"width: 258px". Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        42. Failed, absolute size definition found. table:"width: 258px". Error was found from TABLE element code: <table style="border-width: 0px; width: 258px;" cellpadding="0" cellspacing="0"> <tbody><tr> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        43. Failed, absolute size definition found. span:"line-height: 14px". Error was found from SPAN element code: <span class="smalltext" style="color: rgb(80, 57, 136); line-height: 14px;"><strong>30.04.2008</stro .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        44. Failed, absolute size definition found. td:"height: 8px". Error was found from TD element code: <td class="frontpage_content2" style="height: 8px;"></td> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        45. Failed, absolute size definition found. span:"line-height: 14px". Error was found from SPAN element code: <span class="smalltext" style="color: rgb(80, 57, 136); line-height: 14px;"><strong>29.04.2008</stro .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        46. Failed, absolute size definition found. td:"height: 8px". Error was found from TD element code: <td class="frontpage_content2" style="height: 8px;"></td> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        47. Failed, absolute size definition found. span:"line-height: 14px". Error was found from SPAN element code: <span class="smalltext" style="color: rgb(80, 57, 136); line-height: 14px;"><strong>24.04.2008</stro .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        48. Failed, absolute size definition found. td:"height: 8px". Error was found from TD element code: <td class="frontpage_content2" style="height: 8px;"></td> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        49. Failed, absolute size definition found. span:"line-height: 14px". Error was found from SPAN element code: <span class="smalltext" style="color: rgb(80, 57, 136); line-height: 14px;"><strong>24.04.2008</stro .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        50. Failed, absolute size definition found. td:"height: 8px". Error was found from TD element code: <td class="frontpage_content2" style="height: 8px;"></td> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        51. Failed, absolute size definition found. span:"line-height: 14px". Error was found from SPAN element code: <span class="smalltext" style="color: rgb(80, 57, 136); line-height: 14px;"><strong>24.04.2008</stro .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        52. Failed, absolute size definition found. td:"height: 8px". Error was found from TD element code: <td class="frontpage_content2" style="height: 8px;"></td> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        53. Failed, absolute size definition found. span:"line-height: 14px". Error was found from SPAN element code: <span class="smalltext" style="color: rgb(80, 57, 136); line-height: 14px;"><strong>03.03.2008</stro .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        54. Failed, absolute size definition found. td:"height: 8px". Error was found from TD element code: <td class="frontpage_content2" style="height: 8px;"></td> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        55. Failed, absolute size definition found. table:"width: 258px". Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        56. Failed, absolute size definition found. table:"width: 258px". Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        57. Failed, absolute size definition found. span:"line-height: 14px". Error was found from SPAN element code: <span class="smalltext" style="color: rgb(80, 57, 136); line-height: 14px;"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        58. Failed, absolute size definition found. td:"height: 8px". Error was found from TD element code: <td class="frontpage_content3" style="height: 8px;"></td> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        59. Failed, absolute size definition found. span:"line-height: 14px". Error was found from SPAN element code: <span class="smalltext" style="color: rgb(80, 57, 136); line-height: 14px;"> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        60. Failed, absolute size definition found. td:"height: 8px". Error was found from TD element code: <td class="frontpage_content3" style="height: 8px;"></td> .
          • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
        Test result
        Failed

        3.5 - Proper header usage.

          Test result
          Passed

          3.6 - Proper List usage.

            Test result
            Passed

            3.7 - Proper quote usage.

            (hide test results)
            1. Remark, the number of quotation marks found: 74 Error was found from BODY element code: <body onload="MM_preloadImages('/lut_images/promootiolinkki_on.gif')" lang="fi"> <table style="borde .
              • Please consider using <q> and <blockquote> for quotes.
            Test result
            Passed

            Guideline 4

            (show module information)

            4.1 - Language changes are identified.

            (hide test results)
            1. Remark, if multiple languages are used in the document, clearly identify changes in the natural language of the document's text.
              • Use the "lang" or "xml:lang" attribute to identify any changes in language. For example: Galileo said quietly: <q lang="it">Eppur si muove</q>
            Test result
            Passed

            4.2 - Acronyms and abbreviations. (19)

            (hide test results)
            1. Warning, potential abbreviation found: ATK. Error was found from OPTION element code: <option value="/fi/tietohallinto/index.html">ATK</option> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            2. Warning, potential abbreviation found: OPISKELU. Error was found from FONT element code: <font color="#ffffff">OPISKELU</font> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            3. Warning, potential abbreviation found: TUTKIMUS. Error was found from FONT element code: <font color="#ffffff">TUTKIMUS</font> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            4. Warning, potential abbreviation found: PALVELUT. Error was found from FONT element code: <font color="#ffffff">PALVELUT</font> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            5. Warning, potential abbreviation found: YLIOPISTO. Error was found from FONT element code: <font color="#ffffff">YLIOPISTO LYHYESTI</font> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            6. Warning, potential abbreviation found: LYHYESTI. Error was found from FONT element code: <font color="#ffffff">YLIOPISTO LYHYESTI</font> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            7. Warning, potential abbreviation found: YKSIKÖT. Error was found from FONT element code: <font color="#ffffff">YKSIKÖT</font> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            8. Warning, potential abbreviation found: LINKIT. Error was found from FONT element code: <font color="#ffffff">LINKIT</font> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            9. Warning, potential abbreviation found: KTT. Error was found from A element code: <a href="/php/GetBulletin.php?lang=fi&amp;date=1209534360&amp;category=Frontpage">Tukisäätiön kuudes .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            10. Warning, potential abbreviation found: LTY. Error was found from A element code: <a href="/php/GetBulletin.php?lang=fi&amp;date=1209035940&amp;category=Frontpage">LTY:n Kouvolan yks .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            11. Warning, potential abbreviation found: LTY. Error was found from A element code: <a href="/php/GetBulletin.php?lang=fi&amp;date=1209018720&amp;category=Frontpage">LTY:lle professuur .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            12. Warning, potential abbreviation found: LTY. Error was found from A element code: <a href="/php/GetBulletin.php?lang=fi&amp;date=1209018600&amp;category=Frontpage">LTY:n Kouvolan yks .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            13. Warning, potential abbreviation found: MAG. Error was found from P element code: <p> Diplomi-insinööri Anna Fellmanin (teknillinen tiedekunta, konetekniikan osasto) väitöskirja The .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            14. Warning, potential abbreviation found: NORDI. Error was found from FONT element code: <font class="smalltext" size="2">NORDI:n vuosittainen seminaari </font> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            15. Warning, potential abbreviation found: LTY. Error was found from A element code: <a href="/php/GetBulletin.php?lang=fi&amp;date=1200043560&amp;category=Tunnustusta">LTY:n professori .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            16. Warning, potential abbreviation found: LAPPEENRANTA. Error was found from TD element code: <td class="osoitteet" width="18%">Postiosoite:<br>PL 20 <br>53851 LAPPEENRANTA</td> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            17. Warning, potential abbreviation found: HTML. Error was found from FONT element code: <font color="#cccccc">W3C:n HTML-standardi (HTML 4, CSS 2), Selaimet: MSIE 5+, Netscape 6+, Opera 5+ .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            18. Warning, potential abbreviation found: CSS. Error was found from FONT element code: <font color="#cccccc">W3C:n HTML-standardi (HTML 4, CSS 2), Selaimet: MSIE 5+, Netscape 6+, Opera 5+ .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            19. Warning, potential abbreviation found: MSIE. Error was found from FONT element code: <font color="#cccccc">W3C:n HTML-standardi (HTML 4, CSS 2), Selaimet: MSIE 5+, Netscape 6+, Opera 5+ .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            Test result
            Warning

            4.3 - Primary language.

            (hide test results)
            1. Failed, no lang attribute found. Error was found from HTML element code: <html><head><title>Lappeenrannan teknillinen yliopisto</title> <meta http-equiv="Content-Type" co .
              • Insert lang attribute to specify language used. For example: <html lang="fi">
            Test result
            Failed

            Guideline 5

            (show module information)

            5.1 - Table used properly

              Test result
              Passed

              5.2 - Associate data cells and header cells

              (hide test results)
              1. Remark, for data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-structure.
              Test result
              Passed

              5.3 - Table is used as layout

                Test result
                Passed

                5.5 - Summary, caption and title in table (19)

                (hide test results)
                1. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px; width: 100%; height: 100%;" cellpadding="0" cellspacing="0"> <tbo .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                2. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="742"> <tbody><tr> .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                3. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                4. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table cellpadding="0" cellspacing="0"> <tbody><tr> <td al .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                5. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table class="leipis" cellpadding="0" cellspacing="0" width="100%"> <tbo .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                6. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                7. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="3" cellspacing="3" width="100%"> <tbody .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                8. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="6" cellspacing="6" width="100%"> <tbody .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                9. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                10. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table border="0" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                11. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                12. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table align="center" border="0" width="100%"> <tbody><tr> <td> <p> <span class="smalltext"><a href= .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                13. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px; width: 258px;" cellpadding="0" cellspacing="0"> <tbody><tr> .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                14. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                15. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                16. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table border="0" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                17. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="4" cellspacing="4" width="100%"> <tbody><tr> .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                18. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                19. Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="4" cellspacing="4" width="100%"> <tbody><tr> .
                  • Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                Test result
                Failed

                5.6 - Abbr used in long table headers names

                  Test result
                  Passed

                  Guideline 6

                  (show module information)

                  6.1 - Organize documents so they may be read without style sheets

                  (hide test results)
                  1. Remark, 72 deprecated elements were found. Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
                    • Ensure this document can be read without any styles or style sheets.
                  Test result
                  Passed

                  6.2 - Ensure that equivalents for dynamic content are updated when the dynamic content changes (9)

                  (hide test results)
                  1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="JavaScript" type="text/javascript"> <!-- // -------------------------------------- .
                    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                  2. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="VBScript" type="text/vbscript"> <!-- // Visual basic helper required to detect Fla .
                    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                  3. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="JavaScript1.1" type="text/javascript"> <!-- // Detect Client Browser type var isIE .
                    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                  4. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- function MenuOver (tdObj, buttonNro) { if (!document.getElemen .
                    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                  5. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/Scripts/AC_RunActiveContent.js" type="text/javascript"></script> .
                    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                  6. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/Scripts/AC_OETags.js" type="text/javascript"></script> .
                    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                  7. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> var hasReqestedVersion = DetectFlashVer (8, 0, 0); if (hasReqested .
                    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                  8. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="http://eu1.snoobi.com/snoop.php?tili=lut_fi"></script> .
                    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                  9. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="http://eu1.snoobi.com/snoop2.php?tili=lut_fi&amp;page_name=&amp; .
                    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                  Test result
                  Failed

                  6.3 - Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported (2)

                  (hide test results)
                  1. Failed, src attribute did not contain reachable URI. Error was found from EMBED element code: <embed src="/hakuopas/images/flash/virtuaalikampus_banneri.swf" quality="high" pluginspage="http://w .
                    • Insert valid URI for src attribute.
                  2. Failed, <noembed> not found. Error was found from EMBED element code: <embed src="/hakuopas/images/flash/virtuaalikampus_banneri.swf" quality="high" pluginspage="http://w .
                    • Please insert <noembed> after <embed>.
                  Test result
                  Failed

                  6.4 - For scripts and applets, ensure that event handlers are input device-independent (40)

                  (hide test results)
                  1. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  2. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  3. Failed, found device independent event handler. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  4. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  5. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  6. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  7. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  8. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  9. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/hakuopas/" onmouseover="return MenuOver (this, 1);" onmouseout="return Me .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  10. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/promootio/index.html" onmouseout="MM_swapImgRestore()" onmouseover="MM_sw .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  11. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/fi/kirjasto/index.html" onmouseover="return MenuOver (this, 2);" onmouseo .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  12. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/fi/opiskelu/nykyiset_opiskelijat/weboodi.html" onmouseover="return MenuOv .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  13. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/fi/oppimiskeskus/opetusteknologiapalvelut/webct6.html" onmouseover="retur .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  14. Failed, found device independent event handler. Error was found from A element code: <a href="https://webmail.lut.fi/" onmouseover="return MenuOver (this, 5);" onmouseout="return MenuOu .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  15. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/fi/oppimiskeskus/fuksipussi/index.html" onmouseover="return MenuOver (thi .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  16. Failed, found device independent event handler. Error was found from TD element code: <td style="background: rgb(229, 229, 229) none repeat scroll 0%; -moz-background-clip: -moz-initial; .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  17. Failed, found device independent event handler. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  18. Failed, found device independent event handler. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  19. Failed, found device independent event handler. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  20. Failed, found device independent event handler. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                    • If you use onmouseover, provide also redundant event handler: onfocus.
                  21. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  22. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  23. Failed, found device independent event handler. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  24. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  25. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  26. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  27. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  28. Failed, found device independent event handler. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  29. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/hakuopas/" onmouseover="return MenuOver (this, 1);" onmouseout="return Me .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  30. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/promootio/index.html" onmouseout="MM_swapImgRestore()" onmouseover="MM_sw .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  31. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/fi/kirjasto/index.html" onmouseover="return MenuOver (this, 2);" onmouseo .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  32. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/fi/opiskelu/nykyiset_opiskelijat/weboodi.html" onmouseover="return MenuOv .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  33. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/fi/oppimiskeskus/opetusteknologiapalvelut/webct6.html" onmouseover="retur .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  34. Failed, found device independent event handler. Error was found from A element code: <a href="https://webmail.lut.fi/" onmouseover="return MenuOver (this, 5);" onmouseout="return MenuOu .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  35. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.lut.fi/fi/oppimiskeskus/fuksipussi/index.html" onmouseover="return MenuOver (thi .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  36. Failed, found device independent event handler. Error was found from TD element code: <td style="background: rgb(229, 229, 229) none repeat scroll 0%; -moz-background-clip: -moz-initial; .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  37. Failed, found device independent event handler. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  38. Failed, found device independent event handler. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  39. Failed, found device independent event handler. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  40. Failed, found device independent event handler. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                    • If you use onmouseout, provide also redundant event handler: onblur.
                  Test result
                  Failed

                  6.5 - Ensure that dynamic content is accessible or provide an alternative presentation or page

                    Test result
                    Passed

                    Guideline 7

                    (show module information)

                    7.1 - Avoid causing the screen to flicker

                    (hide test results)
                    1. Remark, until user agents allow users to control flickering, avoid causing the screen to flicker. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-flicker.
                    Test result
                    Passed

                    7.2 - Blink and marquee usage

                      Test result
                      Passed

                      7.3 - Avoid movement in page

                      (hide test results)
                      1. Remark, until user agents allow users to freeze moving content, avoid movement in pages. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-movement.
                      Test result
                      Passed

                      7.4 - Periodically auto-refreshing pages

                        Test result
                        Passed

                        7.5 - Autoredirection

                          Test result
                          Passed

                          Guideline 8

                          (show module information)

                          8.1 - Programmatic elements such as scripts and applets must/should be directly accessible or compatible with assistive technologies (10)

                          (hide test results)
                          1. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script language="JavaScript" type="text/javascript"> <!-- // -------------------------------------- .
                            • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
                          2. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script language="VBScript" type="text/vbscript"> <!-- // Visual basic helper required to detect Fla .
                            • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
                          3. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script language="JavaScript1.1" type="text/javascript"> <!-- // Detect Client Browser type var isIE .
                            • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
                          4. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- function MenuOver (tdObj, buttonNro) { if (!document.getElemen .
                            • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
                          5. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script src="/Scripts/AC_RunActiveContent.js" type="text/javascript"></script> .
                            • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
                          6. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script src="/Scripts/AC_OETags.js" type="text/javascript"></script> .
                            • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
                          7. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script type="text/javascript"> var hasReqestedVersion = DetectFlashVer (8, 0, 0); if (hasReqested .
                            • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
                          8. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from EMBED element code: <embed src="/hakuopas/images/flash/virtuaalikampus_banneri.swf" quality="high" pluginspage="http://w .
                            • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
                          9. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script type="text/javascript" src="http://eu1.snoobi.com/snoop.php?tili=lut_fi"></script> .
                            • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
                          10. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script type="text/javascript" src="http://eu1.snoobi.com/snoop2.php?tili=lut_fi&amp;page_name=&amp; .
                            • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
                          Test result
                          Passed

                          Guideline 9

                          (show module information)

                          9.1 - Client-side versus server-side image maps

                            Test result
                            Passed

                            9.2 - Ensuring any element with own interface to be operated in a device-independent manner

                            (hide test results)
                            1. Warning, if object, embed or applet element is used, then have to ensure that those elements are keyboard accessible. Error was found from EMBED element code: <embed src="/hakuopas/images/flash/virtuaalikampus_banneri.swf" quality="high" pluginspage="http://w .
                              • Make an element keyboard accessible. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-operable.
                            Test result
                            Warning

                            9.3 - Logical event handlers are specified for scripts, rather than device-dependent event handlers (33)

                            (hide test results)
                            1. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            2. Failed, there is wrong tabindex. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            3. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            4. Failed, there is wrong tabindex. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            5. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            6. Failed, there is wrong tabindex. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            7. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            8. Failed, there is wrong tabindex. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            9. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            10. Failed, there is wrong tabindex. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            11. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            12. Failed, there is wrong tabindex. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            13. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            14. Failed, there is wrong tabindex. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            15. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            16. Failed, there is wrong tabindex. Error was found from TD element code: <td class="linktext" onmouseover="javascript:style.background='#822854';" onmouseout="javascript:sty .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            17. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from A element code: <a href="http://www.lut.fi/hakuopas/" onmouseover="return MenuOver (this, 1);" onmouseout="return Me .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            18. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from A element code: <a href="http://www.lut.fi/promootio/index.html" onmouseout="MM_swapImgRestore()" onmouseover="MM_sw .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            19. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from A element code: <a href="http://www.lut.fi/fi/kirjasto/index.html" onmouseover="return MenuOver (this, 2);" onmouseo .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            20. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from A element code: <a href="http://www.lut.fi/fi/opiskelu/nykyiset_opiskelijat/weboodi.html" onmouseover="return MenuOv .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            21. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from A element code: <a href="http://www.lut.fi/fi/oppimiskeskus/opetusteknologiapalvelut/webct6.html" onmouseover="retur .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            22. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from A element code: <a href="https://webmail.lut.fi/" onmouseover="return MenuOver (this, 5);" onmouseout="return MenuOu .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            23. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from A element code: <a href="http://www.lut.fi/fi/oppimiskeskus/fuksipussi/index.html" onmouseover="return MenuOver (thi .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            24. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td style="background: rgb(229, 229, 229) none repeat scroll 0%; -moz-background-clip: -moz-initial; .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            25. Failed, there is wrong tabindex. Error was found from TD element code: <td style="background: rgb(229, 229, 229) none repeat scroll 0%; -moz-background-clip: -moz-initial; .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            26. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            27. Failed, there is wrong tabindex. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            28. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            29. Failed, there is wrong tabindex. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            30. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            31. Failed, there is wrong tabindex. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            32. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                              • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            33. Failed, there is wrong tabindex. Error was found from TD element code: <td style="background: transparent none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-b .
                              • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                            Test result
                            Failed

                            9.4 - Creating a logical tab order through links, form controls and objects

                              Test result
                              Passed

                              9.5 - Keyboard shortcuts

                              (hide test results)
                              1. Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input type="hidden"> .
                                • Accesskey can be defined for label of input or stright to input. Best ways (example): <label for="name" accesskey="N">Name</label><input id="name" type="text" /> or <input type="button" accesskey="B" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts.
                              Test result
                              Warning

                              Guideline 10

                              (show module information)

                              10.1 - No pop-ups or other windows (3)

                              (hide test results)
                              1. Failed, page opens in new window. Error was found from A element code: <a href="http://intra.lut.fi" target="_blank"><font color="#ffffff">Henkilökunnalle</font></a> .
                                • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                              2. Failed, page opens in new window. Error was found from A element code: <a href="http://www.maailmanparhaaksi.com" target="_blank"><img src="/hakuopas/images/lut_energia_ba .
                                • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                              3. Failed, page opens in new window. Error was found from A element code: <a href="http://www.contentbakery.fi/" target="_blank"><font color="#cccccc">Content Bak .
                                • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                              Test result
                              Failed

                              10.2 - The properly positioned label considering all form controls with implicitly associated labels

                                Test result
                                Passed

                                10.3 - Verify that a linearized version of tables used for layout is provided (19)

                                (hide test results)
                                1. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px; width: 100%; height: 100%;" cellpadding="0" cellspacing="0"> <tbo .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                2. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="742"> <tbody><tr> .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                3. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                4. Remark, found table element(s). Error was found from TABLE element code: <table cellpadding="0" cellspacing="0"> <tbody><tr> <td al .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                5. Remark, found table element(s). Error was found from TABLE element code: <table class="leipis" cellpadding="0" cellspacing="0" width="100%"> <tbo .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                6. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                7. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="3" cellspacing="3" width="100%"> <tbody .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                8. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="6" cellspacing="6" width="100%"> <tbody .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                9. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                10. Remark, found table element(s). Error was found from TABLE element code: <table border="0" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                11. Remark, found table element(s). Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                12. Remark, found table element(s). Error was found from TABLE element code: <table align="center" border="0" width="100%"> <tbody><tr> <td> <p> <span class="smalltext"><a href= .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                13. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px; width: 258px;" cellpadding="0" cellspacing="0"> <tbody><tr> .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                14. Remark, found table element(s). Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                15. Remark, found table element(s). Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                16. Remark, found table element(s). Error was found from TABLE element code: <table border="0" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                17. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="4" cellspacing="4" width="100%"> <tbody><tr> .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                18. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                19. Remark, found table element(s). Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="4" cellspacing="4" width="100%"> <tbody><tr> .
                                  • Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables
                                Test result
                                Passed

                                10.4 - Including default, place-holding characters in edit boxes and text areas (empty controls)

                                  Test result
                                  Passed

                                  10.5 - Non-link, printable characters

                                    Test result
                                    Passed

                                    Guideline 11

                                    (show module information)

                                    11.1 - Use of W3C technologies

                                    (hide test results)
                                    1. Remark, use W3C technologies when they are available and appropriate for a task and use the latest versions when supported More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-latest-w3c-specs.
                                    Test result
                                    Passed

                                    11.2 - Avoid using deprecated features of W3C technologies. (18)

                                    (hide test results)
                                    1. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#ffffff">OPISKELU</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    2. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#ffffff">TUTKIMUS</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    3. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#ffffff">PALVELUT</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    4. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#ffffff">YLIOPISTO LYHYESTI</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    5. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#ffffff">YKSIKÖT</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    6. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#ffffff">LINKIT</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    7. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#ffffff">in English</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    8. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#ffffff">Sivukartta</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    9. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#ffffff">Palaute</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    10. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#ffffff">Henkilökunnalle</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    11. Failed, this HTML element is now deprecated and should not be used. Error was found from B element code: <b><a href="/php/EventCal.php?lang=FIN&amp;id=553">5.5.2008 klo 18:00</a></b> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    12. Failed, this HTML element is now deprecated and should not be used. Error was found from B element code: <b><a href="/php/EventCal.php?lang=FIN&amp;id=363">16.5.2008</a></b> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    13. Failed, this HTML element is now deprecated and should not be used. Error was found from B element code: <b><a href="/php/EventCal.php?lang=FIN&amp;id=548">23.5.2008 klo 12:00</a></b> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    14. Failed, this HTML element is now deprecated and should not be used. Error was found from B element code: <b><a href="/php/EventCal.php?lang=FIN&amp;id=436">30.5.2008 klo 15:00</a></b> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    15. Failed, this HTML element is now deprecated and should not be used. Error was found from B element code: <b><a href="/php/EventCal.php?lang=FIN&amp;id=552">3.6. - 4.6. 2008</a></b> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    16. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font class="smalltext" size="2">NORDI:n vuosittainen seminaari </font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    17. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#cccccc">W3C:n HTML-standardi (HTML 4, CSS 2), Selaimet: MSIE 5+, Netscape 6+, Opera 5+ .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    18. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#cccccc">Content Bakery Oy</font> .
                                      • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                    Test result
                                    Failed

                                    11.3 - Provide information

                                    (hide test results)
                                    1. Remark, provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-content-preferences.
                                    Test result
                                    Passed

                                    11.4 - Accessible page

                                    (hide test results)
                                    1. Remark, if, after best efforts, you cannot create an accessible page, provide a link to an alternative page that is accessible, has equivalent information, and is updated as often as the inaccessible page. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-alt-pages.
                                    Test result
                                    Passed

                                    Guideline 12

                                    (show module information)

                                    12.1 - Providing a frame title

                                      Test result
                                      Passed

                                      12.2 - Describe the purpose of frames

                                      (hide test results)
                                      1. Remark, describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-frame-longdesc.
                                      Test result
                                      Passed

                                      12.3 - Dividing large blocks of information into more manageable groups (20)

                                      (hide test results)
                                      1. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px; width: 100%; height: 100%;" cellpadding="0" cellspacing="0"> <tbo .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      2. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="742"> <tbody><tr> .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      3. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      4. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table cellpadding="0" cellspacing="0"> <tbody><tr> <td al .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      5. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="leipis" cellpadding="0" cellspacing="0" width="100%"> <tbo .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      6. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      7. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="3" cellspacing="3" width="100%"> <tbody .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      8. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="6" cellspacing="6" width="100%"> <tbody .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      9. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      10. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table border="0" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      11. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      12. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table align="center" border="0" width="100%"> <tbody><tr> <td> <p> <span class="smalltext"><a href= .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      13. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px; width: 258px;" cellpadding="0" cellspacing="0"> <tbody><tr> .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      14. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      15. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="frontpage_tableBg" style="border-width: 0px; width: 258px;" cellpadding="0" cellspacin .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      16. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table border="0" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      17. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="4" cellspacing="4" width="100%"> <tbody><tr> .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      18. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="0" cellspacing="0" width="100%"> <tbody .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      19. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border-width: 0px;" cellpadding="4" cellspacing="4" width="100%"> <tbody><tr> .
                                        • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                      20. Warning, there is too many (NaN or more) option in select that are not grouped. Error was found from SELECT element code: <select name="redirect" style="font-family: Verdana,Arial,Helvetica; font-style: normal; font-varian .
                                        • Group option-elements by optgroup-element to logic and semantic groups that are easy to understand.
                                      Test result
                                      Failed

                                      12.4 - Associating labels explicitly with their controls

                                        Test result
                                        Passed

                                        Guideline 13

                                        (show module information)

                                        13.1 - Target of each link

                                          Test result
                                          Passed

                                          13.2 - Metadata should be used to add semantic information to pages and sites

                                            Test result
                                            Passed

                                            13.3 - Information about the general layout

                                            (hide test results)
                                            1. Remark, provide information about the general layout of a site (e.g., a site map or table of contents). More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-site-description.
                                            Test result
                                            Passed

                                            13.4 - Navigation mechanisms

                                            (hide test results)
                                            1. Remark, use navigation mechanisms in a consistent manner. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-clear-nav-mechanism.
                                            Test result
                                            Passed

                                            13.5 - Navigation bars may be used to give access to the navigation mechanism

                                              Test result
                                              Passed

                                              13.6 - Title should be used in map when grouping links by map

                                                Test result
                                                Passed

                                                13.7 - Different types of searches

                                                (hide test results)
                                                1. Remark, if search functions are provided, enable different types of searches for different skill levels and preferences. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-searches.
                                                Test result
                                                Passed

                                                13.8 - Information at the beginning

                                                (hide test results)
                                                1. Remark, place distinguishing information at the beginning of headings, paragraphs, lists, etc. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-front-loading.
                                                Test result
                                                Passed

                                                13.9 - Working links

                                                (hide test results)
                                                1. Warning, no title in link. Error was found from LINK element code: <link href="/style.css" rel="stylesheet" type="text/css"> .
                                                  • Add title for link.
                                                Test result
                                                Warning

                                                13.10 - Skipping over multi-line ASCII art

                                                  Test result
                                                  Passed

                                                  Guideline 14

                                                  (show module information)

                                                  14.1 - Clear and simple language.

                                                  (hide test results)
                                                  1. Remark, use the clearest and simplest language appropriate for a site's content.
                                                  Test result
                                                  Passed

                                                  14.2 - Supplement text with presentations.

                                                  (hide test results)
                                                  1. Remark, supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.
                                                  Test result
                                                  Passed

                                                  14.3 - No style element, no style attributes.

                                                  (hide test results)
                                                  1. Warning, number of style attributes found: 71. Error was found from BODY element code: <body onload="MM_preloadImages('/lut_images/promootiolinkki_on.gif')" lang="fi"> <table style="borde .
                                                    • Please use CSS rather than style attributes.
                                                  Test result
                                                  Warning
                                                  kuuluu seuraaviin kategorioihin: , ,