HiSoftware® Cynthia Says - Web Content Accessibility Report
Powered by HiSoftware Content Quality Technology. If you have a question about this output please email support@hisoftware.com

Verified File Name: http://alfa.fct.mctes.pt/acessibilidade.phtml.pt
Date and Time: 3/13/2009 8:00:54 PM
Passed Automated Verification
Resultados das verificações não automáticas em Português
Resultado final: a página satisfaz A (Prioridade 1), não satisfaz AA (Prioridade 2)

HiSoftware logo and link to main web siteHiSoftware can help you meet all of your accessibility needs and more. Our industry leading enterprise and desktop products provide you with an automated, full-featured Accessibility monitoring, testing, and repair solution to make sure your ever-changing Web content is always compliant. Visit www.hisoftware.com to find out more about how HiSoftware solutions can help you meet your Web compliance goals and request a trial copy.

Read Understanding Accessibility today!  Download Now


The level of detail setting for the report is to show all detail.


Verification Checklist
Checkpoints Passed
Basic Settings Yes No Other
1.1 / (a) Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
  • Rule: 1.1.1 - All IMG elements are required to contain either the alt or the longdesc attribute.
    • No invalid IMG elements found in document body.
  • Rule: 1.1.2 - All INPUT elements are required to contain the alt attribute or use a LABEL.
    • No invalid INPUT elements found in document
  • Rule: 1.1.3 - All OBJECT elements are required to contain element content.
    • No OBJECT elements found in document body.
  • Rule: 1.1.4 - All APPLET elements are required to contain both element content and the alt attribute.
    • No APPLET elements found in document body.
  • Rule: 1.1.6 - All IFRAME elements are required to contain element content.
    • No IFRAME elements found in document body.
  • Rule: 1.1.7 - All Anchor elements found within MAP elements are required to contain the alt attribute.
    • No MAP elements found in document body.
  • Rule: 1.1.8 - All AREA elements are required to contain the alt attribute.
    • No AREA elements found in document body.
  • Rule: 1.1.9 - When EMBED Elements are used, the NOEMBED element is required in the document.
    • No EMBED elements found in document body.
Yes    
7.1 / (j) Until user agents allow users to control flickering, avoid causing the screen to flicker.
  • Rule: 7.1.1 - Documents are required not to contain the BLINK element.
    • No BLINK elements found in document body.
  • Rule: 7.1.2 - Documents are required not to contain the MARQUEE element.
    • No MARQUEE elements found in document body.
  • Note: SCRIPT element(s) found in document body, a visual verification must be done to ensure the script does not cause the screen to flicker.
 Sim    
2.1 / (c) Ensure that all information conveyed with color is also available without color, for example from context or markup.  Sim    
6.1 / (d) Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.
  • Note: Document uses external stylesheets, inline style information, or header style information.
 Sim    
Image Maps Yes No Other
1.2 / (e) Provide redundant text links for each active region of a server-side image map.
  • Rule: 1.2.1 - Locate any IMG element that contains the 'ismap' attribute.
    • No IMG elements found in document body that contain the 'ismap' attribute.
  • Rule: 1.2.2 - Locate any INPUT element that contains the 'ismap' attribute.
    • No INPUT elements found in document body that contain the 'ismap' attribute.
    N/A
9.1 / (f) Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
  • Rule: 9.1.1 - No IMG element should contain the 'ismap' attribute.
    • No server-side image map IMG elements found in document body.
  • Rule: 9.1.2 - No INPUT element should contain the 'ismap' attribute.
    • No server-side image map INPUT elements found in document body.
    N/A
Tables Yes No Other
5.1 / (g) For data tables, identify row and column headers.
  • Rule: 5.1.1 - Identify all Data TABLE elements.
    • No TABLE elements found in document body.
    N/A
5.2 / (h) For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.
  • Rule: 5.2.1 - Identify all Data TABLE elements.
    • No TABLE elements found in document body.
    N/A
Frames, Scripts & Multimedia Yes No Other
12.1 / (i) Title each frame to facilitate frame identification and navigation.
  • Document is not a FRAMESET Page.
    N/A
