Foxability - Test results

Test results

Test subject: http://www.turkuamk.fi/public/default.aspx?nodeid=7563&contentlan=1&culture=fi-FI

Statistics for the evaluated page

Total tests: 67

	Tests	Percent	Total	Percent
Total passed:	46	68.66%	46	31.94%
-Passed with remarks:	21	31.34%	29	20.14%
Failed:	12	17.91%	36	25.00%
Warnings:	9	13.43%	33	22.92%
Total:	67	100.00%	144	100.00%

WCAG 1.0 A

Guideline 1

(show module information)

1.1 - Elements have text equivalents. (3)

(hide test results)

Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="javascript" type="text/javascript"> <!-- // Hide from older browsers. var da = .
- Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
Failed, alt attribute not found. Error was found from IMG element code: <img src="/Public/gfx/gfx_1/amk/turku-logo.gif" vspace="20" border="0"> .
- Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
Failed, <object> is missing text content. Error was found from OBJECT element code: <object data="download.aspx?id=78874&guid={8C3E21C8-2BC5-480B-91D4-A7DDEB1710B3}" type="applicat .
- Insert text content for <object>. For example: <object>A representation about peak oil.</object>

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

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

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

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

Guideline 6

(show module information)

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

(hide test results)

Remark, 11 deprecated elements were found. Error was found from LINK element code: <link rel="stylesheet" type="text/css" media="screen" href="/public/gfx/gfx_1/amk/screen3.css"> .
- 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 (2)

(hide test results)

Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="javascript" type="text/javascript"> <!-- // Hide from older browsers. var da = .
- Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
Failed, <object> is missing text content. Error was found from OBJECT element code: <object data="download.aspx?id=78874&guid={8C3E21C8-2BC5-480B-91D4-A7DDEB1710B3}" type="applicat .
- Insert text content for <object>. For example: <object>A representation about peak oil.</object>

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)

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

(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 language="javascript" type="text/javascript"> <!-- // Hide from older browsers. var da = .
- 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 OBJECT element code: <object data="download.aspx?id=78874&guid={8C3E21C8-2BC5-480B-91D4-A7DDEB1710B3}" type="applicat .
- 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)

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)

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

Test result: Passed

WCAG 1.0 AAA

Guideline 1

(show module information)

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

Test result: Passed

Guideline 2

(show module information)

2.2 - Colors are visible.

Test result: Passed

Guideline 4

(show module information)

4.2 - Acronyms and abbreviations. (3)

(hide test results)

Warning, potential abbreviation found: AMK. Error was found from A element code: <a href="default.aspx?contentid=132516&nodeid=7563">Turun AMK:n opiskeluterveydenhuolto muuttaa< .
- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
Warning, potential abbreviation found: AMK. Error was found from A element code: <a href="default.aspx?contentid=132035&nodeid=7563">Tiedote: Turun AMK mukaan rakennusalan FINED .
- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
Warning, potential abbreviation found: FINEDU. Error was found from A element code: <a href="default.aspx?contentid=132035&nodeid=7563">Tiedote: Turun AMK mukaan rakennusalan FINED .
- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>

Test result: Warning

4.3 - Primary language.

(hide test results)

Failed, no xml:lang attribute found. Error was found from HTML element code: <html xmlns="http://www.w3.org/1999/xhtml"><head> <meta http-equiv="Content-Type" content= .
- Insert xml:lang attribute to specify language used. For example: <html xml:lang="fi">

Test result: Failed

Guideline 5

(show module information)

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

(hide test results)

Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr><td id="topstripe .
- Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> .
- Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><h1 class="forBra .
- Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> .
- Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table width="250" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><h1 class="forBrai .
- Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table id="lift" width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td class=" .
- Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table width="250" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <span><span .
- Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
Failed, at least two of next three items must be used in a table: caption, summary and title. Error was found from TABLE element code: <table width="123" align="center" background="download.aspx?ID=72642&GUID={8606BA9B-C060-4676-99 .
- Use at least two of the next three items in a table: caption, summary and title. The caption is an element of the table. Summary and title are attributes of the table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.

Test result: Failed

5.6 - Abbr used in long table headers names

Test result: Passed

Guideline 9

(show module information)

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

(hide test results)

Warning, needed taborder has not been defined. Error was found from OBJECT element code: <object data="download.aspx?id=78874&guid={8C3E21C8-2BC5-480B-91D4-A7DDEB1710B3}" type="applicat .
- Elements a, area, button, input, object, select and textarea need attribute tabindex that is greater than 0. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-tab-order.

