W3C | Web Accessibility Initiative

Summary implementation report for UAAG 1.0

Evaluations Included in Report | Implementation Summary | Low Implementation Summary | Rating Information | Implementation Details | Disclaimer

Nearby: UAWG Home Page | UAWG Test Suites | UAAG 1.0 | Build an evaluation | Previous Implementation Reports

Evaluations Included in Report

  1. Internet Explorer 6.0 for Windows 2000 (IE6W) [XML data]
  2. Internet Explorer 5.0 for Macintosh OS 9.x (IE5M) [XML data]
  3. Opera 7.0 Final for Windows XP Professional Service Pack 1 (Opera6) [XML data]
  4. Mozilla 1.0 for Windows 2000 (Moz1) [XML data]
  5. JAWS for Windows (with Internet Explorer 6.0) for Microsoft Windows (JAWS402) [XML data]
  6. IBM Home Page Reader 3.02 for Microsoft Windows (HPR302) [XML data]
  7. Accessible Browser Project at UIUC (uses Internet Explorer) beta for Microsoft Windows (ABP) [XML data]
  8. Acrobat Reader 5.0 for Windows (PDF) [XML data]
  9. Grins SMIL 2 Player for Windows 9x (GRINS) [XML data]
  10. Windows Media Player 9.0 for Windows XP (WMP) [XML data]
  11. lpPlayer for Windows (LPP) [XML data]
  12. Victor Reader Pro for Windows or Portable Hardware (VIC) [XML data]
  13. Konqueror 2.2.2 for Linux (Konq) [XML data]
  14. Galeon 1.2.5 for Linux (Gal) [XML data]
  15. Amaya 5.3 for Linux (Amaya) [XML data]

Implementation Summary

Maximum Checkpoint Rating by Checkpoint Priority
Rating Priority 1 Priority 2 Priority 3 All Priorities
Number of Checkpoints 48 28 7 83
Two or more complete or almost complete implementations 46 (96%) 27 (96%) 7 (100%) 80 (96%)
One complete or almost complete implementation 48 (100%) 28 (100%) 7 (100%) 83 (100%)
Partial Implementation only 0 (0%) 0 (0%) 0 (0%) 0 (0%)
No Implementation 0 (0%) 0 (0%) 0 (0%) 0 (0%)

Note: Percentages are for a given priority

Checkpoints with Low Implementation Experience

Priority 1 Checkpoints

Checkpoints with no complete or almost complete implementation

Checkpoints with only one complete or almost complete implementation

Priority 2 Checkpoints

Checkpoints with no complete or almost complete implementation

Checkpoints with only one complete or almost complete implementation

Priority 3 Checkpoints

Checkpoints with no complete or almost complete implementation

Checkpoints with only one complete or almost complete implementation

Rating Information

Rating Scale
C: Complete Implementation
AC: Almost Complete Implementation, almost all requirements satisfied or bugs need to be fixed
PI: Partial Implementation, some requirements satisfied
NI: Not Implemented
NR: Not Rated
NA: Not Applicable

Implementation Details

Note: In this version of the report, the checkpoint-level rating is independent of the provision-level ratings. Reviewers may evaluate entire checkpoints and leave provisions as "Not rated". The column with user agent information only refers to provision-level ratings, so there may be a discrepancy between that column and the checkpoint rating column. Future versions of the report tool may derive checkpoint-level ratings from provision-level ratings.

