Implementation Report for User Agent Accessibility Guidelines 1.0

Abstract

This document describes the implementation status of checkpoints defined in "User Agent Accessibility Guidelines 1.0". It is meant to demonstrate that the requirements specified in the guidelines can be implemented in existing and future user agents.

There is no implied or presumed endorsement of one type of implementation or another type of implementation by reference in this document. Inclusion serves only as an example to developers of the viability of satisfying the requirements of a checkpoint.

This document is part of a series of accessibility documents published by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C).

Status of this document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.

This document is support material for User Agent Accessibility Guidelines 1.0 and is not meant to become a W3C Recommendation. The User Agent Guidelines Working Group expects to update it periodically with new techniques and information about implementations that satisfy the guidelines.

This is a W3C Working Draft for review by W3C Members and other interested parties. It is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This is work in progress and does not imply endorsement by, or the consensus of, either W3C or participants in the WAI User Agent (UA) Working Group.

Please send comments about this document to the public mailing list w3c-wai-ua@w3.org (public archives).

This document has been produced as part of the Web Accessibility Initiative. The goals of the User Agent Working Group are described in the charter. A list of the Working Group participants is available.

A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR.

1. Introduction

1.1 Related resources

The implementation examples indicate that a checkpoint has already been fully or practically implemented by some type of user agent. Each checkpoint links to information about existing and proposed techniques for satisfying the checkpoint in Techniques for User Agent Accessibility Guidelines 1.0 [UAAG10-TECHS].

Note. Where "no information is available", it may be that there are not implementations today, that the Working Group is not aware of any, or that the authors have not yet added the information to this document.

1.2 Checkpoints that require developer information

Most users will be able to verify that most checkpoints have been satisfied. Those checkpoints that may be difficult to verify without vendor documentation or support are noted.

Detailed knowledge of the user agent functionality and the operating system APIs and resources used to implement a feature is typically needed to test these checkpoints. People other than developers may be able to verify conformance through interaction with native features of the user interface and compatibility testing with assistive technology. But in these cases the person may not have knowledge of all the functionalities of the user agent or be able to test with all assistive technologies. In the case of assistive technologies it may not be clear if the detected problems reside in the user agent using appropriate interfaces to export information or the assistive technology not taking advantage of information that the user agent is making available.

1.3 Priorities

Each checkpoint in this document is assigned a priority that indicates its importance for users with disabilities.

[Priority 1]

This checkpoint must be satisfied by user agents, otherwise one or more groups of users with disabilities will find it impossible to access the Web. Satisfying this checkpoint is a basic requirement for enabling some people to access the Web.

[Priority 2]

This checkpoint should be satisfied by user agents, otherwise one or more groups of users with disabilities will find it difficult to access the Web. Satisfying this checkpoint will remove significant barriers to Web access for some people.

[Priority 3]

This checkpoint may be satisfied by user agents to make it easier for one or more groups of users with disabilities to access information. Satisfying this checkpoint will improve access to the Web for some people.

2. User agent accessibility guidelines

Guideline 1. Support input and output device-independence.

Checkpoints for user interface accessibility:

1.1 Ensure that every functionality available through the user interface is also available through every input device API supported by the user agent. Excluded from this requirement are functionalities that are part of the input device API itself (e.g., text input for the keyboard API, pointer motion for the pointer API, etc.) [Priority 1] (Checkpoint 1.1)

Note. The device-independence required by this checkpoint applies to functionalities described by the other checkpoints in this document (e.g., installation, documentation, user agent user interface configuration, etc.). This checkpoint does not require user agents to use all operating system input device APIs, only to make the software accessible through those they do use.

May require developer documentation

• Microsoft Internet Explorer 5.0 for MS-Windows provides extensive keyboard and mouse support but does not provide device-independent access to all functionalities.
• Operasoft Opera 3.60 for MS-Windows provides extensive keyboard and mouse support but does not provide device-independent access to all functionalities.

Techniques for checkpoint 1.1

1.2 Use the standard input and output device APIs of the operating system. [Priority 1] (Checkpoint 1.2)

Do not bypass the standard output APIs when rendering information (e.g., for reasons of speed, efficiency, etc.). For example, do not bypass standard APIs to manipulate the memory associated with rendered content, since assistive technologies monitor rendering through the APIs.

May require developer documentation

No implementation information available.

Techniques for checkpoint 1.2

1.3 Ensure that the user can interact with all active elements in a device-independent manner. [Priority 1] (Checkpoint 1.3)

For example, users who are blind or have physical disabilities must be able to activate text links, the links in a client-side image map, and form controls without a pointing device. Note. This checkpoint is an important special case of checkpoint 1.1.

May require developer documentation

• Microsoft Internet Explorer 5.0 for MS-Windows: links and form controls
• Netscape Navigator 4.x for MS-Windows: links and form controls
• Operasoft Opera 3.6 for MS-Windows: links and form controls
• No known native support for device independent access to elements that can respond to scripting events.

Techniques for checkpoint 1.3

1.4 Ensure that every functionality available through the user interface is also available through the standard keyboard API. [Priority 1] (Checkpoint 1.4)

Note. This checkpoint is an important special case of checkpoint 1.1. The comment about low-level functionalities in checkpoint 1.1 applies to this checkpoint as well. Refer also to checkpoint 10.8.

