Foxability - Test results

Test results

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

Statistics for the evaluated page

Total tests: 64

	Tests	Percent	Total	Percent
Total passed:	50	78.13%	50	44.25%
-Passed with remarks:	20	31.25%	23	20.35%
Failed:	9	14.06%	25	22.12%
Warnings:	5	7.81%	15	13.27%
Total:	64	100.00%	113	100.00%

MobileOK

WCAG

Guideline 1

(show module information)

1.1 - Elements have text equivalents. (4)

(hide test results)

Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="http://www.jyu.fi/portal_javascripts/JyuStyle-tyyli/ploneScripts .
- Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"><!-- /* - analytics.js - */ // http://www.jyu.fi/portal_javascripts .
- Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
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>
Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"><!-- startList = function() { .
- 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)

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)

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

Test result: Passed

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

Test result: Passed

Guideline 2

(show module information)

2.1 - Information is conveyed even without colors.

(hide test results)

Remark, ensure that all information conveyed with color is also available without color, for example from context or markup.

Test result: Passed

2.2 - Colors are visible.

Test result: Passed

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

(hide test results)

Failed, absolute size definition found. #portal-top:"border-bottom: 8px solid rgb(228, 233, 238)". Error was found from STYLE element code: <style type="text/css" media="all"> body { background: url(http://www.jyu.fi/bg_liuku.jpg) top left .
- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
Failed, absolute size definition found. #page-heading:"height: 35px". Error was found from STYLE element code: <style type="text/css" media="all"> body { background: url(http://www.jyu.fi/bg_liuku.jpg) top left .
- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
Failed, absolute size definition found. #tiedekunnat:"height: 126px". Error was found from STYLE element code: <style type="text/css" media="all"> body { background: url(http://www.jyu.fi/bg_liuku.jpg) top left .
- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
Failed, absolute size definition found. #portal-column-one:"width: 150px". Error was found from STYLE element code: <style type="text/css" media="screen"> <!-- body { .
- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
Failed, absolute size definition found. #portal-column-two:"width: 160px". Error was found from STYLE element code: <style type="text/css" media="screen"> <!-- body { .
- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
Failed, absolute size definition found. #dropdown-wrapper:"border-top: 8px solid rgb(231, 236, 242)". Error was found from STYLE element code: <style type="text/css" media="screen"> <!-- body { .
- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
Failed, absolute size definition found. #portal-globalnav li a:"padding: 0.3em 5px". Error was found from STYLE element code: <style type="text/css" media="screen"> <!-- body { .
- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
Failed, absolute size definition found. #dropdown:"margin-left: -19px". Error was found from STYLE element code: <style type="text/css" media="screen"> <!-- body { .
- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
Failed, absolute size definition found. li.ddmain:"height: 20px". Error was found from STYLE element code: <style type="text/css" media="screen"> <!-- body { .
- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
Failed, absolute size definition found. #indeximage:"height: 160px". Error was found from STYLE element code: <style type="text/css" media="screen"> <!-- body { .
- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"

Test result: Failed

3.5 - Proper header usage.

(hide test results)

Failed, improper header nesting: Header levels must not increase by more than one level per heading. Do not use headers to create font effects; use style sheets to change font styles. Error was found from H5 element code: <h5 class="hiddenStructure">Osiot</h5> .
- Lower the header level to at least <h2>.

Test result: Failed

3.6 - Proper List usage. (2)

(hide test results)

Failed, a list without list items found. Error was found from DL element code: <dl id="portlet-avoimetvirat"> <dt> .
- List element <dl> should contain at least one list item <li>.
Failed, a list without list items found. Error was found from DL element code: <dl id="portlet-events"> <dd class="avoinev .
- List element <dl> should contain at least one list item <li>.

Test result: Failed

3.7 - Proper quote usage.

Test result: Passed

Guideline 4

(show module information)

4.1 - Language changes are identified.

(hide test results)

Remark, if multiple languages are used in the document, clearly identify changes in the natural language of the document's text.
- Use the "lang" or "xml:lang" attribute to identify any changes in language. For example: Galileo said quietly: <q lang="it">Eppur si muove</q>

Test result: Passed

4.2 - Acronyms and abbreviations. (7)

(hide test results)

Warning, potential abbreviation found: JYY. Error was found from A element code: <a title="Jyväskylän yliopiston ylioppilaskunta" href="http://www.jyy.fi/">Ylioppilaskunta, JYY</a> .
- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
Warning, potential abbreviation found: TUTKA. Error was found from A element code: <a href="http://tutka.jyu.fi/tutka/">TUTKA-tutkimusrekisteri</a> .
- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
Warning, potential abbreviation found: MBA. Error was found from A element code: <a class="external-link" href="http://www.cec.jyu.fi/avance/mba">MBA-ohjelma</a> .
- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
Warning, potential abbreviation found: TTK. Error was found from A element code: <a href="http://www.jyu.fi/ajankohtaista/tiedotteet/tiedote-2008-04-07-15-48-17-882805">3 tohtorikou .
- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
Warning, potential abbreviation found: TTK. Error was found from A element code: <a href="http://www.jyu.fi/ajankohtaista/tiedotteet/tiedote-2008-04-07-15-45-27-581585">Lehtorin ja .
- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
Warning, potential abbreviation found: MLTK. Error was found from A element code: <a href="http://www.jyu.fi/ajankohtaista/tiedotteet/tiedote-2008-04-07-15-40-47-780832">Yliassistent .
- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
Warning, potential abbreviation found: KTL. Error was found from A element code: <a href="http://www.jyu.fi/ajankohtaista/tiedotteet/tiedote-2008-03-31-11-01-41-810622">Professorin .
- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>

Test result: Warning

4.3 - Primary language.

Test result: Passed

Guideline 5

(show module information)

5.1 - Table used properly

Test result: Passed

5.2 - Associate data cells and header cells

(hide test results)

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

Test result: Passed

5.3 - Table is used as layout

Test result: Passed

5.5 - Summary, caption and title in table

(hide test results)

Warning, one of the next three items was not used in a table: caption, summary and title. Error was found from TABLE element code: <table id="portal-columns" title="Columns for layout" summary="Columns for layout"> .
- Use caption, summary and title in a table. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmas calendar. Shows how many days is left before Christmas."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.

Test result: Warning

5.6 - Abbr used in long table headers names

Test result: Passed

Guideline 6

(show module information)

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

(hide test results)

Remark, 12 deprecated elements were found. Error was found from STYLE element code: <style type="text/css"><!-- @import url(http://www.jyu.fi/portal_css/JyuStyle-tyyli/ploneStyles3742. .
- 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 (4)

(hide test results)

Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript" src="http://www.jyu.fi/portal_javascripts/JyuStyle-tyyli/ploneScripts .
- Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"><!-- /* - analytics.js - */ // http://www.jyu.fi/portal_javascripts .
- Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
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>
Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"><!-- startList = function() { .
- Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>

Test result: Failed

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

Test result: Passed

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

Test result: Passed

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

Test result: Passed

Guideline 7

(show module information)

7.1 - Avoid causing the screen to flicker

(hide test results)

Remark, until user agents allow users to control flickering, avoid causing the screen to flicker. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-flicker.

Test result: Passed

7.2 - Blink and marquee usage

Test result: Passed

7.3 - Avoid movement in page

(hide test results)

Remark, until user agents allow users to freeze moving content, avoid movement in pages. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-movement.

Test result: Passed

7.4 - Periodically auto-refreshing pages

Test result: Passed

7.5 - Autoredirection

Test result: Passed

Guideline 8

(show module information)

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

(hide test results)

Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script type="text/javascript" src="http://www.jyu.fi/portal_javascripts/JyuStyle-tyyli/ploneScripts .
- Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script type="text/javascript"><!-- /* - analytics.js - */ // http://www.jyu.fi/portal_javascripts .
- Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
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.
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"><!-- startList = function() { .
- Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.

Test result: Passed

Guideline 9

(show module information)

9.1 - Client-side versus server-side image maps

Test result: Passed

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

Test result: Passed

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

Test result: Passed

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

Test result: Passed

9.5 - Keyboard shortcuts (2)

(hide test results)

Warning, accesskey should be used for inputs whose type is submit, button or reset. Error was found from INPUT element code: <input class="searchButton" value="Hae" type="submit"> .
- Accesskey can be defined for label of input or stright to input. Best ways (example): <label for="name" accesskey="N">Name</label><input id="name" type="text" /> or <input type="button" accesskey="B" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts.
Warning, accesskey should be used for inputs whose type is submit, button or reset. Error was found from INPUT element code: <input class="goButton" value="Go" type="submit"> .
- Accesskey can be defined for label of input or stright to input. Best ways (example): <label for="name" accesskey="N">Name</label><input id="name" type="text" /> or <input type="button" accesskey="B" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts.

Test result: Warning

Guideline 10

(show module information)

10.1 - No pop-ups or other windows

Test result: Passed

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

Test result: Passed

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

(hide test results)

Remark, found table element(s). Error was found from TABLE element code: <table id="portal-columns" title="Columns for layout" summary="Columns for layout"> .
- Verify that a linearized version of tables used for layout is provided. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables

Test result: Passed

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

(hide test results)

Failed, no default text. Error was found from INPUT element code: <input id="searchGadget" name="SearchableText" size="15" title="Etsi sivustolta" accesskey="4" class .
- Add default text. Example: <input type="text" value="Write here" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-place-holders.

Test result: Failed

10.5 - Non-link, printable characters

(hide test results)

Failed, link element a is too close to next one. Error was found from A element code: <a class="hiddenStructure" accesskey="2" href="http://www.jyu.fi/#documentContent">Hyppää sisältöön. .
- Separate links by some element or "whitespace - Some character(s) - whitespase". Examples:...<a href="page7.html">Prew</a> | <a href="page.html9">Next</a>... or...<a href="page7.html">Prew</a> <br /> <a href="page.html9">Next</a>... or...<li><a href="page7.html">Prew</a></li><li><a href="page.html9">Next</a></li>... More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-divide-links.

Test result: Failed

Guideline 11

(show module information)

11.1 - Use of W3C technologies

(hide test results)

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

Test result: Passed

11.2 - Avoid using deprecated features of W3C technologies.

Test result: Passed

11.3 - Provide information

(hide test results)

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

Test result: Passed

11.4 - Accessible page

(hide test results)

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

Test result: Passed

Guideline 12

(show module information)

12.1 - Providing a frame title

Test result: Passed

12.2 - Describe the purpose of frames

(hide test results)

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

(hide test results)

Failed, Improper header nesting: Header levels must not increase by more than one level per heading. Do not use headers to create font effects; use style sheets to change font styles. Error was found from H5 element code: <h5 class="hiddenStructure">Osiot</h5> .
- Lower the header level to at least <h2>.
Warning, in table should be used all of next three: caption, summary and title. Error was found from TABLE element code: <table id="portal-columns" title="Columns for layout" summary="Columns for layout"> .
- Use in table all three: content, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.

Test result: Failed

12.4 - Associating labels explicitly with their controls

Test result: Passed

Guideline 13

(show module information)

13.1 - Target of each link

(hide test results)

Warning, found two identical name and title for two different links. Error was found from A element code: <a href="http://www.jyu.fi/ajankohtaista" class="portletMore"> .
- 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)

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)

