ESOK-hanke 2006-2011

Foxability - Test results

Test results

Test results

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

Statistics for the evaluated page

Total tests: 47

TestsPercentTotalPercent
Total passed:3574.47%3512.20%
-Passed with remarks:1736.17%258.71%
Failed:1021.28%20972.82%
Warnings:24.26%186.27%
Total:47100.00%287100.00%

WCAG 1.0 A

Guideline 1

(show module information)

1.1 - Elements have text equivalents. (9)

(hide test results)
  1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="http://www.sydvast.fi/templates/default_sydvast_07/css_browser_selector.js" type="text/ .
    • 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"> <!-- function MM_jumpMenu(targ,selObj,restore){ //v3.0 eval(targ+" .
    • 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> function extcal_showOnBar(Str) { window.status=Str; return true; } </script> .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  4. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" language="javascript"> /******************************************** .
    • 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 language="JavaScript" type="text/javascript"> <!-- var prefix = '&#109;a' + 'i&#108;' + '& .
    • 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 language="JavaScript" type="text/javascript"> <!-- document.write( '<span style=\'display: .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  7. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="JavaScript" type="text/javascript"> <!-- document.write( '</' ); document.write .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  8. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script 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>
  9. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> _uacct = "UA-1729267-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, 11 deprecated elements were found. Error was found from LINK element code: <link href="http://www.sydvast.fi/templates/default_sydvast_07/css/template_css.css" rel="stylesheet .
        • 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 (9)

      (hide test results)
      1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="http://www.sydvast.fi/templates/default_sydvast_07/css_browser_selector.js" type="text/ .
        • 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"> <!-- function MM_jumpMenu(targ,selObj,restore){ //v3.0 eval(targ+" .
        • 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> function extcal_showOnBar(Str) { window.status=Str; return true; } </script> .
        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
      4. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" language="javascript"> /******************************************** .
        • 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 language="JavaScript" type="text/javascript"> <!-- var prefix = '&#109;a' + 'i&#108;' + '& .
        • 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 language="JavaScript" type="text/javascript"> <!-- document.write( '<span style=\'display: .
        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
      7. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="JavaScript" type="text/javascript"> <!-- document.write( '</' ); document.write .
        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
      8. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script 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>
      9. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> _uacct = "UA-1729267-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 (9)

        (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 src="http://www.sydvast.fi/templates/default_sydvast_07/css_browser_selector.js" type="text/ .
          • 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"> <!-- function MM_jumpMenu(targ,selObj,restore){ //v3.0 eval(targ+" .
          • 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> function extcal_showOnBar(Str) { window.status=Str; return true; } </script> .
          • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
        4. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script type="text/javascript" language="javascript"> /******************************************** .
          • 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 language="JavaScript" type="text/javascript"> <!-- var prefix = '&#109;a' + 'i&#108;' + '& .
          • 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 language="JavaScript" type="text/javascript"> <!-- document.write( '<span style=\'display: .
          • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
        7. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script language="JavaScript" type="text/javascript"> <!-- document.write( '</' ); document.write .
          • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
        8. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script 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.
        9. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script type="text/javascript"> _uacct = "UA-1729267-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 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. 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 H4 element code: <h4>Våra utbildningsprogram: <br> </h4> .
                      • Lower the header level to at least <h1>.
                    Test result
                    Failed

                    3.6 - Proper List usage.

                      Test result
                      Passed

                      3.7 - Proper quote usage.

                      (hide test results)
                      1. Remark, the number of quotation marks found: 178 Error was found from BODY element code: <body> <div id="header_1"></div> <div id="mother"> <div id="sizer"> <div id="expander"> .
                        • Please consider using <q> and <blockquote> for quotes.
                      Test result
                      Passed

                      Guideline 5

                      (show module information)

                      5.3 - Table is used as layout (16)

                      (hide test results)
                      1. Warning, a table may be used as a layout. Error was found from TABLE element code: <table width="96%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr align="left"><td><a href=" .
                        • 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 class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <form actio .
                        • 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 class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <div style=" .
                        • 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 class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <div id="ex .
                        • 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 style="border: 1px solid rgb(190, 194, 195); background-color: rgb(255, 255, 255);" align="ce .
                        • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                      6. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="extcal_navbar" width="96%" border="0" cellpadding="2" cellspacing="0"> <tbody><tr> .
                        • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                      7. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="extcal_weekdays" width="135" align="center" border="0" cellpadding="0" cellspacing="0" .
                        • Use proper ways of layout and use table only for data. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout.
                      8. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <th valign="top"> .
                        • 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.
                      9. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <a href="htt .
                        • 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.
                      10. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <th valign="top"> .
                        • 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.
                      11. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="blog" cellpadding="0" cellspacing="0"><tbody><tr><td valign="top"><div> <table class .
                        • 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.
                      12. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="contentpaneopen"> <tbody><tr> <td class="contentheading" width="96%"> .
                        • 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.
                      13. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="contentpaneopen"> <tbody><tr> <td colspan="2" valign="top"> <div style="bac .
                        • 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.
                      14. Warning, a table may be used as a layout. Error was found from TABLE element code: <table width="96%" cellpadding="0" cellspacing="0"><tbody><tr><td valign="top" width="96%"> <table .
                        • 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.
                      15. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="contentpaneopen"> <tbody><tr> <td class="contentheading" width="96%"> .
                        • 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.
                      16. Warning, a table may be used as a layout. Error was found from TABLE element code: <table class="contentpaneopen"> <tbody><tr> <td colspan="2" valign="top"> <a href="http:/ .
                        • 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, 11 deprecated elements were found. Error was found from LINK element code: <link href="http://www.sydvast.fi/templates/default_sydvast_07/css/template_css.css" rel="stylesheet .
                        • 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 (9)

                      (hide test results)
                      1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="http://www.sydvast.fi/templates/default_sydvast_07/css_browser_selector.js" type="text/ .
                        • 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"> <!-- function MM_jumpMenu(targ,selObj,restore){ //v3.0 eval(targ+" .
                        • 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> function extcal_showOnBar(Str) { window.status=Str; return true; } </script> .
                        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                      4. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" language="javascript"> /******************************************** .
                        • 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 language="JavaScript" type="text/javascript"> <!-- var prefix = '&#109;a' + 'i&#108;' + '& .
                        • 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 language="JavaScript" type="text/javascript"> <!-- document.write( '<span style=\'display: .
                        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                      7. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="JavaScript" type="text/javascript"> <!-- document.write( '</' ); document.write .
                        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                      8. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script 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>
                      9. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> _uacct = "UA-1729267-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 (80)

                        (hide test results)
                        1. Failed, found device independent event handler. Error was found from TD element code: <td onmouseover="extcal_showOnBar('Maj 2009');return true;" onmouseout="extcal_showOnBar('');return .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        2. Failed, found device independent event handler. Error was found from TD element code: <td onmouseover="extcal_showOnBar('Juli 2009');return true;" onmouseout="extcal_showOnBar('');return .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        3. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 23');return true;" onmouseout="extc .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        4. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('01-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        5. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('02-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        6. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('03-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        7. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('04-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        8. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('05-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        9. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('06-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        10. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('07-jun-2009');return true;" onmouseout= .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        11. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 24');return true;" onmouseout="extc .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        12. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('08-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        13. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_todaycell" onmouseover="extcal_showOnBar('09-jun-2009');return true;" onmouseout=" .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        14. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('10-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        15. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('11-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        16. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('12-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        17. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('13-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        18. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('14-jun-2009');return true;" onmouseout= .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        19. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 25');return true;" onmouseout="extc .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        20. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('15-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        21. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('16-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        22. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('17-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        23. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('18-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        24. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('19-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        25. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('20-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        26. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('21-jun-2009');return true;" onmouseout= .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        27. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 26');return true;" onmouseout="extc .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        28. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('22-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        29. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('23-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        30. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('24-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        31. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('25-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        32. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('26-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        33. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('27-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        34. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('28-jun-2009');return true;" onmouseout= .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        35. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 27');return true;" onmouseout="extc .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        36. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('29-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        37. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('30-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseover, provide also redundant event handler: onfocus.
                        38. Failed, found device independent event handler. Error was found from TD element code: <td onmouseover="extcal_showOnBar('Maj 2009');return true;" onmouseout="extcal_showOnBar('');return .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        39. Failed, found device independent event handler. Error was found from TD element code: <td onmouseover="extcal_showOnBar('Juli 2009');return true;" onmouseout="extcal_showOnBar('');return .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        40. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 23');return true;" onmouseout="extc .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        41. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('01-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        42. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('02-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        43. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('03-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        44. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('04-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        45. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('05-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        46. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('06-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        47. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('07-jun-2009');return true;" onmouseout= .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        48. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 24');return true;" onmouseout="extc .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        49. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('08-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        50. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_todaycell" onmouseover="extcal_showOnBar('09-jun-2009');return true;" onmouseout=" .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        51. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('10-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        52. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('11-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        53. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('12-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        54. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('13-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        55. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('14-jun-2009');return true;" onmouseout= .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        56. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 25');return true;" onmouseout="extc .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        57. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('15-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        58. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('16-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        59. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('17-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        60. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('18-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        61. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('19-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        62. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('20-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        63. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('21-jun-2009');return true;" onmouseout= .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        64. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 26');return true;" onmouseout="extc .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        65. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('22-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        66. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('23-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        67. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('24-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        68. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('25-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        69. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('26-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        70. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('27-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        71. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('28-jun-2009');return true;" onmouseout= .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        72. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 27');return true;" onmouseout="extc .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        73. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('29-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        74. Failed, found device independent event handler. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('30-jun-2009');return true;" onmouseout="ex .
                          • If you use onmouseout, provide also redundant event handler: onblur.
                        75. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;do_pdf=1&amp;id=2" target="_blank" .
                          • If you use onclick, provide also redundant event handler: onkeypress.
                        76. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;task=view&amp;id=2&amp;pop=1&amp;pa .
                          • If you use onclick, provide also redundant event handler: onkeypress.
                        77. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;task=emailform&amp;id=2" target="_b .
                          • If you use onclick, provide also redundant event handler: onkeypress.
                        78. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;do_pdf=1&amp;id=237" target="_blank .
                          • If you use onclick, provide also redundant event handler: onkeypress.
                        79. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;task=view&amp;id=237&amp;pop=1&amp; .
                          • If you use onclick, provide also redundant event handler: onkeypress.
                        80. Failed, found device independent event handler. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;task=emailform&amp;id=237" target=" .
                          • 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 (74)

                                  (hide test results)
                                  1. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td onmouseover="extcal_showOnBar('Maj 2009');return true;" onmouseout="extcal_showOnBar('');return .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  2. Failed, there is wrong tabindex. Error was found from TD element code: <td onmouseover="extcal_showOnBar('Maj 2009');return true;" onmouseout="extcal_showOnBar('');return .
                                    • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  3. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td onmouseover="extcal_showOnBar('Juli 2009');return true;" onmouseout="extcal_showOnBar('');return .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  4. Failed, there is wrong tabindex. Error was found from TD element code: <td onmouseover="extcal_showOnBar('Juli 2009');return true;" onmouseout="extcal_showOnBar('');return .
                                    • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  5. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 23');return true;" onmouseout="extc .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  6. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 23');return true;" onmouseout="extc .
                                    • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  7. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('01-jun-2009');return true;" onmouseout="ex .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  8. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('01-jun-2009');return true;" onmouseout="ex .
                                    • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  9. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('02-jun-2009');return true;" onmouseout="ex .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  10. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('02-jun-2009');return true;" onmouseout="ex .
                                    • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  11. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('03-jun-2009');return true;" onmouseout="ex .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  12. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('03-jun-2009');return true;" onmouseout="ex .
                                    • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  13. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('04-jun-2009');return true;" onmouseout="ex .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  14. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('04-jun-2009');return true;" onmouseout="ex .
                                    • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  15. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('05-jun-2009');return true;" onmouseout="ex .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  16. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('05-jun-2009');return true;" onmouseout="ex .
                                    • Tabindex have to be a number. Tabindex is not valid in all element, but keyboard can access only elements that have tabindex atribute. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  17. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('06-jun-2009');return true;" onmouseout="ex .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  18. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('06-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  19. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('07-jun-2009');return true;" onmouseout= .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  20. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('07-jun-2009');return true;" onmouseout= .
                                    • 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.
                                  21. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 24');return true;" onmouseout="extc .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  22. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 24');return true;" onmouseout="extc .
                                    • 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.
                                  23. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('08-jun-2009');return true;" onmouseout="ex .
                                    • Change event to onmouseup, onmousedown or onclick, so it is easy to add onkeyup or onkeydown events for keyboard. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events.
                                  24. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('08-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  25. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_todaycell" onmouseover="extcal_showOnBar('09-jun-2009');return true;" onmouseout=" .
                                    • 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.
                                  26. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_todaycell" onmouseover="extcal_showOnBar('09-jun-2009');return true;" onmouseout=" .
                                    • 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.
                                  27. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('10-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  28. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('10-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  29. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('11-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  30. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('11-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  31. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('12-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  32. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('12-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  33. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('13-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  34. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('13-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  35. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('14-jun-2009');return true;" onmouseout= .
                                    • 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.
                                  36. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('14-jun-2009');return true;" onmouseout= .
                                    • 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.
                                  37. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 25');return true;" onmouseout="extc .
                                    • 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.
                                  38. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 25');return true;" onmouseout="extc .
                                    • 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.
                                  39. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('15-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  40. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('15-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  41. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('16-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  42. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('16-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  43. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('17-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  44. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('17-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  45. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('18-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  46. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('18-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  47. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('19-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  48. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('19-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  49. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('20-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  50. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('20-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  51. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('21-jun-2009');return true;" onmouseout= .
                                    • 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.
                                  52. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('21-jun-2009');return true;" onmouseout= .
                                    • 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.
                                  53. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 26');return true;" onmouseout="extc .
                                    • 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.
                                  54. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 26');return true;" onmouseout="extc .
                                    • 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.
                                  55. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('22-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  56. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('22-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  57. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('23-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  58. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('23-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  59. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('24-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  60. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('24-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  61. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('25-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  62. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('25-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  63. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('26-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  64. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('26-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  65. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('27-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  66. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('27-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  67. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('28-jun-2009');return true;" onmouseout= .
                                    • 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.
                                  68. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_sundaycell" onmouseover="extcal_showOnBar('28-jun-2009');return true;" onmouseout= .
                                    • 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.
                                  69. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 27');return true;" onmouseout="extc .
                                    • 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.
                                  70. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_weekcell" onmouseover="extcal_showOnBar('Vecka 27');return true;" onmouseout="extc .
                                    • 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.
                                  71. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('29-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  72. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('29-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  73. Failed, onmouseover, onmouseout and onmousemove are difficult to define for keyboard, so change those events to keyboard accessible. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('30-jun-2009');return true;" onmouseout="ex .
                                    • 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.
                                  74. Failed, there is wrong tabindex. Error was found from TD element code: <td class="extcal_daycell" onmouseover="extcal_showOnBar('30-jun-2009');return true;" onmouseout="ex .
                                    • 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 (8)

                                  (hide test results)
                                  1. Failed, page opens in new window. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;do_pdf=1&amp;id=2" target="_blank" .
                                    • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                                  2. Failed, page opens in new window. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;task=view&amp;id=2&amp;pop=1&amp;pa .
                                    • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                                  3. Failed, page opens in new window. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;task=emailform&amp;id=2" target="_b .
                                    • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                                  4. Failed, page opens in new window. Error was found from A element code: <a id="fm_file" href="http://www.sydvast.fi/images/stories/ansokan/guide0708m.pdf" target="_blank" t .
                                    • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                                  5. Failed, page opens in new window. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;do_pdf=1&amp;id=237" target="_blank .
                                    • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                                  6. Failed, page opens in new window. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;task=view&amp;id=237&amp;pop=1&amp; .
                                    • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                                  7. Failed, page opens in new window. Error was found from A element code: <a href="http://www.sydvast.fi/index2.php?option=com_content&amp;task=emailform&amp;id=237" target=" .
                                    • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                                  8. Failed, page opens in new window. Error was found from A element code: <a href="http://celtigo.sydvast.fi/studentbostader/" target="_blank"> <div style="width: 100%; backg .
                                    • Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
                                  Test result
                                  Failed

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

                                  (hide test results)
                                  1. Failed, wrong label usage. Error was found from INPUT element code: <input name="searchword" id="mod_search_searchword" maxlength="20" alt="search" class="inputbox" siz .
                                    • 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 (18)

                                    (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 H4 element code: <h4>Våra utbildningsprogram: <br> </h4> .
                                      • Lower the header level to at least <h1>.
                                    2. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table width="96%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr align="left"><td><a href=" .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    3. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <form actio .
                                      • 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 class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <div style=" .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    5. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <div id="ex .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    6. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table style="border: 1px solid rgb(190, 194, 195); background-color: rgb(255, 255, 255);" align="ce .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    7. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="extcal_navbar" width="96%" border="0" cellpadding="2" cellspacing="0"> <tbody><tr> .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    8. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="extcal_weekdays" width="135" align="center" border="0" cellpadding="0" cellspacing="0" .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    9. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <th valign="top"> .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    10. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <a href="htt .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    11. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="moduletable" cellpadding="0" cellspacing="0"> <tbody><tr> <th valign="top"> .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    12. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="blog" cellpadding="0" cellspacing="0"><tbody><tr><td valign="top"><div> <table class .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    13. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="contentpaneopen"> <tbody><tr> <td class="contentheading" width="96%"> .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    14. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="contentpaneopen"> <tbody><tr> <td colspan="2" valign="top"> <div style="bac .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    15. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table width="96%" cellpadding="0" cellspacing="0"><tbody><tr><td valign="top" width="96%"> <table .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    16. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="contentpaneopen"> <tbody><tr> <td class="contentheading" width="96%"> .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    17. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="contentpaneopen"> <tbody><tr> <td colspan="2" valign="top"> <a href="http:/ .
                                      • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                    18. Warning, there are too many (20 or more) option in select that are not grouped. Error was found from SELECT element code: <select style="width: 150px;" name="select" onchange="MM_jumpMenu('parent',this,0)"> <option value .
                                      • Group option-elements by optgroup-element to logic and semantic groups that are easy to understand.
                                    Test result
                                    Failed

                                    12.4 - Associating labels explicitly with their controls

                                    (hide test results)
                                    1. Failed, input does not have label. Error was found from INPUT element code: <input name="searchword" id="mod_search_searchword" maxlength="20" alt="search" class="inputbox" siz .
                                      • 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

                                    (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.yhansokan.fi"> </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: , ,