May require developer documentation

• Microsoft Internet Explorer 5.0 for MS-Windows provides extensive keyboard support but does not provide keyboard access to all functionalities.
• Operasoft Opera 3.60 for MS-Windows provide extensive keyboard support but does not provide keyboard access to all functionalities.

Techniques for checkpoint 1.4

1.5 Ensure every non-text message (e.g., prompt, alert, etc.) available through the user interface also has a text equivalent in the user interface. [Priority 1] (Checkpoint 1.5)

Note. For example, if the user interface provides access to a functionality through a graphical button, ensure that a text equivalent for that button provides access to the same functionality from the user interface. If a sound is used to notify the user of an event, announce the event in text on the status bar as well. Refer also to checkpoint 5.7.

May require developer documentation

No implementation information available.

Techniques for checkpoint 1.5

Guideline 2. Ensure user access to all content.

Checkpoints for content accessibility:

2.1 Ensure that the user has access to all content, including equivalent alternatives for content. [Priority 1] (Checkpoint 2.1)

Refer to 5 for information about programmatic access to content.

May require developer documentation

• Microsoft Internet Explorer 5.0 provides access to some element attributes through context menus ("title" attribute used for tooltips)
• NN 4.61 on Linux: No, since attribute values not readily available and no support for longdesc. For HTML, "alt" is available as visual tool tip.
• Amaya allows users to view content and attribute values.

Techniques for checkpoint 2.1

2.2 For presentations that require user input within a specified time interval, allow the user to configure the time interval (e.g., to extend it or to cause the user agent to pause the presentation automatically and await user input before proceeding). [Priority 1] (Checkpoint 2.2)

• Real Player 7 (Version 6.0.7.362) Users can pause and resume (or restart) presentations as needed. No control over configuring pauses or slowing down presentation speed, however.

Techniques for checkpoint 2.2

2.3 When the author has not supplied a text equivalent for content as required by the markup language, make available other author-supplied information about the content (e.g., object type, file name, etc.). [Priority 2] (Checkpoint 2.3)

• Lynx renders the text "IMAGE" when no text equivalent is available for an HTML IMG element.
• Opera 3.60 for MS-Windows renders the text "IMAGE" when no text equivalent is available for an IMG element.

Techniques for checkpoint 2.3

2.4 When a text equivalent for content is explicitly empty (i.e., an empty string), render nothing. [Priority 3] (Checkpoint 2.4)

• Amaya seems to do this correctly for "alt".

Techniques for checkpoint 2.4

Checkpoints for user interface accessibility:

2.5 If more than one equivalent alternative is available for content, allow the user to choose from among the alternatives. This includes the choice of viewing no alternatives. [Priority 1] (Checkpoint 2.5)

• Real Player G2 and Real Player 7 (Version 6.0.7.362) allow users to select captions based on natural language.

For example, if a multimedia presentation has several captions (or subtitles) available, allow the user to choose from among them. Captions might differ in level of detail, address different reading levels, differ in natural language, etc.

Techniques for checkpoint 2.5

2.6 Allow the user to specify that text transcripts, collated text transcripts, captions, and auditory descriptions be rendered at the same time as the associated auditory and visual tracks. Respect author-supplied synchronization cues during rendering. [Priority 1] (Checkpoint 2.6)

• Real Player G2
• Microsoft Media Player

Techniques for checkpoint 2.6

2.7 For author-identified but unsupported natural languages, allow the user to request notification of language changes in content. [Priority 3] (Checkpoint 2.7)

• No information available.

Techniques for checkpoint 2.7

Guideline 3. Allow the user to turn off rendering or stop behavior that may reduce accessibility.

Checkpoints for content accessibility:

3.1 Allow the user to turn on and off rendering of background images. [Priority 1] (Checkpoint 3.1)

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• NN 4.61 for Linux: Yes, through style sheets or in the default file with *defaultBackgroundImage.
• Amaya allows users to turn off background image rendering through Show background images and style sheets.

Techniques for checkpoint 3.1

3.2 Allow the user to turn on and off rendering of background audio. [Priority 1] (Checkpoint 3.2)

• Microsoft Internet Explorer 5.0 for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• Amaya, through style sheets ('display: none')

Techniques for checkpoint 3.2

3.3 Allow the user to turn on and off rendering of video. [Priority 1] (Checkpoint 3.3)

• Microsoft Internet Explorer 5.0 for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• Amaya, through style sheets

Techniques for checkpoint 3.3

3.4 Allow the user to turn on and off rendering of audio. [Priority 1] (Checkpoint 3.4)

• Microsoft Internet Explorer 5.0 for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• Amaya, through style sheets

Techniques for checkpoint 3.4

3.5 Allow the user to turn on and off animated or blinking text. [Priority 1] (Checkpoint 3.5)

• Microsoft Internet Explorer 5.0 for MS-Windows does not recognize proprietary markup for blinking text content but does allow the user to turn off scripts that could be blinking text.
• Operasoft Opera 3.60 for MS-Windows does not recognize proprietary markup for blinking text content and allows the user to turn off scripts and style sheets that could cause text to be animated.
• NN 4.61 Linux: Yes, through the defaults file, set "*blinkingEnables: False".
• Amaya, for blinking accomplished through style sheets.

