Test results

Test subject: http://www.jyu.fi/sport/laitokset/liikuntabiologia/nmrc/

Statistics for the evaluated page

Total tests: 64

TestsPercentTotalPercent
Total passed:4976.56%4930.06%
-Passed with remarks:2031.25%2314.11%
Failed:1117.19%2615.95%
Warnings:46.25%6539.88%
Total:64100.00%163100.00%

WCAG

Guideline 1

(show module information)

1.1 - Elements have text equivalents. (3)

(hide test results)
  1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="http://www.jyu.fi/portal_javascripts/JyuStyle-tyyli/ploneScripts .
    • 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 type="text/javascript"><!-- /* - analytics.js - */ // http://www.jyu.fi/portal_javascripts .
    • 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 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>
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. (4)

      (hide test results)
      1. Failed, the color difference of rgb(68, 68, 68) and rgb(231, 236, 244) is too low. Error was found from DT element code: <dt class="portletHeader"> <span class="portletTopLeft"></span> <a href="htt .
        • Change the colors so that they have higher color difference.
      2. Failed, the color difference of rgb(68, 68, 68) and rgb(231, 236, 244) is too low. Error was found from DT element code: <dt class="portletHeader">Laadunvarmistus</dt> .
        • Change the colors so that they have higher color difference.
      3. Failed, the color difference of rgb(68, 68, 68) and rgb(231, 236, 244) is too low. Error was found from DT element code: <dt class="portletHeader">Laitokset ja yksiköt</dt> .
        • Change the colors so that they have higher color difference.
      4. Failed, the color difference of rgb(68, 68, 68) and rgb(231, 236, 244) is too low. Error was found from DT element code: <dt class="portletHeader">Linkkejä</dt> .
        • 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.

          Test result
          Passed

          3.3 - Proper font stylings.

            Test result
            Passed

            3.4 - Relative over absolute. (3)

            (hide test results)
            1. Failed, absolute size definition found. #portal-top:"border-bottom: 8px solid rgb(0, 147, 226)". Error was found from STYLE element code: <style type="text/css" media="all"> body { background: url(http://www.jyu.fi/bg_liuku.jpg) top left .
              • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
            2. Failed, absolute size definition found. #page-heading:"height: 35px". Error was found from STYLE element code: <style type="text/css" media="all"> body { background: url(http://www.jyu.fi/bg_liuku.jpg) top left .
              • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
            3. Failed, absolute size definition found. #tiedekunnat:"height: 126px". Error was found from STYLE element code: <style type="text/css" media="all"> body { background: url(http://www.jyu.fi/bg_liuku.jpg) top left .
              • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
            Test result
            Failed

            3.5 - Proper header usage. (2)

            (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 H5 element code: <h5 class="hiddenStructure">Tehdyt toimenpiteet</h5> .
              • Lower the header level to at least <h2>.
            2. Warning, <h1> found 2 times. Error was found from H1 element code: <h1 class="documentFirstHeading">NeuroMuscular Research Center</h1> .
              • Please consider using <h1> only once per page.
            Test result
            Failed

            3.6 - Proper List usage. (6)

            (hide test results)
            1. Failed, a list without list items found. Error was found from DL element code: <dl class="portlet" id="portlet-navigation-tree"> <dt class="portletHeader"> <span class .
              • List element <dl> should contain at least one list item <li>.
            2. Failed, a list without list items found. Error was found from DL element code: <dl class="portlet"> <dt class="portletHeader">Laadunvarmistus</dt> <dd class="por .
              • List element <dl> should contain at least one list item <li>.
            3. Failed, a list without list items found. Error was found from DL element code: <dl class="portlet"> <dt class="portletHeader">Laitokset ja yksiköt</dt> <dd class .
              • List element <dl> should contain at least one list item <li>.
            4. Failed, a list without list items found. Error was found from DL element code: <dl class="portlet"> <dt class="portletHeader">Linkkejä</dt> <dd class="portletIte .
              • List element <dl> should contain at least one list item <li>.
            5. Failed, a list without list items found. Error was found from DL element code: <dl class="portlet" id="portlet-contact"> <dt class="portletHeader"> <span class="portl .
              • List element <dl> should contain at least one list item <li>.
            6. Failed, a list without list items found. Error was found from DL element code: <dl class="portlet"> <dt class="portletHeader">Vuokatin yhteystiedot</dt> <dd clas .
              • List element <dl> should contain at least one list item <li>.
            Test result
            Failed

            3.7 - Proper quote usage.

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

              (hide test results)
              1. Warning, potential abbreviation found: THK. Error was found from A element code: <a class="external-link" href="http://www.jyu.fi/erillis/thk/palvelut/koulutus/taitavaksi">THK/Taita .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              2. Warning, potential abbreviation found: ATK. Error was found from A element code: <a title="atk-tuki henkilöstölle" class="internal-link" href="resolveuid/03211e37114f84498c239858458 .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              3. Warning, potential abbreviation found: NMRC. Error was found from P element code: <p>21.10.1997 the rector of the University of Jyväskylä established in the structure of the Departme .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              4. Warning, potential abbreviation found: LIKES. Error was found from A element code: <a title="external-link" href="http://www.likes.fi/fi/tutkimus/index.html">LIKES</a> .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              5. Warning, potential abbreviation found: NMRC. Error was found from P element code: <p>The task of the NMRC is to investigate neuromuscular system, its functional mechanisms and adapta .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              6. Warning, potential abbreviation found: NMRC. Error was found from P element code: <p>NMRC represents unique know-how in Finland, in which research in biomedical aspects of physical a .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              7. Warning, potential abbreviation found: NMRC. Error was found from P element code: <p>NMRC represents unique know-how in Finland, in which research in biomedical aspects of physical a .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              8. Warning, potential abbreviation found: NMRC. Error was found from P element code: <p>The major research areas of the NMRC are the following:</p> .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              9. Warning, potential abbreviation found: NMRC. Error was found from P element code: <p>NMRC utilizes primarily the research facilities of the Department of Biology of Physical Activity .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              10. Warning, potential abbreviation found: LIKES. Error was found from P element code: <p>NMRC utilizes primarily the research facilities of the Department of Biology of Physical Activity .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              11. Warning, potential abbreviation found: FIN. Error was found from DIV element code: <div class="portletItem odd">Department of Biology of Physical Activity<br> P.O: Box 35<br> FIN-4001 .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              12. Warning, potential abbreviation found: FIN. Error was found from P element code: <p>Sport Technology Programme<br>Snowpolis<br>Kidekuja 2<br>FIN-88610 Vuokatti Finland<br>Tel. +358 .
                • 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.1 - Table used properly (40)

                (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 class="ploneCalendar" id="thePloneCalendar" title="Calendar" summary="Kalenteri"> <th .
                  • 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.
                2. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TH element code: <th colspan="5"> lokakuu 2008 </th> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                3. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>su</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                4. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>ma</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                5. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>ti</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                6. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>ke</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                7. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>to</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                8. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>pe</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                9. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>la</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                10. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>1</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                11. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>2</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                12. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>3</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                13. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>4</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                14. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>5</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                15. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>6</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                16. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>7</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                17. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>8</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                18. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td class="event"><a href="/jyuplone/sport/laitokset/liikuntabiologia/nmrc/index_html/search_pages?r .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                19. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td class="event"><a href="/jyuplone/sport/laitokset/liikuntabiologia/nmrc/index_html/search_pages?r .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                20. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td class="event"><a href="/jyuplone/sport/laitokset/liikuntabiologia/nmrc/index_html/search_pages?r .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                21. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td class="event"><a href="/jyuplone/sport/laitokset/liikuntabiologia/nmrc/index_html/search_pages?r .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                22. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>13</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                23. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>14</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                24. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>15</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                25. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>16</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                26. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>17</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                27. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>18</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                28. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>19</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                29. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>20</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                30. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>21</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                31. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>22</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                32. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td class="event"><a href="/jyuplone/sport/laitokset/liikuntabiologia/nmrc/index_html/search_pages?r .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                33. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td class="todayevent"><a href="/jyuplone/sport/laitokset/liikuntabiologia/nmrc/index_html/search_pa .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                34. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>25</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                35. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>26</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                36. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>27</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                37. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>28</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                38. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td class="event"><a href="/jyuplone/sport/laitokset/liikuntabiologia/nmrc/index_html/search_pages?r .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                39. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>30</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                40. Warning, there is used an id in th or a headers in td but not in all th and td that have text in it. Error was found from TD element code: <td>31</td> .
                  • If use an id in a th or a headers in a td, then have to use an id in every th and a headers in every td that have text in it. Example: <th id="january">...<td headers="january>...". More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers.
                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

                5.3 - Table is used as layout

                  Test result
                  Passed

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

                  (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 id="portal-columns" title="" summary=""> <tbody> <tr> <!-- sta .
                    • 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. Warning, one of the next three items was not used in a table: caption, summary and title. Error was found from TABLE element code: <table class="ploneCalendar" id="thePloneCalendar" title="Calendar" summary="Kalenteri"> <th .
                    • Use caption, summary and title in a table. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmas calendar. Shows how many days is left before Christmas."> <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, 8 deprecated elements were found. Error was found from STYLE element code: <style type="text/css"><!-- @import url(http://www.jyu.fi/portal_css/JyuStyle-tyyli/ploneStyles8988. .
                      • 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 (3)

                    (hide test results)
                    1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="http://www.jyu.fi/portal_javascripts/JyuStyle-tyyli/ploneScripts .
                      • 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 type="text/javascript"><!-- /* - analytics.js - */ // http://www.jyu.fi/portal_javascripts .
                      • 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 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>
                    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

                        Test result
                        Passed

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

                                (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" src="http://www.jyu.fi/portal_javascripts/JyuStyle-tyyli/ploneScripts .
                                  • 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 type="text/javascript"><!-- /* - analytics.js - */ // http://www.jyu.fi/portal_javascripts .
                                  • 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 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.
                                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

                                    Test result
                                    Passed

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

                                      Test result
                                      Passed

                                      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, accesskey should be used for inputs whose type is submit, button or reset. Error was found from INPUT element code: <input class="searchButton" value="Hae" type="submit"> .
                                          • 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

                                          Test result
                                          Passed

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

                                            (hide test results)
                                            1. Remark, found table element(s). Error was found from TABLE element code: <table id="portal-columns" title="" summary=""> <tbody> <tr> <!-- sta .
                                              • 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 class="ploneCalendar" id="thePloneCalendar" title="Calendar" summary="Kalenteri"> <th .
                                              • 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 id="searchGadget" name="SearchableText" size="15" title="Etsi sivustolta" accesskey="4" class .
                                              • 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

                                              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.

                                                Test result
                                                Passed

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

                                                  (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 H5 element code: <h5 class="hiddenStructure">Tehdyt toimenpiteet</h5> .
                                                    • Lower the header level to at least <h2>.
                                                  2. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table id="portal-columns" title="" summary=""> <tbody> <tr> <!-- sta .
                                                    • 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. Warning, <h1> found 2 times. Error was found from H1 element code: <h1 class="documentFirstHeading">NeuroMuscular Research Center</h1> .
                                                    • Please consider using <h1> only once per page.
                                                  4. Warning, in table should be used all of next three: caption, summary and title. Error was found from TABLE element code: <table class="ploneCalendar" id="thePloneCalendar" title="Calendar" summary="Kalenteri"> <th .
                                                    • Use in table all three: content, 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

                                                    Test result
                                                    Passed

                                                    Guideline 13

                                                    (show module information)

                                                    13.1 - Target of each link (6)

                                                    (hide test results)
                                                    1. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="http://www.jyu.fi/sport/laitokset/liikuntabiologia">Liikuntabiologian laitos</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="http://www.jyu.fi/sport/sitemap" class="tile"> </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="http://www.jyu.fi/sport/sitemap" class="tile"> </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="http://www.jyu.fi/sport/sitemap" class="tile"> </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="http://www.jyu.fi/sport/sitemap" class="tile"> </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="https://www.jyu.fi/sport/laitokset/liikuntabiologia/en/personnel" class="state-published vi .
                                                      • 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

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

                                                          (hide test results)
                                                          1. Failed, unworkable link. Error was found from LINK element code: <link rel="home" href="http://www.jyu.fi" title="Front page"> .
                                                            • Add working href for link
                                                          2. Warning, no title in link. Error was found from LINK element code: <link rel="shortcut icon" type="image/x-icon" href="http://www.jyu.fi/favicon.ico"> .
                                                            • Add title for link.
                                                          Test result
                                                          Failed

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

                                                            (hide test results)
                                                            1. Warning, style element found. Error was found from STYLE element code: <style type="text/css"><!-- @import url(http://www.jyu.fi/portal_css/JyuStyle-tyyli/ploneStyles8988. .
                                                              • Please use CSS rather than style element.
                                                            2. Warning, number of style attributes found: 2. Error was found from BODY element code: <body class="section-sport"> <div id="visual-portal-wrapper"> <div id="portal-top"> .
                                                              • Please use CSS rather than style attributes.
                                                            Test result
                                                            Warning