Home » Summary » Priority 1

Results for checkpoints of priorty 1

http://www.tcrm-metz.fr

navigate by results

P.1	4	1	-	12
P.2	7	9	4	9
P.3	11	-	2	6

Priority 1:
12 inapplicable checkpoints

Checkpoint 1.1 - Result: not applicable

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. [Priority 1]

| |

Images: No images used.

• Instructions:
  Each image must have an alt attribute with a text that provides the functionality of the image in the page. If this information is insufficient, for example because the image is complex, there should also be a longdesc attribute specifying a link to a detailed description of the image. In such cases it is useful to provide a textual link to the same information (often using "D" as the text of the link, with a title attribute describing the role of the link.
  [Close instructions]

| |

Graphical submit buttons: No graphical submit buttons used.

• Instructions:
  Each graphic form button (<input type="image">) must have a text alternative to communnicate its function, using an alt attribute.
  [Close instructions]

| |

Image map areas: No image map areas used.

• Instructions:
  Each area of an image map (associated with an <img>, <object> or <input> which defines a "hot zone" as a link) must have an alt attribute that communicates the functionality of the area.
  [Close instructions]

| |

Scripts: There are no scripts in the body of the document.

• Instructions:
  scripts included in document body should have alternative contents that describe their action or replace their functionality. It is recommended to use <noscript> for the alternative content after each <script> tag but it should be evaluated, in each case, the possible exceptions to this norm.
  [Close instructions]

| |

Embedded elements: No embedded elements used.

• Instructions:
  For each <embed> element there should be appropriate content (for example in a <noembed> element) which provides the same functionality as the object included.
  [Close instructions]

| |

Applets: No applets used.

• Instructions:
  Each applet can include alternative text using the "alt" attribute and should provide a detailed description in the content of the element (text between <applet> and </applet>).
  [Close instructions]

| |

Objects: No objects used.

• Instructions:
  Each <object> element must provide an alternative text in the content of the element (text between <object> and </object>).
  [Close instructions]

| |

Inline frames: No inline frames used.

• Instructions:
  Each <iframe> element must use the longdesc attribute to specify an URL that contains a description of the frame and must provide an alternative text in the content of the element (text between <iframe> and </iframe>).
  [Close instructions]

| |

Sound files: There are no linked sound files.

• Instructions:
  When sound files exist directly connected from the page, texts or alternative contents should be provided for those who cannot perceive those sounds.
  [Close instructions]

| |

Multimedia files: there are no linked multimedia files.

• Instructions:
  When video or multimedia files exist directly connected from the page, texts or alternative contents should be provided for those who cannot use those files.
  [Close instructions]

| |

Frames: No frames used.

• Instructions:
  In frames pages a <noframes> should exist that offers an alternative content for the navigators that don't support frames. Each <frame> element should include the title attribute and, if the relations among frames are complex, provide longdesc to describe those relations.
  [Close instructions]

Checkpoint 1.2 - Result: not applicable

Provide redundant text links for each active region of a server-side image map. [Priority 1]

| |

Server-side image maps: No server-side image maps used.

• Instructions:
  Check for each link defined by the active areas of a server-side image map, whether there is a link in text format in the page.
  [Close instructions]

Checkpoint 1.3 - Result: not applicable

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. [Priority 1]

| |

Embedded elements: No embedded elements used.

• Instructions:
  If an <embed> element contains video or an animation, check that a sound description of the visual track is included.
  [Close instructions]

| |

Multimedia elements: No multimedia elements used.

• Instructions:
  If an <object> element contains video or an animation, check that a sound description of the visual track is included.
  [Close instructions]

| |

Multimedia files: There are no multimedia files linked.

• Instructions:
  When multimedia files linked from page exists and present video or animation, a sound description of the visual track must be included.
  [Close instructions]

Checkpoint 1.4 - Result: not applicable

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. [Priority 1]

| |

Embedded elements: No embedded elements used.

• Instructions:
  If an <embed> element contains video or an multimedia application that changes over time, check if it includes equivalent alternatives synchronized with the presentation.
  [Close instructions]

| |

Multimedia elements: No multimedia elements used.

• Instructions:
  If an <object> element contains video or an multimedia application with that changes over time, check if it includes equivalent alternatives synchronized with the presentation.
  [Close instructions]

| |

Multimedia files: There are no multimedia files linked.

• Instructions:
  When multimedia files linked from page contain video or a multimedia application with that changes over time, verify if equivalent alternatives synchronized with the presentation are provided.
  [Close instructions]

Checkpoint 5.1 - Result: not applicable

For data tables, identify row and column headers. [Priority 1]

| |

Data tables: No data tables used.

• Instructions:
  Tables and table cells are identified. Header cells (<th>) are highlighted with a cyan background. Verify that those headers are only used in data tables.
  [Close instructions]

Checkpoint 5.2 - Result: not applicable

For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. [Priority 1]

| |

Complex tables: No complex tables used.

• Instructions:
  Tables and table cells are identified. Data cells (<td>) and header cells (<th>) that have some association attribute are highlighted with a cyan background.
  [Close instructions]

Checkpoint 6.1 - Result: not applicable

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. [Priority 1]

| |

Cascading Style Sheets: No cascading style sheets used.

• Instructions:
  Page is shown without styles. Check that content can be read correctly. In the source view the styles are only pointed out as additional info.
  [Close instructions]

Checkpoint 6.2 - Result: not applicable

Ensure that equivalents for dynamic content are updated when the dynamic content changes. [Priority 1]

| |

Script, applet, embed, object: No script, applet, embed, object used.

• Instructions:
  When changing images are shown, for example, by means of scripts, an equivalent alternative appropriate for that change must be provided.
  [Close instructions]

| |

Frames: No frames used.

• Instructions:
  Frames must be conformed by documents with formats capable to contain alternative texts and descriptions (HTML, XHTML, etc.) and not by an image, for example.
  [Close instructions]

Checkpoint 6.3 - Result: not applicable

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. [Priority 1]

| |

Links: No links used.

• Instructions:
  Check if the content of the "href" attribute in links is a valid resource, that is to say, if an address is indicated (URI) thath can be accesed even with scripts deactivated.
  [Close instructions]

| |

Scripts: No scripts used.

• Instructions:
  Page contents and their interactivity and functionality should be available without the execution of scripts.
  [Close instructions]

| |

Embed and object: No embed and object used.

• Instructions:
  Page Contents and their interactivity and functionality should be available without the execution of the programming elements (embed and object).
  [Close instructions]

| |

Applets: No applets used.

• Instructions:
  Page Contents and their interactivity and functionality should be available without the execution of the programming elements (applet).
  [Close instructions]

Checkpoint 8.1 - Result: not applicable

Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies. [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]

| |

Scripts: No scripts used.

• Instructions:
  Elements that respond to device-dependent events are highlighted. Check that scripts are directly accessible or compatible with the technical help.
  [Close instructions]

| |

Embedded elements: No embedded elements used.

• Instructions:
  Check that the <embed> elements are directly accessible or compatible with assistive technologies.
  [Close instructions]

| |

Applets: No applets used.

• Instructions:
  Check that <applet> elements are directly accessible or compatible with assistive technologies.
  [Close instructions]

| |

Objects: No objects used.

• Instructions:
  Check that <object> elements are directly accessible or compatible with assistive technologies.
  [Close instructions]

Checkpoint 9.1 - Result: not applicable

Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. [Priority 1]

| |

Image maps: No image maps used.

• Instructions:
  It is always preferable that image maps are of client-side, unless their areas cannot be defined with a geometric figure. Verify that in this case it is actually this way.
  [Close instructions]

Checkpoint 12.1 - Result: not applicable

Title each frame to facilitate frame identification and navigation. [Priority 1]

| |

Frames: No frames used.

• Instructions:
  Frames can cause trouble especially to some technical help users difficult to manage. For that reason, if frames are used it is essential that each one has a title as descriptive as possible of the content that will present.
  [Close instructions]

Copyright © Sidar 2003-2005
Development: Carlos Benavídez