Techniques for checkpoint 3.5

3.6 Allow the user to turn on and off animations and blinking images. [Priority 1] (Checkpoint 3.6)

• Microsoft Internet Explorer 5.0 for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• NN 4.61 for Linux: Yes, through Preferences/Advanced menus. Enable Java and JavaScript. Also, possible to turn off images.

Techniques for checkpoint 3.6

3.7 Allow the user to turn on and off support for scripts and applets. [Priority 1] (Checkpoint 3.7)

Note. This is particularly important for scripts that cause the screen to flicker, since people with photosensitive epilepsy can have seizures triggered by flickering or flashing, particularly in the 4 to 59 flashes per second (Hertz) range.

• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• NN 4.61 for Linux: Yes, through the user interface (Preferences/Advanced).

Techniques for checkpoint 3.7

3.8 For automatic content changes specified by the author (e.g., redirection and content refresh), allow the user to slow the rate of change. [Priority 2] (Checkpoint 3.8)

• No information available.

Techniques for checkpoint 3.8

3.9 Allow the user to turn on and off rendering of images. [Priority 3] (Checkpoint 3.9)

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• NN 4.61 for Linux: Yes.
• Amaya, through style sheets at least.

Techniques for checkpoint 3.9

Guideline 4. Ensure user control of styles.

Checkpoints for fonts and colors:

4.1 Allow the user to configure the size of text. [Priority 1] (Checkpoint 4.1)

For example, allow the user to specify a font family and style directly through the user agent user interface or in a user style sheet. Or, allow the user to zoom or magnify content.

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows. Zoom feature.
• pwWebSpeak 2.5 for MS-Windows
• NN 4.61 for Linux: Yes, through style sheets and the user interface (Preferences/Appearances/Fonts).
• Amaya through style sheets

Techniques for checkpoint 4.1

4.2 Allow the user to configure font family. [Priority 1] (Checkpoint 4.2)

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• pwWebSpeak 2.5 for MS-Windows
• NN 4.61 for Linux: Yes, through style sheets and the user interface (Preferences/Appearances/Fonts).
• Amaya through style sheets

Techniques for checkpoint 4.2

4.3 Allow the user to configure foreground color. [Priority 1] (Checkpoint 4.3)

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• pwWebSpeak 2.5 for MS-Windows
• NN 4.61 for Linux: Yes, through style sheets, the user interface (Preferences/Appearance/Fonts), and, for text, in the defaults file (*defaultForeground).
• Amaya through style sheets

Techniques for checkpoint 4.3

4.4 Allow the user to configure background color. [Priority 1] (Checkpoint 4.4)

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• pwWebSpeak 2.5 for MS-Windows
• NN 4.61 for Linux: Yes, through style sheets, the user interface (Preferences/Appearance/Fonts), and, for text, in the defaults file (*defaultBackground).
• Amaya through style sheets

Techniques for checkpoint 4.4

Checkpoints for multimedia and audio presentations:

4.5 Allow the user to slow the presentation rate of audio, video, and animations. [Priority 1] (Checkpoint 4.5)

• Real Player G2
• Microsoft Media Player

Techniques for checkpoint 4.5

4.6 Allow the user to start, stop, pause, advance, and rewind audio, video, and animations. [Priority 1] (Checkpoint 4.6)

• Real Player G2 and Real Player 7 (Version 6.0.7.362)
• Microsoft Media Player

Techniques for checkpoint 4.6

4.7 Allow the user to configure the position of text transcripts, collated text transcripts, and captions on graphical displays. [Priority 1] (Checkpoint 4.7)

• No information available.

Techniques for checkpoint 4.7

4.8 Allow the user to configure the audio volume. [Priority 2] (Checkpoint 4.8)

• Real Player G2 and Real Player 7 (Version 6.0.7.362)
• Microsoft Media Player

Techniques for checkpoint 4.8

Checkpoints for synthesized speech:

4.9 Allow the user to configure synthesized speech playback rate. [Priority 1] (Checkpoint 4.9)

• Henter-Joyce Jaws 3.31 for MS-Windows
• GW-Micro Windoweyes 3.0 for MS-Windows
• AI-Squared Zoomtext 7.0 Level 2 for MS-Windows

Techniques for checkpoint 4.9

4.10 Allow the user to configure synthesized speech volume. [Priority 1] (Checkpoint 4.10)

• Henter-Joyce Jaws 3.31 for MS-Windows
• GW-Micro Windoweyes 3.0 for MS-Windows
• AI-Squared Zoomtext 7.0 Level 2 for MS-Windows

Techniques for checkpoint 4.10

4.11 Allow the user to configure synthesized speech pitch, gender, and other articulation characteristics. [Priority 2] (Checkpoint 4.11)

• Henter-Joyce Jaws 3.31 for MS-Windows
• GW-Micro Windoweyes 3.0 for MS-Windows
• AI-Squared Zoomtext 7.0 Level 2 for MS-Windows

Techniques for checkpoint 4.11

Checkpoints for user interface accessibility:

4.12 Allow the user to select from available author and user style sheets or to ignore them. [Priority 1] (Checkpoint 4.12)

Note. By definition the browser's default style sheet is always present, but may be overridden by author or user styles.