Remark, use navigation mechanisms in a consistent manner. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-clear-nav-mechanism.

Test result: Passed

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

Test result: Passed

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

Test result: Passed

13.7 - Different types of searches

(hide test results)

Remark, if search functions are provided, enable different types of searches for different skill levels and preferences. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-searches.

Test result: Passed

13.8 - Information at the beginning

(hide test results)

Remark, place distinguishing information at the beginning of headings, paragraphs, lists, etc. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-front-loading.

Test result: Passed

13.9 - Working links (2)

(hide test results)

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

Test result: Failed

13.10 - Skipping over multi-line ASCII art

Test result: Passed

Guideline 14

(show module information)

14.1 - Clear and simple language.

(hide test results)

Remark, use the clearest and simplest language appropriate for a site's content.

Test result: Passed

14.2 - Supplement text with presentations.

(hide test results)

Remark, supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.

Test result: Passed

14.3 - No style element, no style attributes. (2)

(hide test results)

Warning, style element found. Error was found from STYLE element code: <style type="text/css"><!-- @import url(http://www.jyu.fi/portal_css/JyuStyle-tyyli/ploneStyles3742. .
- Please use CSS rather than style element.
Warning, number of style attributes found: 3. Error was found from BODY element code: <body class="section-etusivu"> <div id="visual-portal-wrapper"> .
- Please use CSS rather than style attributes.

Test result: Warning

ESOK-hanke 2006-2011

Foxability - Test results

Test results

MobileOK

WCAG

Guideline 1

1.1 - Elements have text equivalents. (4)

1.2 - A serverside Image map without an alternative textlink

1.3 - Auditory descriptions for visual tracks.

1.4 - Equivalent alternatives for time based multimedia.

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

Guideline 2

2.1 - Information is conveyed even without colors.

2.2 - Colors are visible.

Guideline 3

3.1 - MathML

3.2 - Formal grammars.

3.3 - Proper font stylings.

3.4 - Relative over absolute. (10)

3.5 - Proper header usage.

3.6 - Proper List usage. (2)

3.7 - Proper quote usage.

Guideline 4

4.1 - Language changes are identified.

4.2 - Acronyms and abbreviations. (7)

4.3 - Primary language.

Guideline 5

5.1 - Table used properly

5.2 - Associate data cells and header cells

5.3 - Table is used as layout

5.5 - Summary, caption and title in table

5.6 - Abbr used in long table headers names

Guideline 6

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

6.2 - Ensure that equivalents for dynamic content are updated when thedynamic content changes (4)

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

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

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

Guideline 7

7.1 - Avoid causing the screen to flicker

7.2 - Blink and marquee usage

7.3 - Avoid movement in page

7.4 - Periodically auto-refreshing pages

7.5 - Autoredirection

Guideline 8

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

Guideline 9

9.1 - Client-side versus server-side image maps

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

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

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

9.5 - Keyboard shortcuts (2)

Guideline 10

10.1 - No pop-ups or other windows

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

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

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

10.5 - Non-link, printable characters

Guideline 11

11.1 - Use of W3C technologies

11.2 - Avoid using deprecated features of W3C technologies.

11.3 - Provide information

11.4 - Accessible page

Guideline 12

12.1 - Providing a frame title

12.2 - Describe the purpose of frames

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

12.4 - Associating labels explicitly with their controls

Guideline 13

13.1 - Target of each link

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

13.3 - Information about the general layout

13.4 - Navigation mechanisms

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

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

13.7 - Different types of searches

13.8 - Information at the beginning

13.9 - Working links (2)

13.10 - Skipping over multi-line ASCII art

Guideline 14