Foxability - Test results
Test results
Test results
Test subject: http://innovaatioyliopisto.info/
Statistics for the evaluated page
Total tests: 66
Tests | Percent | Total | Percent | |
---|---|---|---|---|
Total passed: | 51 | 77.27% | 51 | 45.13% |
-Passed with remarks: | 20 | 30.30% | 25 | 22.12% |
Failed: | 11 | 16.67% | 24 | 21.24% |
Warnings: | 4 | 6.06% | 13 | 11.50% |
Total: | 66 | 100.00% | 113 | 100.00% |
WCAG 1.0 A
Guideline 1
1.1 - Elements have text equivalents. (7)
(hide test results)- Failed, <noscript> after <script> not found. Error was found from
SCRIPT
element code:<script type="text/javascript" src="js/prototype.js"></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" src="js/scriptaculous.js"></script>
.- Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
- Failed, alt attribute is empty. Error was found from
IMG
element code:<img src="http://www.aaltoyliopisto.info/media/rotate/taik002_258x172.jpg" alt="">
.- Please insert content for alt attribute. For example: alt="Some fava beans and a nice chianti."
- Failed, alt attribute not found. Error was found from
IMG
element code:<img src="media/kuvia/111_pikkukuva.jpg" width="125" border="0" height="170">
.- Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
- Failed, alt attribute not found. Error was found from
IMG
element code:<img src="media/site_images/arrow.gif" width="6" border="0" height="7">
.- Please insert an alt attribute. For example: alt="Some fava beans and a nice chianti."
- 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"> _uacct = "UA-2757591-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)- 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
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
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
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
6.1 - Organize documents so they may be read without style sheets
(hide test results)- Remark, 5 deprecated elements were found. Error was found from
LINK
element code:<link rel="stylesheet" type="text/css" href="style/style.css" media="screen">
.- 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="js/prototype.js"></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" src="js/scriptaculous.js"></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 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"> _uacct = "UA-2757591-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
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
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="js/prototype.js"></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" src="js/scriptaculous.js"></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 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"> _uacct = "UA-2757591-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
9.1 - Client-side versus server-side image maps
- Test result
- Passed
Guideline 11
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
12.1 - Providing a frame title
- Test result
- Passed
Guideline 14
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
1.5 - Client-side image map links need to have text equivalents
- Test result
- Passed
Guideline 2
2.2 - Colors are visible. (2)
(hide test results)- Failed, the color difference of rgb(102, 102, 102) and rgb(213, 222, 217) is too low. Error was found from
INPUT
element code:<input id="search-submit" value="Hae" type="submit">
.- Change the colors so that they have higher color difference.
- Failed, the brightness difference of rgb(102, 102, 102) and rgb(213, 222, 217) is too low. Error was found from
INPUT
element code:<input id="search-submit" value="Hae" type="submit">
.- Change the colors so that they have higher brightness difference.
- Test result
- Failed
Guideline 4
4.2 - Acronyms and abbreviations. (4)
(hide test results)- Warning, potential abbreviation found: HSE. Error was found from
A
element code:<a href="http://www.aaltoyliopisto.info/fi/view/content/hse-i-taik-i-tkk">HSE | TaiK | TKK</a>
.- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
- Warning, potential abbreviation found: TKK. Error was found from
A
element code:<a href="http://www.aaltoyliopisto.info/fi/view/content/hse-i-taik-i-tkk">HSE | TaiK | TKK</a>
.- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
- Warning, potential abbreviation found: HSE. Error was found from
SPAN
element code:<span style="font-size: 7pt; color: rgb(51, 51, 51); font-family: Arial;">Tämän sivuston sisällöstä
.- Please enter a definition for the abbreviation. For example: <abbr title="United States of America">USA</abbr>
- Warning, potential abbreviation found: TKK. Error was found from
SPAN
element code:<span style="font-size: 7pt; color: rgb(51, 51, 51); font-family: Arial;">Tämän sivuston sisällöstä
.- 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 lang attribute found. Error was found from
HTML
element code:<html xmlns="http://www.w3.org/1999/xhtml"><head> <title>Aaltoyliopisto.info</title> <base href="h
.- Insert lang attribute to specify language used. For example: <html lang="fi">
- Test result
- Failed
Guideline 5
5.5 - Summary, caption and title in table
- Test result
- Passed
5.6 - Abbr used in long table headers names
- Test result
- Passed
Guideline 9
9.4 - Creating a logical tab order through links, form controls and objects
- Test result
- Passed
9.5 - Keyboard shortcuts (3)
(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 id="searchstring" name="q" size="25" maxlength="255" value="" type="text">
.- Accesskey can be defined for label of input or stright to input. Best ways (example): <label for="name" accesskey="N">Name</label><input id="name" type="text" /> or <input type="button" accesskey="B" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts.
- 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="lang" value="fi" 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 id="search-submit" 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.
- Test result
- Warning
Guideline 10
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)
(hide test results)- Failed, no default text. Error was found from
INPUT
element code:<input id="searchstring" name="q" size="25" maxlength="255" value="" type="text">
.- Add default text. Example: <input type="text" value="Write here" /> More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-place-holders.
- Test result
- Failed
10.5 - Non-link, printable characters
- Test result
- Passed
Guideline 11
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
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.10 - Skipping over multi-line ASCII art
- Test result
- Passed
Guideline 14
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.
(hide test results)- Warning, number of style attributes found: 3. Error was found from
BODY
element code:<body> <div id="doc2" class="yui-t2"> <div id="hd"> <div id="masthead" class="clearfix">
.- Please use CSS rather than style attributes.
- Test result
- Warning
WCAG 1.0 AA
Guideline 3
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. (3)
(hide test results)- Failed, absolute size definition found. span:"font-size: 7pt". Error was found from
SPAN
element code:<span style="font-size: 7pt; color: rgb(51, 51, 51); font-family: Arial;">Tämän sivuston sisällöstä
.- Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
- Remark, the page used CSS which is in different domain and thus it cannot be reached. Error was found from
LINK
element code:<link rel="stylesheet" type="text/css" href="style/style.css" media="screen">
.- Please relocate the CSS or check the CSS manually.
- Remark, the page used CSS which is in different domain and thus it cannot be reached. Error was found from
LINK
element code:<link rel="alternate stylesheet" type="text/css" media="screen" href="style/larger.css" title="Large
.- Please relocate the CSS or check the CSS manually.
- Test result
- Failed
3.5 - Proper header usage. (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>Aalto-yliopisto on Helsingin kauppakorkeakoulun, Taideteollisen korkeakoulun ja Teknillisen kork
.- Lower the header level to at least <h2>.
- Warning, <h1> found 5 times. Error was found from
H1
element code:<h1>Suomen tiedepalkinto aivotutkija Riitta Harille</h1>
.- Please consider using <h1> only once per page.
- Test result
- Failed
3.6 - Proper List usage.
- Test result
- Passed
3.7 - Proper quote usage.
- Test result
- Passed
Guideline 5
5.3 - Table is used as layout
- Test result
- Passed
Guideline 6
6.1 - Organize documents so they may be read without style sheets
(hide test results)- Remark, 5 deprecated elements were found. Error was found from
LINK
element code:<link rel="stylesheet" type="text/css" href="style/style.css" media="screen">
.- 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="js/prototype.js"></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" src="js/scriptaculous.js"></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 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"> _uacct = "UA-2757591-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
- Test result
- Passed
6.5 - Ensure that dynamic content is accessible or provide an alternative presentation or page
- Test result
- Passed
Guideline 7
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
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
Guideline 10
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
(hide test results)- Failed, wrong label usage. Error was found from
INPUT
element code:<input id="searchstring" name="q" size="25" maxlength="255" value="" type="text">
.- Use label right before or after input and use for - id relationship or parentship.More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-unassociated-labels.
- Test result
- Failed
Guideline 11
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
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>Aalto-yliopisto on Helsingin kauppakorkeakoulun, Taideteollisen korkeakoulun ja Teknillisen kork
.- Lower the header level to at least <h2>.
- Warning, <h1> found 5 times. Error was found from
H1
element code:<h1>Suomen tiedepalkinto aivotutkija Riitta Harille</h1>
.- Please consider using <h1> only once per page.
- Test result
- Failed
12.4 - Associating labels explicitly with their controls
(hide test results)- Failed, input does not have label. Error was found from
INPUT
element code:<input id="searchstring" name="q" size="25" maxlength="255" value="" type="text">
.- Use label right before or after input and use for - id relationship or parentship.
- Test result
- Failed
Guideline 13
13.1 - Target of each link (3)
(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.aaltoyliopisto.info/fi/news/kutsu-aalto-yliopiston-arvopohdintaan">Lue lisää</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="http://www.aaltoyliopisto.info/fi/news/kutsu-aalto-yliopiston-arvopohdintaan">Lue lisää</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="http://www.aaltoyliopisto.info/fi/news/maija-t-yrylle-aikakauslehtien-liiton-j-v-snellman-p
.- 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