• Microsoft Internet Explorer 5.0 for MS-Windows
• Operasoft 3.60 for MS-Windows
• NN 4.61 for Linux: Turn of author styles only, through Preferences/Advanced: style sheets.
• Amaya allows you to select style sheets, disable, remove, open, link, etc.

Techniques for checkpoint 4.12

4.13 Allow the user to configure how the selection is highlighted (e.g., foreground and background color). [Priority 1] (Checkpoint 4.13)

• Microsoft Internet Explorer 5.0 for MS-Windows Windows 9x settings for highlight, which can be set by the user.
• NN 4.61 for Linux: Yes, in the defaults file set *selectForeground and *selectBackground.

Techniques for checkpoint 4.13

4.14 Allow the user to configure how the content focus is highlighted (e.g., foreground and background color). [Priority 1] (Checkpoint 4.14)

• Operasoft 3.60 for MS-Windows

Techniques for checkpoint 4.14

4.15 Allow the user to configure how the focus changes. [Priority 2] (Checkpoint 4.15)

For instance, allow the user to require that user interface focus not move automatically to a newly opened viewport.

• No information available.

Techniques for checkpoint 4.15

4.16 Allow the user to configure viewports, prompts, and windows opened on user agent initiation. [Priority 2] (Checkpoint 4.16)

For instance, allow the user to turn off viewport creation. Refer also to checkpoint 5.7.

• NN 4.61 for Linux: Partial support. In the defaults file, the *dontForceWindowStacking resource allows one to suppress some automatic window stacking caused by JavaScript window.open().

Techniques for checkpoint 4.16

Guideline 5. Observe system conventions and standard interfaces.

Checkpoints for content accessibility:

5.1 Provide programmatic read access to HTML and XML content by conforming to the W3C Document Object Model (DOM) Level 2 Core and HTML modules and exporting the interfaces they define. [Priority 1] (Checkpoint 5.1)

Note. These modules are defined in DOM Level 2 [DOM2], chapters 1 and 2. Please refer to that specification for information about which versions of HTML and XML are supported and for the definition of a "read-only DOM. For content other than HTML and XML, refer to checkpoint 5.3. This checkpoint is an important special case of checkpoint 2.1.

May require developer documentation

• Microsoft Internet Explorer 5.0 for MS-Windows provides access to the DOM through a COM interface. We have not verified whether the implementation conforms to the DOM specification.
• Amaya supports DOM
• Refer to the Java Weblets implementation of the DOM.
• Refer to the Xerces tool available from the Apache XML project.
• Refer to the 4DOM Library available from FourThought LLC.

Techniques for checkpoint 5.1

5.2 If the user can modify HTML and XML content through the user interface, provide the same functionality programmatically by conforming to the W3C Document Object Model (DOM) Level 2 Core and HTML modules and exporting the interfaces they define. [Priority 1] (Checkpoint 5.2)

For example, if the user interface allows users to complete HTML forms, this must also be possible through the DOM APIs. Note. These modules are defined in DOM Level 2 [DOM2], chapters 1 and 2. Please refer to DOM Level 2 [DOM2] for information about which versions of HTML and XML are supported. For content other than HTML and XML, refer to checkpoint 5.3. This checkpoint is an important special case of checkpoint 2.1.

May require developer documentation

• Microsoft Internet Explorer 5.0 for MS-Windows provides access to the DOM through a COM interface. We have not verified whether the implementation conforms to the DOM specification.
• Amaya supports DOM
• Refer to the Java Weblets implementation of the DOM.
• Refer to the Xerces tool available from the Apache XML project.
• Refer to the 4DOM Library available from FourThought LLC.

Techniques for checkpoint 5.2

5.3 For markup languages other than HTML and XML, provide programmatic access to content using standard APIs (e.g., platform-independent APIs and standard APIs for the operating system). [Priority 1] (Checkpoint 5.3)

Note. This checkpoint addresses content not covered by checkpoints checkpoint 5.1 and checkpoint 5.2. This checkpoint is an important special case of checkpoint 2.1.

May require developer documentation

• No information yet gathered (e.g., usage of MSAA).

Techniques for checkpoint 5.3

5.4 Provide programmatic access to Cascading Style Sheets (CSS) by conforming to the W3C Document Object Model (DOM) Level 2 CSS module and exporting the interfaces it defines. [Priority 3] (Checkpoint 5.4)

Note. This module is defined in DOM Level 2 [DOM2], chapter 5. Please refer to that specification for information about which versions of CSS are supported. This checkpoint is an important special case of checkpoint 2.1.

May require developer documentation

• Refer to Jackaroo (a Scalable Vector Graphics viewer) for DOM access to CSS 1 [CSS1].

Techniques for checkpoint 5.4

Checkpoints for user interface accessibility:

5.5 Provide programmatic read and write access to user agent user interface controls using standard APIs (e.g., platform-independent APIs such as the W3C DOM, standard APIs for the operating system, and conventions for programming languages, plug-ins, virtual machine environments, etc.) [Priority 1] (Checkpoint 5.5)

For example, ensure that assistive technologies have access to information about the user agent's current input configuration so that they can trigger functionalities through keyboard events, mouse events, etc.

May require developer documentation

• Microsoft Internet Explorer 5.0 for MS-Windows provides access through Microsoft Active Accessibility.

Techniques for checkpoint 5.5