6.3 / (l),(m) Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.
  • Rule: 6.3.1 - Anchor elements are required not to use javascript for the link target when the NOSCRIPT element is not present in the document. These elements will not cause a failure of the checkpoint if the NOSCRIPT element is found, however, they will be identified.
    • No Anchor elements that use javascript for the link target were found in document body.
  • Rule: 6.3.2 - AREA elements are required not to use javascript for the link target when the NOSCRIPT element is not present in the document. These elements will not cause a failure of the checkpoint if the NOSCRIPT element is found, however, they will be identified.
    • No AREA Elements found in document body.
  • Rule: 6.3.3 - Locate elements that use HTML event handlers.
    • Note: This rule has not been selected to be verified for this checkpoint.
  • Rule: 6.3.4 - When SCRIPT Elements are used, the NOSCRIPT element is required in the document.
    • Warning - SCRIPT Element(s) are found in document and the NOSCRIPT element is not.
  • Rule: 6.3.5 - All OBJECT elements are required to contain element content.
    • No OBJECT elements found in document body.
  • Rule: 6.3.6 - All APPLET elements are required to contain both element content and the alt attribute.
    • No APPLET elements found in document body.
  • Rule: 6.3.7 - When EMBED Elements are used, the NOEMBED element is required in the document.
    • No EMBED elements found in document body.
  • Rule: 6.3.8 - All pages that have links to files that require a special reader or plug-in are required to contain the specified text indicating a link to the reader or plug-in.
    • Note: This rule has not been selected to be verified for this checkpoint.
 Sim após introdução do elemento NOSCRIPT    
1.4 / (b) 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.
  • Rule: 1.4.1 - Identify all OBJECT Elements that have a multimedia MIME type as the type attribute value.
    • No OBJECT elements found in document body.
  • Rule: 1.4.2 - Identify all OBJECT Elements that have a 'data' attribute value with a multimedia file extension.
    • No OBJECT elements found in document body.
  • Rule: 1.4.3 - Identify all EMBED Elements that have a 'src' attribute value with a multimedia file extension.
    • No EMBED elements found in document body.
    N/A
Failsafe Yes No Other
11.4 / (k) If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.      N/A
11.4 / (k) Option A - Check for the string 'Text Version' within the document.     N/V
11.4 / (k) Option B - Check for a Global Text Version Link within the document.     N/V
11.4 / (k) Option C - Check for an Accessibility Policy Link within the document.     N/V
Non 508 Yes No Other
4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).      N/A
14.1 Use the clearest and simplest language appropriate for a site's content.      N/V
1.3 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.      N/A
6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.      N/A

Priority 2 Verification Checklist
Checkpoints Passed
Priority 2 - Basic Yes No Other
2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.    Não  
3.1 When an appropriate markup language exists, use markup rather than images to convey information. Sim     
3.2 Create documents that validate to published formal grammars.
  • Rule: 3.2.1 - Documents are required to use the !DOCTYPE tag.
    • Note: Document contains the !DOCTYPE tag with the value: html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
    • You need to confirm that the HTML in your page conforms to the standards for that doctype. You may validate your page for a selected doctype at http://validator.w3.org/.
 Sim    
3.3 Use style sheets to control layout and presentation.
  • Rule: 3.3.1 - Identify the use of external stylesheets, inline style information, or header style information within the document.
    • Note: Document uses external stylesheets, inline style information, or header style information.
  • Rule: 3.3.2 - Identify the use of Bold and Italic elements within the document.
    • Note: Document does not use either the Bold or Italic elements.
 Sim    
3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.
  • Rule: 3.4.1 - Identify the use of external stylesheets, inline style information, or header style information within the document.
    • Note: Document uses external stylesheets, inline style information, or header style information.
  • Rule: 3.4.2 - Identify the use of the 'width' or 'height' attribute in one or more elements.
    • Note: Document does not use either the 'width' or 'height' attribute in any of the following elements: HR, IFRAME, TABLE ,TD, TH.
 Sim    
3.5 Use header elements to convey document structure and use them according to specification.
  • Rule: 3.5.1 - Identify the use of Header elements (H1, H2, H3, H4, H5, H6) within the document.
    • Note: Document uses Header elements (H1, H2, H3, H4, H5, H6). Please verify that they are used according to the HTML specification.
 Sim    
3.6 Mark up lists and list items properly.
  • Rule: 3.6.1 - Identify the use of List elements (DL, UL, OL) within the document.
    • Note: Document uses List elements (DL, UL, OL). Please verify that they are used according to the HTML specification.
 Sim    
3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.
  • Rule: 3.7.1 - Identify the use of Quote and BLOCKQUOTE elements within the document.
    • Note: Document does not use any Quote or BLOCKQUOTE elements.
    N/A
6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page.

