ESOK-hanke 2006-2011

Foxability - Test results

Test results

Test results

Test subject: http://www.kajak.fi/suomeksi.iw3

Statistics for the evaluated page

Total tests: 67

TestsPercentTotalPercent
Total passed:4567.16%4521.74%
-Passed with remarks:2232.84%4119.81%
Failed:1623.88%9244.44%
Warnings:68.96%2914.01%
Total:67100.00%207100.00%

WCAG 1.0 A

Guideline 1

(show module information)

1.1 - Elements have text equivalents. (19)

(hide test results)
  1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"><!--//--><![CDATA[//><!-- function email() { wind .
    • 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 src="http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> .
    • 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 type="text/javascript"> _uacct = "UA-1491385-1"; urchinTracker(); </script> .
    • 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"> //<![CDATA[ var theForm = document.forms['InfowebForm']; if (!theFor .
    • 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="/WebResource.axd?d=8w8EbsgEIHM_Ze0YpIgfBQ2&amp;t=633695378075598361" type="text/javascr .
    • 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="/ScriptResource.axd?d=01GXe_K1L3YnwurDQWgR2aqW3Ck6CRDXGRCYHYdoeGz-9iS8Hou22rsh6VM-Rk2nL .
    • 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 src="/ScriptResource.axd?d=01GXe_K1L3YnwurDQWgR2aqW3Ck6CRDXGRCYHYdoeGz-9iS8Hou22rsh6VM-Rk2nL .
    • 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"> //<![CDATA[ Sys.WebForms.PageRequestManager._initialize('ScriptManag .
    • 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"><!--//--><![CDATA[//><!-- function printcontent(){ window.o .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  10. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"><!--//--><![CDATA[//><!-- sfHover = function() { var .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  11. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="/includes/swfobject.js"></script> .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  12. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/loader.aspx?id=5556d024-fedf-4e7d-8fc3-40e148012ac3" alt="" id="6108" width="428" height= .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  13. Failed, alt attribute not found. Error was found from IMG element code: <img src="/loader.aspx?id=1e713afb-3c54-49cc-8e5e-9db3c96e2632"> .
    • Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
  14. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="/includes/swfobject.js"></script> .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  15. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/loader.aspx?id=811cbe41-f19a-4f88-bf12-3e14d1ac770e" alt="" id="6110" width="170" height= .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  16. Failed, alt attribute not found. Error was found from IMG element code: <img src="/loader.aspx?id=7d53ab74-1645-410d-9388-96be37efe3ea" border="0"> .
    • Please insert an 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="/loader.aspx?id=82c77f21-d402-47b8-ada1-b6c3d409c801" border="0"> .
    • Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
  18. Failed, alt attribute not found. Error was found from IMG element code: <img src="/loader.aspx?id=ebf85f02-fba1-4527-ac5a-8f25b436e09c" border="0"> .
    • Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
  19. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> //<![CDATA[ Sys.Application.initialize(); //]]> </script> .
    • 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

    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

    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

    Guideline 5

    (show module information)

    5.1 - Table used properly

    (hide test results)
    1. Failed, if use one of thead, tfoot or tbody then must use all of them. Error was found from TABLE element code: <table style="width: 880px; height: 240px;" background="/loader.aspx?id=1d0a1f91-394d-43fa-aecb-96d1 .
      • Use all of thead, tfoot and tbody or if you do not need them, do not use them at all. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-structure.
    Test result
    Failed

    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

    Guideline 6

    (show module information)

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

    (hide test results)
    1. Remark, 16 deprecated elements were found. Error was found from LINK element code: <link href="http://www.kajak.fi/includes/global_print.css" type="text/css" media="print" rel="styles .
      • 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 thedynamic content changes (13)

    (hide test results)
    1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"><!--//--><![CDATA[//><!-- function email() { wind .
      • 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 src="http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> .
      • 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 type="text/javascript"> _uacct = "UA-1491385-1"; urchinTracker(); </script> .
      • 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"> //<![CDATA[ var theForm = document.forms['InfowebForm']; if (!theFor .
      • 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="/WebResource.axd?d=8w8EbsgEIHM_Ze0YpIgfBQ2&amp;t=633695378075598361" type="text/javascr .
      • 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="/ScriptResource.axd?d=01GXe_K1L3YnwurDQWgR2aqW3Ck6CRDXGRCYHYdoeGz-9iS8Hou22rsh6VM-Rk2nL .
      • 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 src="/ScriptResource.axd?d=01GXe_K1L3YnwurDQWgR2aqW3Ck6CRDXGRCYHYdoeGz-9iS8Hou22rsh6VM-Rk2nL .
      • 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"> //<![CDATA[ Sys.WebForms.PageRequestManager._initialize('ScriptManag .
      • 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"><!--//--><![CDATA[//><!-- function printcontent(){ window.o .
      • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
    10. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"><!--//--><![CDATA[//><!-- sfHover = function() { var .
      • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
    11. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="/includes/swfobject.js"></script> .
      • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
    12. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="/includes/swfobject.js"></script> .
      • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
    13. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> //<![CDATA[ Sys.Application.initialize(); //]]> </script> .
      • 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

      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

      Guideline 8

      (show module information)

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

      (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 type="text/javascript"><!--//--><![CDATA[//><!-- function email() { wind .
        • 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 src="http://www.google-analytics.com/urchin.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.
      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 type="text/javascript"> _uacct = "UA-1491385-1"; urchinTracker(); </script> .
        • 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"> //<![CDATA[ var theForm = document.forms['InfowebForm']; if (!theFor .
        • 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="/WebResource.axd?d=8w8EbsgEIHM_Ze0YpIgfBQ2&amp;t=633695378075598361" type="text/javascr .
        • 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="/ScriptResource.axd?d=01GXe_K1L3YnwurDQWgR2aqW3Ck6CRDXGRCYHYdoeGz-9iS8Hou22rsh6VM-Rk2nL .
        • 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 src="/ScriptResource.axd?d=01GXe_K1L3YnwurDQWgR2aqW3Ck6CRDXGRCYHYdoeGz-9iS8Hou22rsh6VM-Rk2nL .
        • 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 SCRIPT element code: <script type="text/javascript"> //<![CDATA[ Sys.WebForms.PageRequestManager._initialize('ScriptManag .
        • 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"><!--//--><![CDATA[//><!-- function printcontent(){ window.o .
        • 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"><!--//--><![CDATA[//><!-- sfHover = function() { var .
        • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
      11. 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="/includes/swfobject.js"></script> .
        • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
      12. 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="/includes/swfobject.js"></script> .
        • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
      13. 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"> //<![CDATA[ Sys.Application.initialize(); //]]> </script> .
        • 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

        Guideline 11

        (show module information)

        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

          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

          WCAG 1.0 AAA

          Guideline 1

          (show module information)

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

            Test result
            Passed

            Guideline 2

            (show module information)

            2.2 - Colors are visible. (3)

            (hide test results)
            1. Failed, the color difference of rgb(0, 0, 0) and rgb(177, 139, 85) is too low. Error was found from BODY element code: <body id="iw_mainbody" class="mainbody"> <form name="InfowebForm" method="post" action="/su .
              • Change the colors so that they have higher color difference.
            2. Failed, the color difference of rgb(0, 0, 0) and rgb(0, 0, 0) is too low. Error was found from DIV element code: <div id="topline"></div> .
              • Change the colors so that they have higher color difference.
            3. Failed, the brightness difference of rgb(0, 0, 0) and rgb(0, 0, 0) is too low. Error was found from DIV element code: <div id="topline"></div> .
              • Change the colors so that they have higher brightness difference.
            Test result
            Failed

            Guideline 4

            (show module information)

            4.2 - Acronyms and abbreviations. (2)

            (hide test results)
            1. Warning, potential abbreviation found: KAMO. Error was found from A element code: <a href="/suomeksi/Opiskelijoille/Opiskelijakunta_KAMO.iw3">Opiskelijakunta KAMO</a> .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            2. Warning, potential abbreviation found: KAMO. Error was found from A element code: <a id="ContentVersionEditView1_interface_ctl07_ctl00_Public1_ctl20_HyperLink1" href="http://www.kaja .
              • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
            Test result
            Warning

            4.3 - Primary language.

              Test result
              Passed

              Guideline 5

              (show module information)

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

              (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="width: 880px; height: 240px;" background="/loader.aspx?id=1d0a1f91-394d-43fa-aecb-96d1 .
                • 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> <tbody> <tr> <td><font color="#808080">[11.6.2009]</font> <br><strong><a href="/suomeksi/Esi .
                • 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> <tbody> <tr> <td><font color="#808080">[11.6.2009]</font> <br><strong><a href="/suomeksi/Esi .
                • 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> <tbody> <tr> <td><font color="#808080">[1.6.2009]</font> <br><strong><a href="/suomeksi/Esit .
                • 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> <tbody> <tr> <td><font color="#808080">[29.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                • 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> <tbody> <tr> <td><font color="#808080">[28.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                • 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> <tbody> <tr> <td><font color="#808080">[26.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                • 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> <tbody> <tr> <td><font color="#808080">[14.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                • 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 9

                (show module information)

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

                  Test result
                  Passed

                  9.5 - Keyboard shortcuts (5)

                  (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 name="__EVENTTARGET" id="__EVENTTARGET" value="" 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.
                  2. Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input name="__EVENTARGUMENT" id="__EVENTARGUMENT" value="" 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.
                  3. Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUKMTQxOTcyNjgzNw9kFgJmD2QWBAIHD2QWAmYPZBYCAg .
                    • 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.
                  4. Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input name="ContentVersionEditView1$interface$SearchPanel1$keyword" id="ContentVersionEditView1_int .
                    • 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.
                  5. Warning, accesskey should be used for inputs whose type is submit, button or reset. Error was found from INPUT element code: <input name="ContentVersionEditView1$interface$SearchPanel1$btnSearch" value="Hae" onclick="if(docum .
                    • 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.3 - Verify that a linearized version of tables used for layout is provided (8)

                  (hide test results)
                  1. Remark, found table element(s). Error was found from TABLE element code: <table style="width: 880px; height: 240px;" background="/loader.aspx?id=1d0a1f91-394d-43fa-aecb-96d1 .
                    • 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> <tbody> <tr> <td><font color="#808080">[11.6.2009]</font> <br><strong><a href="/suomeksi/Esi .
                    • 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> <tbody> <tr> <td><font color="#808080">[11.6.2009]</font> <br><strong><a href="/suomeksi/Esi .
                    • 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> <tbody> <tr> <td><font color="#808080">[1.6.2009]</font> <br><strong><a href="/suomeksi/Esit .
                    • 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> <tbody> <tr> <td><font color="#808080">[29.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                    • 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> <tbody> <tr> <td><font color="#808080">[28.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                    • 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> <tbody> <tr> <td><font color="#808080">[26.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                    • 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> <tbody> <tr> <td><font color="#808080">[14.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                    • 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)

                  (hide test results)
                  1. Failed, no default text. Error was found from INPUT element code: <input name="ContentVersionEditView1$interface$SearchPanel1$keyword" id="ContentVersionEditView1_int .
                    • Add default text. Example: <input type="text" value="Write here" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-place-holders.
                  Test result
                  Failed

                  10.5 - Non-link, printable characters

                  (hide test results)
                  1. Failed, link element a is too close to next one. Error was found from A element code: <a href="http://www.kajak.fi/suomeksi/Tyoelamapalvelut/Koulutuspalvelut,_taydennyskoulutus/Kurssitar .
                    • Separate links by some element or "whitespace - Some character(s) - whitespase". Examples:...<a href="page7.html">Prew</a> | <a href="page.html9">Next</a>... or...<a href="page7.html">Prew</a> <br /> <a href="page.html9">Next</a>... or...<li><a href="page7.html">Prew</a></li><li><a href="page.html9">Next</a></li>... More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-divide-links.
                  Test result
                  Failed

                  Guideline 11

                  (show module information)

                  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

                  Guideline 13

                  (show module information)

                  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 (5)

                      (hide test results)
                      1. Warning, no title in link. Error was found from LINK element code: <link href="http://www.kajak.fi/includes/global_print.css" type="text/css" media="print" rel="styles .
                        • Add title for link.
                      2. Warning, no title in link. Error was found from LINK element code: <link href="http://www.kajak.fi/includes/global.css" type="text/css" media="screen, projection" rel= .
                        • Add title for link.
                      3. Warning, no title in link. Error was found from LINK element code: <link href="http://www.kajak.fi/interfaces/kajak/internet/includes/print.css" media="print" rel="sty .
                        • Add title for link.
                      4. Warning, no title in link. Error was found from LINK element code: <link href="http://www.kajak.fi/interfaces/kajak/internet/includes/style.css" media="screen, project .
                        • Add title for link.
                      5. Warning, no title in link. Error was found from LINK element code: <link rel="shortcut icon" href="/interfaces/kajak/internet/images/kajak_logo.ico"> .
                        • Add title for link.
                      Test result
                      Warning

                      13.10 - Skipping over multi-line ASCII art

                        Test result
                        Passed

                        Guideline 14

                        (show module information)

                        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. (2)

                        (hide test results)
                        1. Warning, style element found. Error was found from STYLE element code: <style type="text/css"> .iw_banner_ { display: block; margin-bottom: px; } </style .
                          • Please use CSS rather than style element.
                        2. Warning, number of style attributes found: 11. Error was found from BODY element code: <body id="iw_mainbody" class="mainbody"> <form name="InfowebForm" method="post" action="/su .
                          • Please use CSS rather than style attributes.
                        Test result
                        Warning

                        WCAG 1.0 AA

                        Guideline 3

                        (show module information)

                        3.1 - MathML

                          Test result
                          Passed

                          3.2 - Formal grammars.

                            Test result
                            Passed

                            3.3 - Proper font stylings. (8)

                            (hide test results)
                            1. Failed, deprecated element found. Error was found from FONT element code: <font color="#808080">[11.6.2009]</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="#808080">[11.6.2009]</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="#808080">[1.6.2009]</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="#808080">[29.5.2009]</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="#808080">[28.5.2009]</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="#808080">[26.5.2009]</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="#808080">[14.5.2009]</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 size="+0"><img src="/loader.aspx?id=1e713afb-3c54-49cc-8e5e-9db3c96e2632"></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.

                              Test result
                              Passed

                              3.5 - Proper header usage.

                              (hide test results)
                              1. Failed, improper header nesting: Header levels must not increase by more than one level per heading. Do not use headers to create font effects; use style sheets to change font styles. Error was found from H3 element code: <h3></h3> .
                                • Lower the header level to at least <h1>.
                              Test result
                              Failed

                              3.6 - Proper List usage.

                                Test result
                                Passed

                                3.7 - Proper quote usage.

                                (hide test results)
                                1. Remark, the number of quotation marks found: 36 Error was found from BODY element code: <body id="iw_mainbody" class="mainbody"> <form name="InfowebForm" method="post" action="/su .
                                  • Please consider using <q> and <blockquote> for quotes.
                                Test result
                                Passed

                                Guideline 5

                                (show module information)

                                5.3 - Table is used as layout (8)

                                (hide test results)
                                1. Warning, a table may be used as a layout. Error was found from TABLE element code: <table style="width: 880px; height: 240px;" background="/loader.aspx?id=1d0a1f91-394d-43fa-aecb-96d1 .
                                  • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                                2. Warning, a table may be used as a layout. Error was found from TABLE element code: <table> <tbody> <tr> <td><font color="#808080">[11.6.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                  • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                                3. Warning, a table may be used as a layout. Error was found from TABLE element code: <table> <tbody> <tr> <td><font color="#808080">[11.6.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                  • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                                4. Warning, a table may be used as a layout. Error was found from TABLE element code: <table> <tbody> <tr> <td><font color="#808080">[1.6.2009]</font> <br><strong><a href="/suomeksi/Esit .
                                  • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                                5. Warning, a table may be used as a layout. Error was found from TABLE element code: <table> <tbody> <tr> <td><font color="#808080">[29.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                  • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                                6. Warning, a table may be used as a layout. Error was found from TABLE element code: <table> <tbody> <tr> <td><font color="#808080">[28.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                  • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                                7. Warning, a table may be used as a layout. Error was found from TABLE element code: <table> <tbody> <tr> <td><font color="#808080">[26.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                  • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                                8. Warning, a table may be used as a layout. Error was found from TABLE element code: <table> <tbody> <tr> <td><font color="#808080">[14.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                  • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                                Test result
                                Warning

                                Guideline 6

                                (show module information)

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

                                (hide test results)
                                1. Remark, 16 deprecated elements were found. Error was found from LINK element code: <link href="http://www.kajak.fi/includes/global_print.css" type="text/css" media="print" rel="styles .
                                  • 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 thedynamic content changes (13)

                                (hide test results)
                                1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"><!--//--><![CDATA[//><!-- function email() { wind .
                                  • 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 src="http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> .
                                  • 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 type="text/javascript"> _uacct = "UA-1491385-1"; urchinTracker(); </script> .
                                  • 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"> //<![CDATA[ var theForm = document.forms['InfowebForm']; if (!theFor .
                                  • 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="/WebResource.axd?d=8w8EbsgEIHM_Ze0YpIgfBQ2&amp;t=633695378075598361" type="text/javascr .
                                  • 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="/ScriptResource.axd?d=01GXe_K1L3YnwurDQWgR2aqW3Ck6CRDXGRCYHYdoeGz-9iS8Hou22rsh6VM-Rk2nL .
                                  • 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 src="/ScriptResource.axd?d=01GXe_K1L3YnwurDQWgR2aqW3Ck6CRDXGRCYHYdoeGz-9iS8Hou22rsh6VM-Rk2nL .
                                  • 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"> //<![CDATA[ Sys.WebForms.PageRequestManager._initialize('ScriptManag .
                                  • 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"><!--//--><![CDATA[//><!-- function printcontent(){ window.o .
                                  • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                                10. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"><!--//--><![CDATA[//><!-- sfHover = function() { var .
                                  • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                                11. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="/includes/swfobject.js"></script> .
                                  • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                                12. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="/includes/swfobject.js"></script> .
                                  • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                                13. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> //<![CDATA[ Sys.Application.initialize(); //]]> </script> .
                                  • 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

                                  Test result
                                  Passed

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

                                  (hide test results)
                                  1. Failed, found device independent event handler. Error was found from INPUT element code: <input name="ContentVersionEditView1$interface$SearchPanel1$btnSearch" value="Hae" onclick="if(docum .
                                    • If you use onclick, provide also redundant event handler: onkeypress.
                                  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.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 9

                                          (show module information)

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

                                            Test result
                                            Passed

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

                                              Test result
                                              Passed

                                              Guideline 10

                                              (show module information)

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

                                              (hide test results)
                                              1. Failed, page opens in new window. Error was found from A element code: <a target="_blank" href="/suomeksi/Opiskelijoille/Opinnaytetyo.iw3">Opinnäytetyö</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 target="_blank" href="/modules/Banner/public/banner_redirect.aspx?id=6108"><img src="/loader.aspx .
                                                • 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 target="_blank" href="/modules/Banner/public/banner_redirect.aspx?id=6110"><img src="/loader.aspx .
                                                • 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.
                                              4. Failed, page opens in new window. Error was found from A element code: <a id="ContentVersionEditView1_interface_ctl07_ctl00_Public1_ctl26_HyperLink1" href="https://remote. .
                                                • 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

                                              (hide test results)
                                              1. Failed, wrong label usage. Error was found from INPUT element code: <input name="ContentVersionEditView1$interface$SearchPanel1$keyword" id="ContentVersionEditView1_int .
                                                • Use label right before or after input and use for - id relationship or parentship.More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-unassociated-labels.
                                              Test result
                                              Failed

                                              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. (8)

                                              (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="#808080">[11.6.2009]</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="#808080">[11.6.2009]</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="#808080">[1.6.2009]</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="#808080">[29.5.2009]</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="#808080">[28.5.2009]</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="#808080">[26.5.2009]</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="#808080">[14.5.2009]</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 size="+0"><img src="/loader.aspx?id=1e713afb-3c54-49cc-8e5e-9db3c96e2632"></font> .
                                                • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                              Test result
                                              Failed

                                              Guideline 12

                                              (show module information)

                                              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 (9)

                                              (hide test results)
                                              1. Failed, Improper header nesting: Header levels must not increase by more than one level per heading. Do not use headers to create font effects; use style sheets to change font styles. Error was found from H3 element code: <h3></h3> .
                                                • Lower the header level to at least <h1>.
                                              2. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="width: 880px; height: 240px;" background="/loader.aspx?id=1d0a1f91-394d-43fa-aecb-96d1 .
                                                • 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> <tbody> <tr> <td><font color="#808080">[11.6.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                                • 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> <tbody> <tr> <td><font color="#808080">[11.6.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                                • 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> <tbody> <tr> <td><font color="#808080">[1.6.2009]</font> <br><strong><a href="/suomeksi/Esit .
                                                • 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> <tbody> <tr> <td><font color="#808080">[29.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                                • 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> <tbody> <tr> <td><font color="#808080">[28.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                                • 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> <tbody> <tr> <td><font color="#808080">[26.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                                • 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> <tbody> <tr> <td><font color="#808080">[14.5.2009]</font> <br><strong><a href="/suomeksi/Esi .
                                                • 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.
                                              Test result
                                              Failed

                                              12.4 - Associating labels explicitly with their controls

                                              (hide test results)
                                              1. Failed, input does not have label. Error was found from INPUT element code: <input name="ContentVersionEditView1$interface$SearchPanel1$keyword" id="ContentVersionEditView1_int .
                                                • Use label right before or after input and use for - id relationship or parentship.
                                              Test result
                                              Failed

                                              Guideline 13

                                              (show module information)

                                              13.1 - Target of each link (7)

                                              (hide test results)
                                              1. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/suomeksi/Ylatunnisteen_apuvalikko/Extranet.iw3">Extranet</a> .
                                                • Use unique and meaningfull name and title for different links.
                                              2. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/suomeksi/Ylatunnisteen_apuvalikko/In_English.iw3">In English</a> .
                                                • Use unique and meaningfull name and title for different links.
                                              3. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/suomeksi/Esittely/Ajankohtaista.iw3">Ajankohtaista</a> .
                                                • Use unique and meaningfull name and title for different links.
                                              4. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/suomeksi/Esittely/Yhteystiedot.iw3">Yhteystiedot</a> .
                                                • Use unique and meaningfull name and title for different links.
                                              5. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/suomeksi/Esittely/Tyoelamapalvelut.iw3">Työelämäpalvelut</a> .
                                                • Use unique and meaningfull name and title for different links.
                                              6. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/suomeksi/Esittely/Kansainvalisyys.iw3">Kansainvälisyys</a> .
                                                • Use unique and meaningfull name and title for different links.
                                              7. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/suomeksi/Opiskelijoille/Harjoittelu.iw3">Harjoittelu</a> .
                                                • Use unique and meaningfull name and title for different links.
                                              Test result
                                              Warning

                                              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
                                                kuuluu seuraaviin kategorioihin: , ,