5.6 Implement selection, content focus, and user interface focus mechanisms. [Priority 1] (Checkpoint 5.6)

Refer also to checkpoint 7.1 and checkpoint 5.5. Note. This checkpoint is an important special case of checkpoint 5.5.

• Most browsers do this (NN, IE, Amaya, Lynx, etc.)

Techniques for checkpoint 5.6

5.7 Provide programmatic notification of changes to content and user interface controls (including selection, content focus, and user interface focus). [Priority 1] (Checkpoint 5.7)

May require developer documentation

• Microsoft Internet Explorer 5.0 for MS-Windows provides access through Microsoft Active Accessibility.

Refer also to checkpoint 5.5.

Techniques for checkpoint 5.7

5.8 Ensure that programmatic exchanges proceed in a timely manner. [Priority 2] (Checkpoint 5.8)

For example, the programmatic exchange of information required by other checkpoints in this document must be efficient enough to prevent information loss, a risk when changes to content or user interface occur more quickly than the communication of those changes. The techniques for this checkpoint explain how developers can reduce communication delays, e.g., to ensure that assistive technologies have timely access to the document object model and other information needed for accessibility.

May require developer documentation

• For information about Microsoft IE 5.0, refer to http://support.microsoft.com/support/kb/articles/Q179/2/30.asp

Techniques for checkpoint 5.8

5.9 Follow operating system conventions and accessibility settings. In particular, follow conventions for user interface design, default keyboard configuration, product installation, and documentation. [Priority 2] (Checkpoint 5.9)

Refer also to checkpoint 10.2.

• Microsoft Internet Explorer 5.0 for MS-Windows inherits Windows 9x system and accessibility settings.

Techniques for checkpoint 5.9

Guideline 6. Implement accessible specifications.

Checkpoints for content accessibility:

6.1 Implement the accessibility features of supported specifications (markup languages, style sheet languages, metadata languages, graphics formats, etc.). [Priority 1] (Checkpoint 6.1)

May require developer documentation

• Real Player 7 (Version 6.0.7.362) implements SMIL 1.0

Techniques for checkpoint 6.1

6.2 Conform to W3C Recommendations when they are appropriate for a task. [Priority 2] (Checkpoint 6.2)

For instance, for markup, implement HTML 4.01 [HTML4] or XML 1.0 [XML]. For style sheets, implement CSS ([CSS1], [CSS2]). For mathematics, implement MathML [MATHML]. For synchronized multimedia, implement SMIL 1.0 [SMIL]. For access to the structure of HTML or XML documents, implement the DOM [DOM2]. Refer also to guideline 5.

Note. For reasons of backward compatibility, user agents should continue to support deprecated features of specifications. The current guidelines refer to some deprecated language features that do not necessarily promote accessibility but are widely deployed. Information about deprecated language features is generally part of the language's specification.

May require developer documentation

• Amaya does this for DOM, CSS, HTML, and MathML.

Techniques for checkpoint 6.2

Guideline 7. Provide navigation mechanisms.

Checkpoints for user interface accessibility:

7.1 Allow the user to navigate viewports (including frames). [Priority 1] (Checkpoint 7.1)

Note. For example, when all frames of a frameset are displayed side-by-side, allow the user to navigate among them with the keyboard. Or, when frames are accessed or viewed one at a time (e.g., by a text browser or speech synthesizer), provide a list of links to other frames. Navigating into a viewport makes it the current viewport.

• Lynx for UNIX (for frames).
• Microsoft Internet Explorer 5.0 for MS-Windows (for frames).
• Operasoft Opera 3.60 for MS-Windows (for frames).
• NN 4.61 for Linux: Yes: View/Page Source for frames in a single window. Navigation possible with the mouse. Navigation of history possible with a history window, a pulldown menu, and arrow icons (also possible with keyboard). Navigation of windows is done through the window manager (Alt-Tab in my configuration). It is not possible to navigate links sequentially in NN on Linux.

Techniques for checkpoint 7.1

7.2 For user agents that offer a browsing history mechanism, when the user returns to a previous viewport, restore the point of regard in the viewport. [Priority 1] (Checkpoint 7.2)

For example, when users navigate "back" and "forth" among viewports, they should find the viewport position where they last left it.

• Lynx for UNIX (for frames).
• Microsoft Internet Explorer 5.0 for MS-Windows (for frames).
• Operasoft Opera 3.60 for MS-Windows (for frames).

Techniques for checkpoint 7.2

7.3 Allow the user to navigate all active elements. [Priority 1] (Checkpoint 7.3)

Navigation may include non-active elements in addition to active elements. Note. This checkpoint is an important special case of checkpoint 7.6.

• Microsoft Internet Explorer 5.0 for MS-Windows, only for links and form controls.
• Netscape Navigator 4.x for MS-Windows, only for links and form controls.
• Operasoft Opera 3.60 for MS-Windows, only for links and form controls.

Techniques for checkpoint 7.3

7.4 Allow the user to choose to navigate only active elements. [Priority 2] (Checkpoint 7.4)

• Microsoft Internet Explorer 5.0 for MS-Windows, only for links and form controls.
• Netscape Navigator 4.x for MS-Windows only for links and form controls.
• NN 4.61 for Linux: No.
• Operasoft Opera 3.60 for MS-Windows, only for links and form controls.