In addition to the rules specified below, refer to the detail of checkpoints 6.3 / (l),(m) and 1.1 / (a) for locations of elements that apply to this checkpoint.
  • Rule: 6.5.1 - Identify the use of LINK elements with the 'rel' attribute containing the value 'Alternate'.
    • Note: Document does not use any LINK elements with the 'rel' attribute containing the value 'Alternate'.
 Sim    
7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off).

To assist with visual verification, we recommend that you refer to the detail of checkpoint 7.1 / (j) for locations of elements that apply to this checkpoint.
 Sim    
7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.
  • Rule: 7.4.1 - Documents are required not to use the META element with the 'http-equiv' attribute value 'refresh'.
    • Note: Document does not use the META element with the 'http-equiv' attribute value 'refresh'.
Yes    
7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects.

To assist with visual verification, we recommend that you refer to the detail of checkpoint 7.4 for potential violations that apply to this checkpoint.
 Sim    
10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.

To assist with visual verification, we recommend that you refer to the detail of checkpoints 6.3 / (l),(m) and 7.4 for locations of elements and potential violations that apply to this checkpoint.
 Sim    
11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. Sim     
11.2 Avoid deprecated features of W3C technologies.
  • Rule: 11.2.1 - Identify the use of one or more deprecated elements or attributes within the document.
    • Note: Document does not use any deprecated elements or attributes.
Yes    
12.3 Divide large blocks of information into more manageable groups where natural and appropriate.      
13.1 Clearly identify the target of each link.
  • Rule: 13.1.1 - All Anchor elements are required not to use any of the defined link phrases in the link text.
    • No Anchor elements that use any of the defined link phrases in the link text were found in document body.
  • Rule: 13.1.2 - All Anchor elements are required not to use the same link text to refer to different resources.
    • No Anchor elements that use the same link text to refer to different resources were found in document body.
Yes    
13.2 Provide metadata to add semantic information to pages and sites.
  • Rule: 13.2.1 - Documents are required to use the TITLE element.
    • Note: Document uses the TITLE element.
  • Rule: 13.2.2 - Documents are required to use META elements, that are defined as required, in Head section.
    • Note: Document contains all required META elements in Head section.
Yes    
13.3 Provide information about the general layout of a site (e.g., a site map or table of contents).
  • Rule: 13.3.1 - Check for link to site map page within document.
    Site Map Link Text:
    • Note: This rule has not been selected to be verified for this checkpoint.
Yes    
13.4 Use navigation mechanisms in a consistent manner. Sim     
Priority 2 - Tables Yes No Other
5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version).
  • Rule: 5.3.1 - Identify all Layout Tables.
    • No TABLE elements found in document body.
    N/A
5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.

To assist with visual verification, we recommend that you refer to the detail of checkpoint 5.3 for locations of elements that apply to this checkpoint.
 Sim    
Priority 2 - Frames Yes No Other
12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.
  • Document is not a FRAMESET Page.
Yes    
Priority 2 - Forms Yes No Other
10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.
  • Rule: 10.2.1 - Identify all LABEL elements used within FORM elements.
    • Note: LABEL Element found at Line: 201, Column: 29 is in FORM element at Line: 200, Column: 1.
    • Note: LABEL Element found at Line: 202, Column: 7 is in FORM element at Line: 200, Column: 1.
 Sim    
12.4 Associate labels explicitly with their controls.
  • Rule: 12.4.1 - Identify all non-hidden INPUT elements that do not have an explicit LABEL association.
    • No invalid INPUT elements found in FORM element found at Line: 200, Column: 1.
  • Rule: 12.4.2 - Identify all TEXTAREA elements that do not have an explicit LABEL association.
    • No TEXTAREA Elements found within FORM element found at Line: 200, Column: 1.
  • Rule: 12.4.3 - Identify all SELECT elements that do not have an explicit LABEL association.
    • No SELECT Elements found within FORM element found at Line: 200, Column: 1.
  • Rule: 12.4.4 - Identify all OBJECT elements, within a FORM element, that do not have an explicit LABEL association.
    • No OBJECT Elements found within FORM element found at Line: 200, Column: 1.
Yes    
Priority 2 - Applets, Objects and Scripts Yes No Other
6.4 For scripts and applets, ensure that event handlers are input device-independent.

To assist with visual verification, we recommend that you refer to the detail of checkpoint 6.3 / (l),(m) for locations of elements that apply to this checkpoint.
     
7.3 Until user agents allow users to freeze moving content, avoid movement in pages.

To assist with visual verification, we recommend that you refer to the detail of checkpoint 7.1 / (j) for locations of elements that apply to this checkpoint.
Sim     
8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.