Test result: Warning

9.5 - Keyboard shortcuts (8)

(hide test results)

Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input name="ctl00$Topbar1$ctl03$SearchText" id="ctl00_Topbar1_ctl03_SearchText" style="width: 120px .
- 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, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input name="TemplateID" value="28" type="radio"> .
- Accesskey can be defined for label of input or stright to input. Best ways (example): <label for="name" accesskey="N">Name</label><input id="name" type="text" /> or <input type="button" accesskey="B" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts.
Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input name="TemplateID" value="" checked="checked" type="radio"> .
- Accesskey can be defined for label of input or stright to input. Best ways (example): <label for="name" accesskey="N">Name</label><input id="name" type="text" /> or <input type="button" accesskey="B" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts.
Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input value="1" name="ContentType" type="hidden"> .
- Accesskey can be defined for label of input or stright to input. Best ways (example): <label for="name" accesskey="N">Name</label><input id="name" type="text" /> or <input type="button" accesskey="B" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts.
Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input name="showmode" value="1" type="hidden"> .
- Accesskey can be defined for label of input or stright to input. Best ways (example): <label for="name" accesskey="N">Name</label><input id="name" type="text" /> or <input type="button" accesskey="B" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts.
Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input name="ThisIsQuickSearch" value="1" type="hidden"> .
- Accesskey can be defined for label of input or stright to input. Best ways (example): <label for="name" accesskey="N">Name</label><input id="name" type="text" /> or <input type="button" accesskey="B" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts.
Warning, if page has less than ten inputs, then accesskey should be defined for every input. Error was found from INPUT element code: <input name="DescendantNodesID" value="7563" type="hidden"> .
- Accesskey can be defined for label of input or stright to input. Best ways (example): <label for="name" accesskey="N">Name</label><input id="name" type="text" /> or <input type="button" accesskey="B" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts.
Warning, accesskey should be used for inputs whose type is submit, button or reset. Error was found from INPUT element code: <input style="width: 50px;" value="Hae" name="Submit2" 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.3 - Verify that a linearized version of tables used for layout is provided (8)

(hide test results)

Remark, found table element(s). Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr><td id="topstripe .
- 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
Remark, found table element(s). Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> .
- 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
Remark, found table element(s). Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><h1 class="forBra .
- 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
Remark, found table element(s). Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> .
- 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
Remark, found table element(s). Error was found from TABLE element code: <table width="250" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><h1 class="forBrai .
- 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
Remark, found table element(s). Error was found from TABLE element code: <table id="lift" width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td class=" .
- 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
Remark, found table element(s). Error was found from TABLE element code: <table width="250" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <span><span .
- 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
Remark, found table element(s). Error was found from TABLE element code: <table width="123" align="center" background="download.aspx?ID=72642&GUID={8606BA9B-C060-4676-99 .
- 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 name="ctl00$Topbar1$ctl03$SearchText" id="ctl00_Topbar1_ctl03_SearchText" style="width: 120px .
- 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 (2)

(hide test results)

Failed, link element a is too close to next one. Error was found from A element code: <a href="Default.aspx?culture=fi-FI&contentlan=1&nodeid=7563"> suomeksi</a> .
- Separate links by some element or "whitespace - Some character(s) - whitespase". Examples:...<a href="page7.html">Prew</a> | <a href="page.html9">Next</a>... or...<a href="page7.html">Prew</a> <br /> <a href="page.html9">Next</a>... or...<li><a href="page7.html">Prew</a></li><li><a href="page.html9">Next</a></li>... More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-divide-links.
Failed, link element a is too close to next one. Error was found from A element code: <a href="Default.aspx?culture=sv-FI&contentlan=3&nodeid=7563"> på svenska</a> .
- Separate links by some element or "whitespace - Some character(s) - whitespase". Examples:...<a href="page7.html">Prew</a> | <a href="page.html9">Next</a>... or...<a href="page7.html">Prew</a> <br /> <a href="page.html9">Next</a>... or...<li><a href="page7.html">Prew</a></li><li><a href="page.html9">Next</a></li>... More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-divide-links.

Test result: Failed

Guideline 11

(show module information)

11.3 - Provide information

(hide test results)

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

Test result: Passed

Guideline 13

(show module information)

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

Test result: Passed

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

Test result: Passed

13.7 - Different types of searches

(hide test results)

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

(hide test results)