Techniques for checkpoint 7.4

7.5 Allow the user to search for rendered text content, including rendered text equivalents. [Priority 2] (Checkpoint 7.5)

Note. Use operating system conventions for marking the result of a search (e.g., selection or content focus).

• Productivity Works pwWebSpeak 2.5 for MS-Windows will search alternative text.
• Most user agents do not include searching alternative text in their search functions.

Techniques for checkpoint 7.5

7.6 Allow the user to navigate according to structure. [Priority 2] (Checkpoint 7.6)

For example, allow the user to navigate familiar elements of a document: paragraphs, tables and table cells, headers, lists, etc. Note. Use operating system conventions to indicate navigation progress (e.g., selection or content focus).

• Opera for Windows: navigate headers or all elements
• W3C Amaya for MS-Windows.
• NN 4.61 for Linux: Only partly - View/Source gives some access to document structure, but not headers, etc.

Techniques for checkpoint 7.6

7.7 Allow the user to configure structured navigation. [Priority 3] (Checkpoint 7.7)

For example, allow the user to navigate only paragraphs, or only headers and paragraphs, etc.

• No information available.

Techniques for checkpoint 7.7

Guideline 8. Orient the user.

Checkpoints for content accessibility:

8.1 Make available to the user the author-specified purpose of each table and the relationships among the table cells and headers. [Priority 1] (Checkpoint 8.1)

For example, provide information about table headers, how headers relate to cells, table summary information, cell position information, table dimensions, etc. Refer also to checkpoint 5.3. Note. This checkpoint is an important special case of checkpoint 2.1.

• Jaws for Windows 3.5 with Microsoft Internet Explorer 5.0 for MS-Windows, for table header information.

Techniques for checkpoint 8.1

8.2 Indicate to the user whether a link has been visited. [Priority 2] (Checkpoint 8.2)

Note. This checkpoint is an important special case of checkpoint 8.4.

• NN 4.61 for Linux: Yes, colors controllable through style sheets, *vlinkForeground in the defaults file, and through the UI under Preferences/Appearance/Colors. From there you can also enable/disable underlining.
• Amaya yes, through colors at least.

Techniques for checkpoint 8.2

8.3 Indicate to the user whether a link has been marked up to indicate that following it will involve a fee. [Priority 2] (Checkpoint 8.3)

Note. This checkpoint is an important special case of checkpoint 8.4. The W3C specification "Common Markup for micropayment per-fee-links" [MICROPAYMENT] describes how authors may mark up micropayment information in an interoperable manner.

• No information available.

Techniques for checkpoint 8.3

8.4 To help the user decide whether to follow a link, make available link information supplied by the author and computed by the user agent. [Priority 3] (Checkpoint 8.4)

Information supplied by the author includes link content, link title, whether the link is internal, whether it involves a fee, and hints on the content type, size, or natural language of the linked resource. Information computed by the user agent includes whether the user has already visited the link. Note. User agents are not required to retrieve the resource designated by a link as part of computing information about the link.

• Operasoft Opera 3.60 for MS-Windows

Techniques for checkpoint 8.4

Checkpoints for user interface accessibility:

8.5 Provide a mechanism for highlighting and identifying (through a standard interface where available) the current viewport, selection, and content focus. [Priority 1] (Checkpoint 8.5)

Note. This includes highlighting and identifying frames. Note. This checkpoint is an important special case of checkpoint 1.1. Refer also to checkpoint 8.4.

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• NN 4.61 for Linux: Yes for selection and viewport, but graphically only. The selection is highlighted through colors. The viewport highlighted with a black outline.

Techniques for checkpoint 8.5

8.6 Make available to the user an "outline" view of content, built from structural elements (e.g., frames, headers, lists, forms, tables, etc.). [Priority 2] (Checkpoint 8.6)

For example, for each frame in a frameset, provide a table of contents composed of headers where each entry in the table of contents links to the header in the document. Note. The outline view does not have to be navigable, but if it is, it may satisfy checkpoint 7.6.

• W3C Amaya for MS-Windows
• Microsoft Internet Explorer 5.0 for MS-Windows with style sheets.
• Operasoft Opera 3.60 for MS-Windows

Techniques for checkpoint 8.6

8.7 Provide a mechanism for highlighting and identifying active elements (through a standard interface where available). [Priority 2] (Checkpoint 8.7)

Note. User agents may satisfy this checkpoint by implementing the appropriate style sheet mechanisms, such as link highlighting.

• Operasoft Opera 3.60 for MS-Windows allows for controlling link styles. No information about support for event handlers.

Techniques for checkpoint 8.7

8.8 Allow the user to configure the outline view. [Priority 3] (Checkpoint 8.8)

For example, allow the user to configure the level of detail of the outline. Refer also to checkpoint 8.6. Refer also to checkpoint 5.5.

• Microsoft Internet Explorer 5.0 for MS-Windows with style sheets
• Operasoft Opera 3.60 for MS-Windows with style sheets

Techniques for checkpoint 8.8

8.9 Allow the user to configure what information about links to present. [Priority 3] (Checkpoint 8.9)

Note. Do not use color as the only distinguishing factor between visited and unvisited links as some users may not perceive colors and some devices may not render them. Refer also to checkpoint 8.4.

