Proposed modification to Guideline 1 and Guideline 2

Background

The following proposal attempts to address a number of concerns about Guidelines 1 and 2 that were raised by Marja Koivunen (refer to Marja's message of 29 September 1999. See also Marja's comments on Guidelines 1 and 2 upon which this proposal is founded. It also takes into account changes proposed by Rich Schwerdtfeger.

The goals of this proposal are the following:

Why make this proposal now?

Notes on the proposal

Summary of the fate of old checkpoints:

2. User Agent Accessibility Guidelines

Guideline 1. Support input and output device-independence

1.1 Ensure that all functionalities offered through the user interface are available through input device APIs implemented by the user agent. Functionalities include installation procedures, control of the user interface, access to documentation, and configuration. [Priority 1]
Note. Functionalities include being able to show, hide, resize and move graphical viewports created by the user agent.
Note. The device-independence required by this checkpoint applies to functionalities described by the other checkpoints in this document unless otherwise stated by individual checkpoints.
1.2 Ensure that the user can interact with all active elements in a device independent manner. [Priority 1]
For example, ensure that the user can activate links of a client-side image map in a device-independent manner (e.g., by making them available as text links).
1.3 Support standard input and output device APIs for the operating system.
[Priority 1]
Note. What is "standard" for a particular environment will change over time. Today, for example, the mouse and keyboard are standard in a graphical desktop computer environment. Tomorrow, voice input and output may be standard. For a small device, standard input may come from a pen or keypad, and output through an LCD screen.
1.4 Ensure that all functionalities offered through the user interface are available through the standard keyboard API.
1.5 Ensure that information output as part of operating the user agent is available through ouput device APIs implemented by the user agent. [Priority 1]
For instance, users must be able to operate the user agent without relying on two-dimensional graphical output, cursor position, etc. User agents must ensure that information about how much of a page or video clip has been viewed is available through output device APIs. Proportional navigation bars may provide this information visually, but the information must be available to users relying on synthesized speech or braille output.

Guideline 11. Allow the user to configure the user agent

11.1 Document the default input configuration for the keyboard, graphical user interface, voice commands, etc. [Priority 1]
11.2 Provide information to the user about the current input configuration for the keyboard, graphical user interface, voice commands, etc. [Priority 1]
The current configuration is the result of a cascade of author-specified user interface information (e.g., "accesskey" or "tabindex" in HTML), browser defaults, and user-modified settings.
11.3 Allow the user to control the input configuration for standard input devices, including the keyboard, graphical user interface, voice commands, etc. "One stroke" access should be possible, for example a single key stroke, voice command, or button to activate an important functionality. [Priority 2]
11.4 Use system conventions to provide information to the user about the current input configuration for the keyboard, graphical user interface, voice commands, etc. [Priority 2]
For example, on some platforms, if a functionality is available from a menu, the letter of the key that will activate that functionality is underlined.
11.5 Avoid default keyboard, graphical user interface, voice, or other input configurations that interfere with or deviate from system conventions. [Priority 2]
For example, the default configuration should not include "Alt-F4" or "Control-Alt-Delete" on systems where that combination has special meaning to the operating system. In particular, default configurations should not interfere with the mobility access keyboard modifiers reserved for the operating system. Refer also to guideline 6.
11.6 Allow the user to configure the user agent in named profiles that may be shared (by other users or software). [Priority 2]
Users must be able to select from among available profiles or no profile (i.e., the user agent default settings).
11.7 Provide default keyboard, graphical user interface, voice, and other input configurations for frequently performed operations. [Priority 3]
11.8 Allow the user to configure the graphical arrangement of user interface controls. [Priority 3]

Glossary

Input configuration
This refers to the mapping between user agent functionality and activation method. This includes mapping to keyboard shortcuts, to buttons, to voice commands, etc. Input configurations should help users remember which functionalities are available and should allow them to access those functionalities quickly, and for any supported input or output device.
Standard Input and Output Devices
The devices users are expected to use with the operating system and its standard user interface. Operating systems provide standard APIs to these devices to be used by applications.

Ian Jacobs
Last modified: $Date: 2000/11/08 07:48:45 $