Warning, no title in link. Error was found from LINK element code: <link rel="stylesheet" type="text/css" media="screen" href="/public/gfx/gfx_1/amk/screen3.css"> .
- Add title for link.
Warning, no title in link. Error was found from LINK element code: <link rel="stylesheet" type="text/css" media="screen" href="/public/gfx/gfx_1/amk/style.css"> .
- Add title for link.
Warning, no title in link. Error was found from LINK element code: <link rel="stylesheet" type="text/css" media="print" href="/public/gfx/gfx_1/amk/print.css"> .
- Add title for link.
Warning, no title in link. Error was found from LINK element code: <link rel="stylesheet" type="text/css" media="braille" href="/public/gfx/gfx_1/amk/braille.css"> .
- Add title for link.

Test result: Warning

13.10 - Skipping over multi-line ASCII art

Test result: Passed

Guideline 14

(show module information)

14.2 - Supplement text with presentations.

(hide test results)

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"> <!-- #themeright { } #pageingress { background-color: #ffffff; .
- Please use CSS rather than style element.
Warning, number of style attributes found: 6. Error was found from BODY element code: <body> <h1 class="forBraille">Kielivalinta</h1> <span class="forBraille"> Valitse kieli: < .
- Please use CSS rather than style attributes.

Test result: Warning

WCAG 1.0 AA

Guideline 3

(show module information)

3.1 - MathML

Test result: Passed

3.2 - Formal grammars.

Test result: Passed

3.3 - Proper font stylings.

Test result: Passed

3.4 - Relative over absolute.

Test result: Passed

3.5 - Proper header usage.

(hide test results)

Warning, <h1> found 11 times. Error was found from H1 element code: <h1 class="forBraille">Lisätoiminnot</h1> .
- Please consider using <h1> only once per page.

Test result: Warning

3.6 - Proper List usage.

Test result: Passed

3.7 - Proper quote usage.

Test result: Passed

Guideline 5

(show module information)

5.3 - Table is used as layout (8)

(hide test results)

Warning, a table may be used as a layout. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr><td id="topstripe .
- 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.
Warning, a table may be used as a layout. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> .
- 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.
Warning, a table may be used as a layout. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><h1 class="forBra .
- 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.
Warning, a table may be used as a layout. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> .
- 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.
Warning, a table may be used as a layout. Error was found from TABLE element code: <table width="250" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><h1 class="forBrai .
- 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.
Warning, a table may be used as a layout. Error was found from TABLE element code: <table id="lift" width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td 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.
Warning, a table may be used as a layout. Error was found from TABLE element code: <table width="250" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <span><span .
- 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.
Warning, a table may be used as a layout. Error was found from TABLE element code: <table width="123" align="center" background="download.aspx?ID=72642&GUID={8606BA9B-C060-4676-99 .
- 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)

Remark, 11 deprecated elements were found. Error was found from LINK element code: <link rel="stylesheet" type="text/css" media="screen" href="/public/gfx/gfx_1/amk/screen3.css"> .
- 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 (2)

(hide test results)

Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script language="javascript" type="text/javascript"> <!-- // Hide from older browsers. var da = .
- Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
Failed, <object> is missing text content. Error was found from OBJECT element code: <object data="download.aspx?id=78874&guid={8C3E21C8-2BC5-480B-91D4-A7DDEB1710B3}" type="applicat .
- Insert text content for <object>. For example: <object>A representation about peak oil.</object>

Test result: Failed

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

Test result: Passed

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

(hide test results)

Failed, found device independent event handler. Error was found from A element code: <a href="#" onclick="javascript:printPage();">Tulosta sivu</a> .
- 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)

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

(hide test results)

Warning, if object, embed or applet element is used, then have to ensure that those elements are keyboard accessible. Error was found from OBJECT element code: <object data="download.aspx?id=78874&guid={8C3E21C8-2BC5-480B-91D4-A7DDEB1710B3}" type="applicat .
- Make an element keyboard accessible. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-operable.

Test result: Warning

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

Test result: Passed

Guideline 10

(show module information)

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

(hide test results)

Failed, page opens in new window. Error was found from A element code: <a href="https://optima.turkuamk.fi/login1?ns=" target="_blank">Optima</a> .
- Do not use target="_blank" or target="_new" atributes. It will open a new window that can disorient some users. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups.
Failed, page opens in new window. Error was found from A element code: <a href="http://www.turkuamk.fi/Public/default.aspx?nodeid=8743&culture=fi-FI&contentlan=1" .
- 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 (3)

(hide test results)