• No information available.

Techniques for checkpoint 8.9

Guideline 9. Notify the user of content and viewport changes.

Checkpoints for user interface accessibility:

9.1 Ensure that when the selection or content focus changes, it is in a viewport after the change. [Priority 2] (Checkpoint 9.1)

For example, users navigating links may navigate to a portion of the document outside the viewport, so the viewport should scroll to include the new location of the focus.

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows

Techniques for checkpoint 9.1

9.2 Prompt the user to confirm any form submission triggered indirectly, that is by any means other than the user activating an explicit form submit control. [Priority 2] (Checkpoint 9.2)

For example, do not submit a form automatically when a menu option is selected, when all fields of a form have been filled out, or when a mouseover event occurs.

• No information available.

Techniques for checkpoint 9.2

9.3 Allow the user to configure notification preferences for common types of content and viewport changes. [Priority 3] (Checkpoint 9.3)

For example, allow the user to choose to be notified (or not) that a script has been executed, that a new viewport has been opened, that a pulldown menu has been opened, that a new frame has received focus, etc.

• No information available.

Techniques for checkpoint 9.3

9.4 When loading content (e.g., document, image, audio, video, etc.) indicate what portion of the content has loaded and whether loading has stalled. [Priority 3] (Checkpoint 9.4)

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• NN 4.61 for Linux: Yes. Indicates visually in status bar at bottom of browser the percentage of a page loaded, the amount loaded, and whether loading has stalled or terminated. I do not know whether this information is made available through an interface.
• The Real Player 7 (Version 6.0.7.362) status bar includes loading information, elapsed and total time, and whether clip is a live broadcast.

Techniques for checkpoint 9.4

9.5 Indicate the relative position of the viewport in rendered content (e.g., the percentage of an audio or video clip that has been played, the percentage of a Web page that has been viewed, etc.). [Priority 3] (Checkpoint 9.5)

Note. The user agent may calculate the percentage according to content focus position, selection position, or viewport position, depending on how the user has been browsing.

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• RealPlayer G2
• The Real Player 7 (Version 6.0.7.362) status bar shows elapsed time and total clip time.
• Microsoft Media Player
• Amaya, graphically.

Techniques for checkpoint 9.5

Guideline 10. Allow configuration and customization.

Checkpoints for user interface accessibility:

10.1 Provide information to the user about current user preferences for input configurations (e.g., keyboard or voice bindings). [Priority 1] (Checkpoint 10.1)

• Microsoft Word for Windows 97 (not a WWW browser, but demonstrates concept).
• Amaya does this the "brute force" way since attribute values are available to the user.

Techniques for checkpoint 10.1

10.2 Avoid default input configurations that interfere with operating system accessibility conventions. [Priority 1] (Checkpoint 10.2)

In particular, default configurations should not interfere with the mobility access keyboard modifiers reserved for the operating system. Refer also to guideline 5.

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows

Techniques for checkpoint 10.2

10.3 Provide information to the user about current author-specified input configurations (e.g., keyboard bindings specified in content such as by "accesskey" in HTML). [Priority 2] (Checkpoint 10.3)

• Amaya does this the brute force way by providing information about attribute values.

Techniques for checkpoint 10.3

10.4 Allow the user to change the input configuration. [Priority 2] (Checkpoint 10.4)

For voice-activated browsers, allow the user to modify which voice commands activate functionalities. Similarly, allow the user to modify the graphical user agent user interface for quick access to commonly used functionalities (e.g., through buttons). Refer also to checkpoint 10.5 and checkpoint 10.9.

• No information available.

Techniques for checkpoint 10.4

10.5 Allow the user to configure the user agent so that the user's preferred one-step operations may be activated with a single input command (keystroke, voice command, etc.). [Priority 2] (Checkpoint 10.5)

Note. User agents are not required to provide single command activation of all user agent functionalities at once, only some of them. This checkpoint is an important special case of checkpoint 10.4.

• No information available.

Techniques for checkpoint 10.5

10.6 Follow operating system conventions to indicate the input configuration. [Priority 2] (Checkpoint 10.6)

For example, on some operating systems, if a functionality is available from a menu, the letter of the key that will activate that functionality is underlined. Note. This checkpoint is an important special case of checkpoint 5.9.

• Microsoft Internet Explorer 5.0 for MS-Windows
• Netscape Navigator 4.x for MS-Windows
• Operasoft Opera 3.60 for MS-Windows

Techniques for checkpoint 10.6

10.7 For the configuration requirements of this document, allow the user to save user preferences a profile. [Priority 2] (Checkpoint 10.7)

Note. This includes user preferences for styles, presentation rates, input configurations, navigation, views, and notification. Users must be able to select from among available profiles or no profile (i.e., the user agent default settings).

• Microsoft Internet Explorer 5.0 for MS-Windows does, for information that can be contained in user style sheets.
• Operasoft Opera 3.60 for MS-Windows does, for information that can be contained in user style sheets.
• NN 4.61 for Linux: Yes, since configuration is done through XResources, users can specify their own resources.
• Amaya offers profiles

Techniques for checkpoint 10.7

10.8 Ensure that frequently used functionalities are easily activated in the default input configuration. [Priority 3] (Checkpoint 10.8)

Make the most frequent operations easy to access and operable through a single command.