Checkpoint and Provision Implementation by User Agent
Checkpoint Highest
Checkpoint
Rating		 Provision Highest
Provision
Rating		 User Agent Information
1.1. Full keyboard access. (P1) Complete 1. Ensure that the user can operate through keyboard input alone any user agent functionality available through the user interface. Complete
1.2. Activate event handlers. (P1) Complete 1. Allow the user to activate, through keyboard input alone, all event handlers that are explicitly associated with the element designated by the content focus. Complete
2. In order to satisfy provision one of this checkpoint, the user must be able to activate as a group all event handlers of the same input device event type. Complete
1.3. Provide text messages. (P1) Complete 1. Ensure that every message (e.g., prompt, alert, notification, etc.) that is a non-text element and is part of the user agent user interface has a text equivalent. Complete
2.1. Render content according to specification. (P1) Complete 1. Render content according to format specification (e.g., for a markup language or style sheet language). Complete
2.2. Provide text view. (P1) Complete 1. For content authored in text formats, provide a view of the text source. For the purposes of this checkpoint, a text format is any media object given an Internet media type of "text" (e.g., "text/plain", "text/html", or "text/*") as defined in RFC 2046 [RFC2046], section 4.1. Complete
2.3. Render conditional content. (P1) Complete 1. Allow configuration to provide access to each piece of unrendered conditional content "C". Complete
2. When a specification does not explain how to provide access to this content, do so as follows: If C is a summary, title, alternative, description, or expansion of another piece of content D, provide access through at least one of the following mechanisms: (1a) render C in place of D; (2a) render C in addition to D; (3a) provide access to C by allowing the user to query D. In this case, the user agent must also alert the user, on a per-element basis, to the existence of C (so that the user knows to query D); (4a) allow the user to follow a link to C from the context of D. Otherwise, provide access to C through at least one of the following mechanisms: (1b) render a placeholder for C, and allow the user to view the original author-supplied content associated with each placeholder; (2b) provide access to C by query (e.g., allow the user to query an element for its attributes). In this case, the user agent must also alert the user, on a per-element basis, to the existence of C; (3b) allow the user to follow a link in context to C. Complete
2.4. Allow time-independent interaction. (P1) Complete 1. For rendered content where user input is only possible within a finite time interval controlled by the user agent, allow configuration to provide a view where user interaction is time-independent. Complete
2.5. Make captions, transcripts, audio descriptions available. (P1) Complete 1. Allow configuration or control to render text transcripts, collated text transcripts, captions, and audio descriptions in content at the same time as the associated audio tracks and visual tracks. Complete
2.6. Respect synchronization cues. (P1) Complete 1. Respect synchronization cues (e.g., in markup) during rendering. Complete
2.7. Repair missing content. (P2) Complete 1. Allow configuration to generate repair text when the user agent recognizes that the author has failed to provide conditional content that was required by the format specification. Complete
2.8. No repair text. (P3) Complete 1. Allow at least two configurations for when the user agent recognizes that conditional content required by the format specification is present but empty content: generate no repair text, or generate repair as described in checkpoint 2.7. Complete
2.9. Render conditional content automatically. (P3) Complete 1. Allow configuration to render all conditional content automatically. Complete
2. As part of satisfying provision one of this checkpoint, provide access according to specification, or where unspecified, by applying one of the techniques 1a, 2a, or 1b defined in checkpoint 2.3. Complete
2.10. Don't render unsupported language. (P3) Complete 1. Allow configuration not to render text in unsupported scripts (i.e., writing systems) when that text would otherwise be rendered. Complete
2. When configured per provision one of this checkpoint, indicate to the user in context that author-supplied content has not been rendered. Complete
3.1. Toggle background images. (P1) Complete 1. Allow configuration not to render background image content. Complete
3.2. Toggle audio, video, animated images. (P1) Complete 1. Allow configuration not to render audio, video, or animated image content, except on explicit user request. Complete
3.3. Toggle animated or blinking text. (P1) Complete 1. Allow configuration to render animated or blinking text content as motionless, unblinking text. Blinking text is text whose visual rendering alternates between visible and invisible, at any rate of change. Complete
3.4. Toggle scripts. (P1) Complete 1. Allow configuration not to execute any executable content (e.g., scripts and applets). Complete
3.5. Toggle automatic content retrieval. (P1) Complete 1. Allow configuration so that the user agent only retrieves content on explicit user request. Complete
3.6. Toggle images. (P2) Complete 1. Allow configuration not to render image content. Complete
4.1. Configure text scale. (P1) Complete 1. Allow global configuration of the scale of visually rendered text content. Preserve distinctions in the size of rendered text as the user increases or decreases the scale. Complete
2. As part of satisfying provision one of this checkpoint, provide a configuration option to override rendered text sizes specified by the author or user agent defaults. Complete
3. As part of satisfying provision one of this checkpoint, offer a range of text sizes to the user that includes at least: the range offered by the conventional utility available in the operating environment that allows users to choose the text size (e.g., the font size), or if no such utility is available, the range of text sizes supported by the conventional APIs of the operating environment for drawing text. Complete
4.2. Configure font family. (P1) Complete 1. Allow global configuration of the font family of all visually rendered text content. Complete
2. As part of satisfying provision one of this checkpoint, provide a configuration option to override font families specified by the author or by user agent defaults. Complete
3. As part of satisfying provision one of this checkpoint, offer a range of font families to the user that includes at least: the range offered by the conventional utility available in the operating environment that allows users to choose the font family, or if no such utility is available, the range of font families supported by the conventional APIs of the operating environment for drawing text. Complete
4.3. Configure text colors. (P1) Complete 1. Allow global configuration of the foreground and background color of all visually rendered text content. Complete
2. As part of satisfying provision one of this checkpoint, provide a configuration option to override foreground and background colors specified by the author or user agent defaults. Complete
3. As part of satisfying provision one of this checkpoint, offer a range of colors to the user that includes at least: the range offered by the conventional utility available in the operating environment that allows users to choose colors, or if no such utility is available, the range of colors supported by the conventional APIs of the operating environment for specifying colors. Complete
4.4. Slow multimedia. (P1) Complete 1. Allow the user to slow the presentation rate of rendered audio and animation content (including video and animated images). Complete
2. As part of satisfying provision one of this checkpoint, for a visual track, provide at least one setting between 40% and 60% of the original speed. Complete
3. As part of satisfying provision one of this checkpoint, for a prerecorded audio track including audio-only presentations, provide at least one setting between 75% and 80% of the original speed. Complete
4. When the user agent allows the user to slow the visual track of a synchronized multimedia presentation to between 100% and 80% of its original speed, synchronize the visual and audio tracks (per checkpoint 2.6). Below 80%, the user agent is not required to render the audio track. Complete
4.5. Start, stop, pause, and navigate multimedia. (P1) Complete 1. Allow the user to stop, pause, and resume rendered audio and animation content (including video and animated images) that last three or more seconds at their default playback rate. Complete
2. Allow the user to navigate efficiently within audio and animations (including video and animated images) that last three or more seconds at their default playback rate. Complete
4.6. Do not obscure captions. (P1) Complete 1. For graphical viewports, allow configuration so that captions synchronized with a visual track in content are not obscured by it. Complete
4.7. Global volume control. (P1) Complete 1. Allow global configuration of the volume of all rendered audio, with an option to override audio volumes specified by the author or user agent defaults. Complete
2. As part of satisfying provision one of this checkpoint, allow the user to choose zero volume (i.e., silent). Complete
4.8. Independent volume control. (P1) Complete 1. Allow independent control of the volumes of rendered audio content synchronized to play simultaneously. Complete
4.9. Configure synthesized speech rate. (P1) Complete 1. Allow configuration of the synthesized speech rate, according to the full range offered by the speech synthesizer. Complete
4.10. Configure synthesized speech volume. (P1) Complete 1. Allow control of the synthesized speech volume, independent of other sources of audio. Complete
4.11. Configure synthesized speech characteristics. (P1) Complete 1. Allow configuration of synthesized speech characteristics according to the full range of values offered by the speech synthesizer. Complete
4.12. Specific synthesized speech characteristics. (P2) Complete 1. Allow configuration of synthesized speech pitch. Pitch refers to the average frequency of the speaking voice. Complete
2. Allow configuration of synthesized speech pitch range. Pitch range specifies a variation in average frequency. Complete
3. Allow configuration of synthesized speech stress. Stress refers to the height of "local peaks" in the intonation contour of the voice. Complete
4. Allow configuration of synthesized speech richness. Richness refers to the richness or brightness of the voice. Complete
4.13. Configure synthesized speech features. (P2) Complete 1. Provide support for user-defined extensions to the synthesized speech dictionary. Complete
2. Provide support for spell-out: where text is spelled one character at a time, or according to language-dependent pronunciation rules. Complete
3. Allow at least two configurations for speaking numerals: one where numerals are spoken as individual digits, and one where full numbers are spoken. Complete
4. Allow at least two configurations for speaking punctuation: one where punctuation is spoken literally, and one where punctuation is rendered as natural pauses. Complete
4.14. Choose style sheets. (P1) Complete 1. Allow the user to choose from and apply alternative author style sheets (such as linked style sheets). Complete
2. Allow the user to choose from and apply at least one user style sheet. Complete
3. Allow the user to turn off (i.e., ignore) author and user style sheets. Complete
5.1. No automatic content focus change. (P2) Complete 1. Allow configuration so that if a viewport opens without explicit user request, neither its content focus nor its user interface focus automatically becomes the current focus. Complete
5.2. Keep viewport on top. (P2) Complete 1. For graphical user interfaces, allow configuration so that the viewport with the current focus remains "on top" of all other viewports with which it overlaps. Complete
5.3. Manual viewport open only. (P2) Complete 1. Allow configuration so that viewports only open on explicit user request. Complete
2. When configured per provision one of this checkpoint, instead of opening a viewport automatically, alert the user and allow the user to open it with an explicit request (e.g., by confirming a prompt or following a link generated by the user agent). Complete