ESOK-hanke 2006-2011

Foxability - Test results

Test results

Test results

Test subject: http://www.samk.fi/

Statistics for the evaluated page

Total tests: 67

TestsPercentTotalPercent
Total passed:4871.64%4822.43%
-Passed with remarks:2232.84%3114.49%
Failed:1217.91%10348.13%
Warnings:710.45%3214.95%
Total:67100.00%214100.00%

WCAG 1.0 A

Guideline 1

(show module information)

1.1 - Elements have text equivalents. (20)

(hide test results)
  1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="/js/swfobject.js?120219720"></script> .
    • 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" src="/js/quicktime.js?96560880"></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"> //<![CDATA[ var theForm = document.forms['aspnetForm']; if (!theForm .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  4. Failed, alt attribute not found. Error was found from INPUT element code: <input name="T$SearchBtn" id="T_SearchBtn" src="/instancedata/prime_product_julkaisu/samk/pics/searc .
    • Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
  5. Failed, alt attribute not found. Error was found from A element code: <a href="http://www.samk.fi/julkaisut" onclick="window.open('http://www.samk.fi/julkaisut');return f .
    • Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
  6. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- if(!navigator.cookieEnabled) { document.write("<div style=\" .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  7. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/embeds/5cc3f45eaee54f39941546c1e356471a68218247. .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  8. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/embeds/b43310657396f251c789d81cf5cd37f2c8c99947. .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  9. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/embeds/dc8f4c23bfd91d7c4555dc9fe174bd1458097204. .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  10. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/embeds/01286e7f268ea2c1d218189917bd90d95e63ac34. .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  11. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/pics/newsarrow.gif" alt=""> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  12. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/pics/newsarrow.gif" alt=""> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  13. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/pics/newsarrow.gif" alt=""> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  14. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/pics/newsarrow.gif" alt=""> .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  15. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/embeds/01502411d6615b96baa5af1d04cc6c3e85b7d4d8. .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  16. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/embeds/1f17ef0c7044ac8fcfd7ce5a7093c34a773cf431. .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  17. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/embeds/1e46bd27d112d75a5937eb9c72e7d4d74ace523c. .
    • Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
  18. Failed, alt attribute is empty. Error was found from IMG element code: <img src="/instancedata/prime_product_julkaisu/samk/embeds/b2a7bc575beb88f10d5f0352818c0d4ffe312aca. .
    • Please insert content for 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 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>
  20. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- _uacct="UA-3149314-1"; urchinTracker(); //--> </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

      Test result
      Passed

      5.2 - Associate data cells and header cells

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

      Guideline 6

      (show module information)

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

      (hide test results)
      1. Remark, 15 deprecated elements were found. Error was found from STYLE element code: <style type="text/css"> <!-- body { background-color: #009100; } div#pikalinkit { height: 210px; } d .
        • 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 (6)

      (hide test results)
      1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="/js/swfobject.js?120219720"></script> .
        • 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" src="/js/quicktime.js?96560880"></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"> //<![CDATA[ var theForm = document.forms['aspnetForm']; if (!theForm .
        • 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"> <!-- if(!navigator.cookieEnabled) { document.write("<div style=\" .
        • 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="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>
      6. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- _uacct="UA-3149314-1"; urchinTracker(); //--> </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 (6)

        (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="/js/swfobject.js?120219720"></script> .
          • 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" src="/js/quicktime.js?96560880"></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"> //<![CDATA[ var theForm = document.forms['aspnetForm']; if (!theForm .
          • 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"> <!-- if(!navigator.cookieEnabled) { document.write("<div style=\" .
          • 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="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.
        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 type="text/javascript"> <!-- _uacct="UA-3149314-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.
        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. (8)

              (hide test results)
              1. Failed, the color difference of rgb(0, 0, 0) and rgb(0, 145, 0) is too low. Error was found from BODY element code: <body> <form method="post" action="" id="aspnetForm" onsubmit="return true;"><div> <div> <input name .
                • Change the colors so that they have higher color difference.
              2. Failed, the brightness difference of rgb(0, 0, 0) and rgb(0, 145, 0) is too low. Error was found from BODY element code: <body> <form method="post" action="" id="aspnetForm" onsubmit="return true;"><div> <div> <input name .
                • Change the colors so that they have higher brightness difference.
              3. Failed, the color difference of rgb(0, 0, 0) and rgb(98, 105, 104) is too low. Error was found from DIV element code: <div id="pagelayout_shadow"> <div id="pagelayout"> <div id="header"> <div id="left_header"> .
                • Change the colors so that they have higher color difference.
              4. Failed, the brightness difference of rgb(0, 0, 0) and rgb(98, 105, 104) is too low. Error was found from DIV element code: <div id="pagelayout_shadow"> <div id="pagelayout"> <div id="header"> <div id="left_header"> .
                • Change the colors so that they have higher brightness difference.
              5. Failed, the color difference of rgb(0, 0, 0) and rgb(0, 168, 194) is too low. Error was found from DIV element code: <div id="footer"> <div id="omanvaenoikotiet"> <select onchange="window.open(this.options[this.se .
                • Change the colors so that they have higher color difference.
              6. Failed, the brightness difference of rgb(0, 0, 0) and rgb(0, 168, 194) is too low. Error was found from DIV element code: <div id="footer"> <div id="omanvaenoikotiet"> <select onchange="window.open(this.options[this.se .
                • Change the colors so that they have higher brightness difference.
              7. Failed, the color difference of rgb(0, 0, 0) and rgb(98, 105, 104) is too low. Error was found from DIV element code: <div></div> .
                • Change the colors so that they have higher color difference.
              8. Failed, the brightness difference of rgb(0, 0, 0) and rgb(98, 105, 104) is too low. Error was found from DIV element code: <div></div> .
                • Change the colors so that they have higher brightness difference.
              Test result
              Failed

              Guideline 4

              (show module information)

              4.2 - Acronyms and abbreviations. (7)

              (hide test results)
              1. Warning, potential abbreviation found: HAE. Error was found from TD element code: <td colspan="2">HAE</td> .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              2. Warning, potential abbreviation found: SAMK. Error was found from OPTION element code: <option value="https://owa.samk.fi/owa/">SAMK Webmail</option> .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              3. Warning, potential abbreviation found: SAMK. Error was found from OPTION element code: <option value="http://moodle.samk.fi/">SAMK Moodle</option> .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              4. Warning, potential abbreviation found: SAMK. Error was found from OPTION element code: <option value="http://www.samk.fi/virtualia">SAMK Virtualia</option> .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              5. Warning, potential abbreviation found: SAMK. Error was found from OPTION element code: <option value="https://kesy01.cc.spt.fi/intra/intra.nsf">SAMK Intranet (SAMK henkilökunta)</option> .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              6. Warning, potential abbreviation found: SAMK. Error was found from OPTION element code: <option value="https://193.166.40.45:8181/idm/user">SAMK-tunnus / vaihda salasana</option> .
                • Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
              7. Warning, potential abbreviation found: SAMK. Error was found from OPTION element code: <option value="https://oldmail.samk.fi/uwc/auth">SAMK Oldmail</option> .
                • 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 (5)

                (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 class="searchtable" border="0" cellpadding="0" cellspacing="0"> <tbody><tr><td colspan="2 .
                  • 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 width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><input name= .
                  • 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 id="timespaneventslisttable"> <tbody><tr> <td><div class="eventlistlinks"></div></td> <td id= .
                  • 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 style="white-space: nowrap;"> .
                  • 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> <div class="eventblock samkeventblock"> <div class="eventhead .
                  • 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 (9)

                    (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="/wEPDwUENTM4MQ9kFgJmD2QWAgIBD2QWCAIBDw8WAh4EVGV4dA .
                      • 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 id="T_SearchSiteRB" name="T$SearchType" value="SearchSiteRB" checked="checked" type="radio"> .
                      • 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, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input id="T_SearchStudiesRB" name="T$SearchType" value="SearchStudiesRB" type="radio"> .
                      • 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.
                    6. Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input id="T_SearchPersonRB" name="T$SearchType" value="SearchPersonRB" type="radio"> .
                      • 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.
                    7. 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="T$SearchText" id="T_SearchText" class="searchfield" type="text"> .
                      • 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.
                    8. 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="T$SearchBtn" id="T_SearchBtn" src="/instancedata/prime_product_julkaisu/samk/pics/searc .
                      • 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.
                    9. Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input style="display: none; visibility: hidden;" type="text"> .
                      • 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 (5)

                    (hide test results)
                    1. Remark, found table element(s). Error was found from TABLE element code: <table class="searchtable" border="0" cellpadding="0" cellspacing="0"> <tbody><tr><td colspan="2 .
                      • 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 width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><input name= .
                      • 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 id="timespaneventslisttable"> <tbody><tr> <td><div class="eventlistlinks"></div></td> <td id= .
                      • 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 style="white-space: nowrap;"> .
                      • 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> <div class="eventblock samkeventblock"> <div class="eventhead .
                      • 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) (2)

                    (hide test results)
                    1. Failed, no default text. Error was found from INPUT element code: <input name="T$SearchText" id="T_SearchText" class="searchfield" type="text"> .
                      • Add default text. Example: <input type="text" value="Write here" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-place-holders.
                    2. Failed, no default text. Error was found from INPUT element code: <input style="display: none; visibility: hidden;" type="text"> .
                      • 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 (4)

                    (hide test results)
                    1. Failed, link element a is too close to next one. Error was found from A element code: <a class="a" href="javascript:__doPostBack('T$ctl01','')">A</a> .
                      • 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.
                    2. Failed, link element a is too close to next one. Error was found from A element code: <a class="aa" href="javascript:__doPostBack('T$ctl02','')">A</a> .
                      • 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.
                    3. Failed, link element a is too close to next one. Error was found from A element code: <a href="/tyopaikat"><img src="/instancedata/prime_product_julkaisu/samk/embeds/01502411d6615b96baa5 .
                      • 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.
                    4. Failed, link element a is too close to next one. Error was found from A element code: <a href="http://samk.smartpage.fi/fi/agora_209/" onclick="window.open('http://samk.smartpage.fi/fi/a .
                      • 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 (4)

                        (hide test results)
                        1. Warning, no title in link. Error was found from LINK element code: <link rel="stylesheet" href="/css/screen?size=2&amp;front=1&amp;type=1" media="screen" type="text/cs .
                          • Add title for link.
                        2. Warning, no title in link. Error was found from LINK element code: <link rel="stylesheet" href="/css/print?size=2&amp;front=1&amp;type=1" media="print" type="text/css" .
                          • Add title for link.
                        3. Warning, no title in link. Error was found from LINK element code: <link rel="shortcut icon" href="http://www.samk.fi/instancedata/prime_product_julkaisu/samk/pics/fav .
                          • Add title for link.
                        4. Warning, no title in link. Error was found from LINK element code: <link rel="icon" href="http://www.samk.fi/instancedata/prime_product_julkaisu/samk/pics/favicon.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"> <!-- body { background-color: #009100; } div#pikalinkit { height: 210px; } d .
                            • Please use CSS rather than style element.
                          2. Warning, number of style attributes found: 12. Error was found from BODY element code: <body> <form method="post" action="" id="aspnetForm" onsubmit="return true;"><div> <div> <input name .
                            • 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.

                                Test result
                                Passed

                                3.4 - Relative over absolute.

                                  Test result
                                  Passed

                                  3.5 - Proper header usage.

                                  (hide test results)
                                  1. Warning, <h1> found 2 times. Error was found from H1 element code: <h1 class="channeltitle">Ajankohtaista</h1> .
                                    • Please consider using <h1> only once per page.
                                  Test result
                                  Warning

                                  3.6 - Proper List usage.

                                    Test result
                                    Passed

                                    3.7 - Proper quote usage.

                                    (hide test results)
                                    1. Remark, the number of quotation marks found: 12 Error was found from BODY element code: <body> <form method="post" action="" id="aspnetForm" onsubmit="return true;"><div> <div> <input name .
                                      • Please consider using <q> and <blockquote> for quotes.
                                    Test result
                                    Passed

                                    Guideline 5

                                    (show module information)

                                    5.3 - Table is used as layout (5)

                                    (hide test results)
                                    1. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="searchtable" border="0" cellpadding="0" cellspacing="0"> <tbody><tr><td colspan="2 .
                                      • 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 width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><input name= .
                                      • 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 id="timespaneventslisttable"> <tbody><tr> <td><div class="eventlistlinks"></div></td> <td id= .
                                      • 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 style="white-space: nowrap;"> .
                                      • 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> <div class="eventblock samkeventblock"> <div class="eventhead .
                                      • 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, 15 deprecated elements were found. Error was found from STYLE element code: <style type="text/css"> <!-- body { background-color: #009100; } div#pikalinkit { height: 210px; } d .
                                      • 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 (6)

                                    (hide test results)
                                    1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="/js/swfobject.js?120219720"></script> .
                                      • 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" src="/js/quicktime.js?96560880"></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"> //<![CDATA[ var theForm = document.forms['aspnetForm']; if (!theForm .
                                      • 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"> <!-- if(!navigator.cookieEnabled) { document.write("<div style=\" .
                                      • 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="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>
                                    6. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- _uacct="UA-3149314-1"; urchinTracker(); //--> </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 (19)

                                      (hide test results)
                                      1. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/4b616d70756b736574" onmouseover="src='/textimage/menulink_sel/4b616d70 .
                                        • If you use onmouseover, provide also redundant event handler: onfocus.
                                      2. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/4b69726a6173746f2d206a6120746965746f70616c76656c7574" onmouseover="src .
                                        • If you use onmouseover, provide also redundant event handler: onfocus.
                                      3. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/5665726b6b6f2d6f70696e6e6f74" onmouseover="src='/textimage/menulink_se .
                                        • If you use onmouseover, provide also redundant event handler: onfocus.
                                      4. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/54c3a47964656e6e79736b6f756c75747573" onmouseover="src='/textimage/men .
                                        • If you use onmouseover, provide also redundant event handler: onfocus.
                                      5. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/5972697479736b69696864797474c3a46dc3b6" onmouseover="src='/textimage/m .
                                        • If you use onmouseover, provide also redundant event handler: onfocus.
                                      6. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/537475647920696e20456e676c697368" onmouseover="src='/textimage/menulin .
                                        • If you use onmouseover, provide also redundant event handler: onfocus.
                                      7. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/41766f696e20414d4b" onmouseover="src='/textimage/menulink_sel/41766f69 .
                                        • If you use onmouseover, provide also redundant event handler: onfocus.
                                      8. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/4a756c6b616973756b6175707061" onmouseover="src='/textimage/menulink_se .
                                        • If you use onmouseover, provide also redundant event handler: onfocus.
                                      9. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/4b616d70756b736574" onmouseover="src='/textimage/menulink_sel/4b616d70 .
                                        • If you use onmouseout, provide also redundant event handler: onblur.
                                      10. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/4b69726a6173746f2d206a6120746965746f70616c76656c7574" onmouseover="src .
                                        • If you use onmouseout, provide also redundant event handler: onblur.
                                      11. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/5665726b6b6f2d6f70696e6e6f74" onmouseover="src='/textimage/menulink_se .
                                        • If you use onmouseout, provide also redundant event handler: onblur.
                                      12. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/54c3a47964656e6e79736b6f756c75747573" onmouseover="src='/textimage/men .
                                        • If you use onmouseout, provide also redundant event handler: onblur.
                                      13. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/5972697479736b69696864797474c3a46dc3b6" onmouseover="src='/textimage/m .
                                        • If you use onmouseout, provide also redundant event handler: onblur.
                                      14. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/537475647920696e20456e676c697368" onmouseover="src='/textimage/menulin .
                                        • If you use onmouseout, provide also redundant event handler: onblur.
                                      15. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/41766f696e20414d4b" onmouseover="src='/textimage/menulink_sel/41766f69 .
                                        • If you use onmouseout, provide also redundant event handler: onblur.
                                      16. Failed, found device independent event handler. Error was found from IMG element code: <img src="/textimage/menulink/4a756c6b616973756b6175707061" onmouseover="src='/textimage/menulink_se .
                                        • If you use onmouseout, provide also redundant event handler: onblur.
                                      17. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.samk.fi/julkaisut" onclick="window.open('http://www.samk.fi/julkaisut');return f .
                                        • If you use onclick, provide also redundant event handler: onkeypress.
                                      18. Failed, found device independent event handler. Error was found from A element code: <a href="http://samk.smartpage.fi/fi/agora_209/" onclick="window.open('http://samk.smartpage.fi/fi/a .
                                        • If you use onclick, provide also redundant event handler: onkeypress.
                                      19. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.satakorkea.fi/site.aspx?taso=1&amp;id=338" onclick="window.open('http://www.sata .
                                        • 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 (16)

                                                (hide test results)
                                                1. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from IMG element code: <img src="/textimage/menulink/4b616d70756b736574" onmouseover="src='/textimage/menulink_sel/4b616d70 .
                                                  • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                2. Failed, there is wrong tabindex. Error was found from IMG element code: <img src="/textimage/menulink/4b616d70756b736574" onmouseover="src='/textimage/menulink_sel/4b616d70 .
                                                  • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                3. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from IMG element code: <img src="/textimage/menulink/4b69726a6173746f2d206a6120746965746f70616c76656c7574" onmouseover="src .
                                                  • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                4. Failed, there is wrong tabindex. Error was found from IMG element code: <img src="/textimage/menulink/4b69726a6173746f2d206a6120746965746f70616c76656c7574" onmouseover="src .
                                                  • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                5. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from IMG element code: <img src="/textimage/menulink/5665726b6b6f2d6f70696e6e6f74" onmouseover="src='/textimage/menulink_se .
                                                  • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                6. Failed, there is wrong tabindex. Error was found from IMG element code: <img src="/textimage/menulink/5665726b6b6f2d6f70696e6e6f74" onmouseover="src='/textimage/menulink_se .
                                                  • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                7. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from IMG element code: <img src="/textimage/menulink/54c3a47964656e6e79736b6f756c75747573" onmouseover="src='/textimage/men .
                                                  • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                8. Failed, there is wrong tabindex. Error was found from IMG element code: <img src="/textimage/menulink/54c3a47964656e6e79736b6f756c75747573" onmouseover="src='/textimage/men .
                                                  • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                9. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from IMG element code: <img src="/textimage/menulink/5972697479736b69696864797474c3a46dc3b6" onmouseover="src='/textimage/m .
                                                  • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                10. Failed, there is wrong tabindex. Error was found from IMG element code: <img src="/textimage/menulink/5972697479736b69696864797474c3a46dc3b6" onmouseover="src='/textimage/m .
                                                  • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                11. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from IMG element code: <img src="/textimage/menulink/537475647920696e20456e676c697368" onmouseover="src='/textimage/menulin .
                                                  • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                12. Failed, there is wrong tabindex. Error was found from IMG element code: <img src="/textimage/menulink/537475647920696e20456e676c697368" onmouseover="src='/textimage/menulin .
                                                  • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                13. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from IMG element code: <img src="/textimage/menulink/41766f696e20414d4b" onmouseover="src='/textimage/menulink_sel/41766f69 .
                                                  • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                14. Failed, there is wrong tabindex. Error was found from IMG element code: <img src="/textimage/menulink/41766f696e20414d4b" onmouseover="src='/textimage/menulink_sel/41766f69 .
                                                  • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                15. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from IMG element code: <img src="/textimage/menulink/4a756c6b616973756b6175707061" onmouseover="src='/textimage/menulink_se .
                                                  • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                16. Failed, there is wrong tabindex. Error was found from IMG element code: <img src="/textimage/menulink/4a756c6b616973756b6175707061" onmouseover="src='/textimage/menulink_se .
                                                  • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                                Test result
                                                Failed

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

                                                  (hide test results)
                                                  1. Failed, wrong label usage. Error was found from INPUT element code: <input id="T_SearchSiteRB" name="T$SearchType" value="SearchSiteRB" checked="checked" type="radio"> .
                                                    • 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.
                                                  2. Failed, wrong label usage. Error was found from INPUT element code: <input id="T_SearchStudiesRB" name="T$SearchType" value="SearchStudiesRB" type="radio"> .
                                                    • 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.
                                                  3. Failed, wrong label usage. Error was found from INPUT element code: <input id="T_SearchPersonRB" name="T$SearchType" value="SearchPersonRB" type="radio"> .
                                                    • 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.
                                                  4. Failed, wrong label usage. Error was found from INPUT element code: <input name="T$SearchText" id="T_SearchText" class="searchfield" type="text"> .
                                                    • 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.
                                                  5. Failed, wrong label usage. Error was found from INPUT element code: <input name="T$SearchBtn" id="T_SearchBtn" src="/instancedata/prime_product_julkaisu/samk/pics/searc .
                                                    • 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.
                                                  6. Failed, wrong label usage. Error was found from INPUT element code: <input style="display: none; visibility: hidden;" type="text"> .
                                                    • 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.

                                                    Test result
                                                    Passed

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

                                                    (hide test results)
                                                    1. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="searchtable" border="0" cellpadding="0" cellspacing="0"> <tbody><tr><td colspan="2 .
                                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                                    2. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><input name= .
                                                      • 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 id="timespaneventslisttable"> <tbody><tr> <td><div class="eventlistlinks"></div></td> <td id= .
                                                      • 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 style="white-space: nowrap;"> .
                                                      • 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> <div class="eventblock samkeventblock"> <div class="eventhead .
                                                      • 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. Warning, <h1> found 2 times. Error was found from H1 element code: <h1 class="channeltitle">Ajankohtaista</h1> .
                                                      • Please consider using <h1> only once per page.
                                                    Test result
                                                    Failed

                                                    12.4 - Associating labels explicitly with their controls (6)

                                                    (hide test results)
                                                    1. Failed, input does not have label. Error was found from INPUT element code: <input id="T_SearchSiteRB" name="T$SearchType" value="SearchSiteRB" checked="checked" type="radio"> .
                                                      • Use label right before or after input and use for - id relationship or parentship.
                                                    2. Failed, input does not have label. Error was found from INPUT element code: <input id="T_SearchStudiesRB" name="T$SearchType" value="SearchStudiesRB" type="radio"> .
                                                      • Use label right before or after input and use for - id relationship or parentship.
                                                    3. Failed, input does not have label. Error was found from INPUT element code: <input id="T_SearchPersonRB" name="T$SearchType" value="SearchPersonRB" type="radio"> .
                                                      • Use label right before or after input and use for - id relationship or parentship.
                                                    4. Failed, input does not have label. Error was found from INPUT element code: <input name="T$SearchText" id="T_SearchText" class="searchfield" type="text"> .
                                                      • Use label right before or after input and use for - id relationship or parentship.
                                                    5. Failed, input does not have label. Error was found from INPUT element code: <input name="T$SearchBtn" id="T_SearchBtn" src="/instancedata/prime_product_julkaisu/samk/pics/searc .
                                                      • Use label right before or after input and use for - id relationship or parentship.
                                                    6. Failed, input does not have label. Error was found from INPUT element code: <input style="display: none; visibility: hidden;" type="text"> .
                                                      • 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 (3)

                                                    (hide test results)
                                                    1. Warning, found two identical name and title for two different links. Error was found from A element code: <a class="a" href="javascript:__doPostBack('T$ctl01','')">A</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 class="a" href="javascript:__doPostBack('T$ctl01','')">A</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 class="aa" href="javascript:__doPostBack('T$ctl02','')">A</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: , ,