• Microsoft Internet Explorer 5.0 for MS-Windows
• Operasoft Opera 3.60 for MS-Windows

Techniques for checkpoint 10.8

10.9 Allow the user to configure the arrangement of graphical user agent user interface controls. [Priority 3] (Checkpoint 10.9)

Note. This checkpoint is an important special case of checkpoint 10.4.

• NN 4.51 for Linux: Yes. It's possible to:
  • View the toolbar a certain way (refer to Preferences/Appearance)
  • Control the position of the tool bar
  • Add menus to the tool bar
  • Control text of menus and existence of menus in the defaults file. E.g., "*Composition*toggleNavigationToolbar.mnemonic: T"

Techniques for checkpoint 10.9

Guideline 11. Provide accessible product documentation and help.

Checkpoints for user interface accessibility:

11.1 Provide a version of the product documentation that conforms to the Web Content Accessibility Guidelines 1.0 [WCAG10]. [Priority 1] (Checkpoint 11.1)

User agents may provide documentation in many formats, but at least one must conform to the Web Content Accessibility Guidelines 1.0 [WCAG10].

May require developer documentation

• Amaya documentation is available in HTML.

Techniques for checkpoint 11.1

11.2 Document all user agent features that promote accessibility. [Priority 1] (Checkpoint 11.2)

For example, review the documentation or help system to ensure that it includes information about the accessibility features discussed in this document.

May require developer documentation

• Microsoft Internet Explorer 5.0 for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• Refer to the Amaya accessibility page.

Techniques for checkpoint 11.2

11.3 Document the default input configuration (e.g., default keyboard bindings). [Priority 1] (Checkpoint 11.3)

May require developer documentation

• Microsoft Internet Explorer 5.0 for MS-Windows
• Operasoft Opera 3.60 for MS-Windows
• Lynx for UNIX
• pwWebSpeak
• NN 4.61 for Linux: The default bindings are listed in the default configuration file.

Techniques for checkpoint 11.3

11.4 In a dedicated section of the documentation, describe all features of the user agent that promote accessibility. [Priority 2] (Checkpoint 11.4)

Note. This is a more specific requirement than checkpoint 11.2.

May require developer documentation

• Microsoft Internet Explorer 5.0 for MS-Windows: Built-in Accessibility Features.
• Opera 3.6x
• Refer to the Amaya accessibility page.
• NN 4.61: No, refer to the help page for Netscape Communicator.

Techniques for checkpoint 11.4

11.5 Document changes between software releases. [Priority 2] (Checkpoint 11.5)

• Real Player 7 (Version 6.0.7.362) includes a section called "What's New" which reviews new features and changes to the interface.

Techniques for checkpoint 11.5

3. References

For the latest version of any W3C specification please consult the list of W3C Technical Reports at http://www.w3.org/TR.

[CSS1]

"CSS, level 1 Recommendation", B. Bos, H. Wium Lie, eds., 17 December 1996, revised 11 January 1999. This CSS 1 Recommendation is http://www.w3.org/TR/1999/REC-CSS1-19990111.

[CSS2]

"CSS, level 2 Recommendation", B. Bos, H. Wium Lie, C. Lilley, and I. Jacobs, eds., 12 May 1998. This CSS 2 Recommendation is http://www.w3.org/TR/1998/REC-CSS2-19980512.

[DOM2]

"Document Object Model (DOM) Level 2 Specification", L. Wood, A. Le Hors, V. Apparao, L. Cable, M. Champion, J. Kesselman, P. Le Hégaret, T. Pixley, J. Robie, P. Sharpe, C. Wilson, eds. The latest version of the specification is available at: http://www.w3.org/TR/DOM-Level-2.

[HTML4]

"HTML 4.01 Recommendation", D. Raggett, A. Le Hors, and I. Jacobs, eds. The 24 December 1999 HTML 4.01 Recommendation is http://www.w3.org/TR/1999/REC-html401-19991224

[MATHML]

"Mathematical Markup Language", P. Ion and R. Miner, eds. The 7 April 1998 MathML 1.0 Recommendation is http://www.w3.org/TR/1998/REC-MathML-19980407

[MICROPAYMENT]

"Common Markup for micropayment per-fee-links", T. Michel, ed. The latest version of this W3C Working Draft is available at http://www.w3.org/TR/Micropayment-Markup.

[SMIL]

"Synchronized Multimedia Integration Language (SMIL) 1.0 Specification", P. Hoschka, editor. The 15 June 1998 SMIL 1.0 Recommendation is http://www.w3.org/TR/1998/REC-smil-19980615

[UAAG10-TECHS]

"Techniques for User Agent Accessibility Guidelines 1.0," J. Gunderson, I. Jacobs, eds. The latest draft of the techniques document is available at http://www.w3.org/WAI/UA/UAAG10-TECHS/

[WCAG10]

"Web Content Accessibility Guidelines 1.0", W. Chisholm, G. Vanderheiden, and I. Jacobs, eds. The 5 May 1999 Recommendation is http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505

[XML]

"Extensible Markup Language (XML) 1.0.", T. Bray, J. Paoli, C.M. Sperberg-McQueen, eds. The 10 February 1998 XML 1.0 Recommendation is http://www.w3.org/TR/1998/REC-xml-19980210