To assist with visual verification, we recommend that you refer to the detail of checkpoint 6.3 / (l),(m) for locations of elements that apply to this checkpoint.
     
9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.

To assist with visual verification, we recommend that you refer to the detail of checkpoint 6.3 / (l),(m) for locations of elements that apply to this checkpoint.
     N/A
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.

To assist with visual verification, we recommend that you refer to the detail of checkpoint 6.3 / (l),(m) for locations of elements that apply to this checkpoint.
 Yes    

Priority 3 Verification Checklist
Checkpoints Passed
Priority 3 - Basic Yes No Other
4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs.
  • Rule: 4.2.1 - Identify the use of ABBR elements within the document.
    • Note: Document does not use any ABBR elements.
  • Rule: 4.2.2 - Identify the use of ACRONYM elements within the document.
    • Note: Document uses one or more ACRONYM elements. Please verify that the first occurence of each contains the 'title' attribute.
     
4.3 Identify the primary natural language of a document.
  • Rule: 4.3.1 - Documents are required to use the META element with the 'name' attribute value 'language' in the Head section.
    • Note: Document uses the META element with the 'name' attribute value 'language'.
  • Rule: 4.3.2 - The HTML (Root) element must use the 'lang' attribute.
    • Note: The HTML (Root) element uses the 'lang' attribute.
Yes    
9.4 Create a logical tab order through links, form controls, and objects.
  • Rule: 9.4.1 - All Anchor, AREA, BUTTON, INPUT, OBJECT, SELECT and TEXTAREA elements are required to use the 'tabindex' attribute.
    • Warning - One or more Anchor, AREA, BUTTON, INPUT, OBJECT, SELECT and TEXTAREA elements do not use the 'tabindex' attribute.
    Warning
9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.
  • Rule: 9.5.1 - All Anchor, AREA, BUTTON, INPUT, LABEL, LEGEND, and TEXTAREA elements are required to use the 'accesskey' attribute.
    • Warning - One or more Anchor, AREA, BUTTON, INPUT, LABEL, LEGEND, and TEXTAREA elements do not use the 'accesskey' attribute.
    Warning
10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.
  • Rule: 10.5.1 - All Anchor elements not surrounding images cannot be directly adjacent.
    • No invalid Anchor Elements found within document body.
Yes    
11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)      
13.5 Provide navigation bars to highlight and give access to the navigation mechanism.      
13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.
  • Rule: 13.6.1 - All pages are required to contain a bookmark link to skip navigation that has the specified text in either the link text or the 'title' attribute value.
    Skip Navigation Text:
    • Note: This rule has not been selected to be verified for this checkpoint.
     
13.7 If search functions are provided, enable different types of searches for different skill levels and preferences.      
13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.      
13.9 Provide information about document collections (i.e., documents comprising multiple pages.).      
13.10 Provide a means to skip over multi-line ASCII art.      
14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.      
14.3 Create a style of presentation that is consistent across pages.      
Priority 3 - Image Maps Yes No Other
1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map.
  • Rule: 1.5.1 - Identify all MAP elements that use the AREA element.
    • No MAP elements found in document body.
    N/A
Priority 3 - Tables Yes No Other
5.5 Provide summaries for tables.

To assist with visual verification, we recommend that you refer to the detail of checkpoints 5.1 / (g) or 5.2 / (h) and 5.3 for locations of elements that apply to this checkpoint.
     
5.6 Provide abbreviations for header labels.

To assist with visual verification, we recommend that you refer to the detail of checkpoints 5.1 / (g) or 5.2 / (h) for locations of elements that apply to this checkpoint.
     
10.3 Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.

To assist with visual verification, we recommend that you refer to the detail of checkpoints 5.1 / (g) or 5.2 / (h) and 5.3 for locations of elements that apply to this checkpoint.
     
Priority 3 - Forms Yes No Other
10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.      

Checkpoint Result Legend: Yes = Passed Automated Verification, No = Failed Automated Verification, Warning = Failed Automated Verification, however, configured not to cause page to fail (Priority 2 or 3 only), N/V = Not selected for verification, N/A = No related elements were found in document (Visual only), No Value = Visual Checkpoint


Report generated by the HiSoftware Company Cynthia Agent. Powered by the AccMonitor Compliance Server HiSoftware, Cynthia Says, AccMonitor Compliance Server, Cynthia Agent are all trademarks of HiSoftware Inc. (www.hisoftware.com 603.578.1870 or 1.888.272.2484)