Failed, wrong label usage. Error was found from INPUT element code: <input name="ctl00$Topbar1$ctl03$SearchText" id="ctl00_Topbar1_ctl03_SearchText" style="width: 120px .
- 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.
Failed, wrong label usage. Error was found from INPUT element code: <input name="TemplateID" value="28" type="radio"> .
- Use label right before or after input and use for - id relationship or parentship.More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-unassociated-labels.
Failed, wrong label usage. Error was found from INPUT element code: <input name="TemplateID" value="" checked="checked" type="radio"> .
- Use label right before or after input and use for - id relationship or parentship.More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-unassociated-labels.

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

Guideline 12

(show module information)

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

(hide test results)

Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr><td id="topstripe .
- 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.
Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> .
- 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.
Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><h1 class="forBra .
- 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.
Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> .
- 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.
Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table width="250" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td><h1 class="forBrai .
- 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.
Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table id="lift" width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td 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.
Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table width="250" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <span><span .
- 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.
Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table width="123" align="center" background="download.aspx?ID=72642&GUID={8606BA9B-C060-4676-99 .
- 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.
Warning, <h1> found 11 times. Error was found from H1 element code: <h1 class="forBraille">Lisätoiminnot</h1> .
- Please consider using <h1> only once per page.

Test result: Failed

12.4 - Associating labels explicitly with their controls (3)

(hide test results)

Failed, input does not have label. Error was found from INPUT element code: <input name="ctl00$Topbar1$ctl03$SearchText" id="ctl00_Topbar1_ctl03_SearchText" style="width: 120px .
- Use label right before or after input and use for - id relationship or parentship.
Failed, input does not have label. Error was found from INPUT element code: <input name="TemplateID" value="28" type="radio"> .
- Use label right before or after input and use for - id relationship or parentship.
Failed, input does not have label. Error was found from INPUT element code: <input name="TemplateID" value="" checked="checked" type="radio"> .
- 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 (4)

(hide test results)

Warning, found two identical name and title for two different links. Error was found from A element code: <a href="Default.aspx?culture=sv-FI&contentlan=3&nodeid=7563"> på svenska</a> .
- Use unique and meaningfull name and title for different links.
Warning, found two identical name and title for two different links. Error was found from A element code: <a href="default.aspx?uielementsize=1&nodeid=7563" style="font-size: 11px;">a</a> .
- Use unique and meaningfull name and title for different links.
Warning, found two identical name and title for two different links. Error was found from A element code: <a href="default.aspx?uielementsize=1&nodeid=7563" style="font-size: 11px;">a</a> .
- Use unique and meaningfull name and title for different links.
Warning, found two identical name and title for two different links. Error was found from A element code: <a href="default.aspx?uielementsize=2&nodeid=7563" style="font-size: 12px;">a</a> .
- Use unique and meaningfull name and title for different links.

Test result: Warning

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

Test result: Passed

13.3 - Information about the general layout

(hide test results)

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

ESOK-hanke 2006-2011

Foxability - Test results

Test results

WCAG 1.0 A

Guideline 1

1.1 - Elements have text equivalents. (3)

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.

Guideline 2

2.1 - Information is conveyed even without colors.

Guideline 4

4.1 - Language changes are identified.

Guideline 5

5.1 - Table used properly

5.2 - Associate data cells and header cells

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

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

Guideline 7

7.1 - Avoid causing the screen to flicker

Guideline 8

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

Guideline 9

9.1 - Client-side versus server-side image maps

Guideline 11

11.4 - Accessible page

Guideline 12

12.1 - Providing a frame title

Guideline 14

14.1 - Clear and simple language.

WCAG 1.0 AAA

Guideline 1

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

Guideline 2

2.2 - Colors are visible.

Guideline 4

4.2 - Acronyms and abbreviations. (3)

4.3 - Primary language.

Guideline 5

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

5.6 - Abbr used in long table headers names

Guideline 9

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

9.5 - Keyboard shortcuts (8)

Guideline 10

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

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

10.5 - Non-link, printable characters (2)

Guideline 11

11.3 - Provide information

Guideline 13

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

13.10 - Skipping over multi-line ASCII art

Guideline 14

14.2 - Supplement text with presentations.

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

WCAG 1.0 AA

Guideline 3

3.1 - MathML

3.2 - Formal grammars.

3.3 - Proper font stylings.

3.4 - Relative over absolute.

3.5 - Proper header usage.

3.6 - Proper List usage.

3.7 - Proper quote usage.

Guideline 5

5.3 - Table is used as layout (8)

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

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