Foxability - Test results

Test results

Test subject: http://www.joensuu.fi/joyindex.html

Statistics for the evaluated page

Total tests: 64

	Tests	Percent	Total	Percent
Total passed:	59	92.19%	59	70.24%
-Passed with remarks:	18	28.13%	18	21.43%
Failed:	4	6.25%	6	7.14%
Warnings:	1	1.56%	1	1.19%
Total:	64	100.00%	84	100.00%

MobileOK

WCAG

Guideline 1

(show module information)

1.1 - Elements have text equivalents.

(hide test results)

Failed, root <frameset> must have a <noframes> as a child. Error was found from HTML element code: <html><head><title>Joensuun yliopisto</title> <meta name="generator" content="Adobe Photoshop(R .
- Insert <noframes> into <frameset>. For example: <frameset><frame>...</frame><noframes><a href="noframe.html">Main page without frames.</a></noframes></frameset>

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.

(hide test results)

Warning, <body> not found. Error was found from HTML element code: <html><head><title>Joensuun yliopisto</title> <meta name="generator" content="Adobe Photoshop(R .
- Please test individual pages, not top level frameset-pages.

Test result: Warning

Guideline 3

(show module information)

3.1 - MathML

Test result: Passed

3.2 - Formal grammars.

(hide test results)

Failed, no DOCTYPE found. Error was found from HTML element code: <html><head><title>Joensuun yliopisto</title> <meta name="generator" content="Adobe Photoshop(R .
- Define document type in the first line of the page. For example: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

Test result: Failed

3.3 - Proper font stylings.

Test result: Passed

3.4 - Relative over absolute.

(hide test results)

Remark, stylesheets not detected.
- Please use CSS or <style> to achieve a richer browsing experience.

Test result: Passed

3.5 - Proper header usage.

Test result: Passed

3.6 - Proper List usage.

Test result: Passed

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.

Test result: Passed

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

Test result: Passed

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

Test result: Passed

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

Test result: Passed

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

(hide test results)

Failed, root <frameset> must have a <noframes> as a child. Error was found from HTML element code: <html><head><title>Joensuun yliopisto</title> <meta name="generator" content="Adobe Photoshop(R .
- Insert <noframes> into <frameset>. For example: <frameset><frame>...</frame><noframes> <a href="noframe.html">. Main page without frames.</a></noframes></frameset>

Test result: Failed

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

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

Test result: Passed

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

Test result: Passed

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

Test result: Passed

10.5 - Non-link, printable characters

Test result: Passed

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

(hide test results)

Failed, missing title for frame. Error was found from FRAMESET element code: <frameset frameborder="no" cols="180,100%" border="0" framespacing="0"> <frame src="ajankohtaist .
- Add title for frame <FRAME src="nav.html" title="Navigation bar">. More from http://www.w3.org/TR/WCAG10-TECHS/#tech-frame-titles
Failed, missing title for frame. Error was found from FRAME element code: <frame src="ajankohtaista/konferenssipalkki.html" name="konferenssit" marginwidth="0" marginheight=" .
- Add title for frame <FRAME src="nav.html" title="Navigation bar">. More from http://www.w3.org/TR/WCAG10-TECHS/#tech-frame-titles
Failed, missing title for frame. Error was found from FRAME element code: <frame src="index-main.html" name="main" frameborder="no"> .
- Add title for frame <FRAME src="nav.html" title="Navigation bar">. More from http://www.w3.org/TR/WCAG10-TECHS/#tech-frame-titles

Test result: Failed

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

Test result: Passed

12.4 - Associating labels explicitly with their controls

Test result: Passed

Guideline 13

(show module information)

13.1 - Target of each link

Test result: Passed

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

Test result: Passed

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.

Test result: Passed

ESOK-hanke 2006-2011

Foxability - Test results

Test results

MobileOK

WCAG

Guideline 1

1.1 - Elements have text equivalents.

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.

3.5 - Proper header usage.

3.6 - Proper List usage.

3.7 - Proper quote usage.

Guideline 4

4.1 - Language changes are identified.

4.2 - Acronyms and abbreviations.

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

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

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

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

12.2 - Describe the purpose of frames

12.3 - Dividing large blocks of information into more manageable groups

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

13.10 - Skipping over multi-line ASCII art

Guideline 14