• ConfigAndCustom

Guideline 11. Allow configuration and customization

11.1 Current user input configuration (P1)

1. Provide information to the user about current user preferences for input configurations.

Sufficient techniques

1. To satisfy this checkpoint, the user agent may make available binding information in a centralized fashion (e.g., a list of bindings) or a distributed fashion (e.g., by listing keyboard shortcuts in user interface menus). See related documentation checkpoints 12.2, 12.3, and 12.5.

Normative inclusions and exclusions

1. Conformance detail: For user agent features

UAAG2 ISSUES

11.2 Current author input configuration (P2)

1. Provide a centralized view of the current author-specified input configuration.

Sufficient techniques

1. The user agent may satisfy this checkpoint by providing different views for different input modalities (keyboard, pointing device, and voice).

Normative inclusions and exclusions

1. Conformance detail: For all content

Notes

• For example, for HTML documents, provide a view of keyboard bindings specified by the author through the accesskey attribute. The intent of this checkpoint is to centralize information about author-specified bindings so that the user does not have to read an entire document to learn about available bindings.

UAAG2 ISSUES

• Should the user be able to override (change) these input configurations in the UA
• How should UA expose author specified keybindings that occur in javascript or other scripting which are not exposed in the DOM or to accessibility APIs. [should the be a WCAG requirement?]

11.3 Allow override of bindings (P2)

1. Allow the user to override any binding that is part of the user agent default input configuration.

Normative inclusions and exclusions

1. The user agent is not required to allow the user to override conventional bindings for the operating environment (e.g., for access to help).
2. The override requirement only applies to bindings for the same input modality (e.g., the user must be able to override a keyboard binding with another keyboard binding).
3. This checkpoint excludes the requirements of checkpoint 11.4.
4. Conformance detail: For user agent features

Notes

• See checkpoint 11.5 for default input configuration requirements and checkpoint 12.3 for information about their documentation.

UAAG2 ISSUES

• move 'doing more' 2. Allow users to easily restore the default input configuration.

to be a Normative Inclusion

• add Normative Inclusion: When user overrides a binding the UA must update the current iinput configuration (in order to meet 11.1 requiarements)

11.4 Single-key access (P2)

1. Allow the user to override any binding in the user agent default keyboard configuration with a binding to either a key plus modifier keys or to a single key.
2. For each functionality in the set required by checkpoint 11.5, allow the user to configure a single-key binding. A single-key binding is one where a single key press performs the task, with zero modifier keys.

Sufficient techniques

1. The user agent may satisfy the requirements of provision two of this checkpoint with a "single-key mode." In a single-key mode, the complete set of functionalities required by provision two must be available through single-key bindings. The user must be able to remain in single-key mode until explicitly requesting to leave it.

Normative inclusions and exclusions

1. In this checkpoint, "key" refers to a physical key of the keyboard (rather than, say, a character of the document character set).
2. The user agent is not required to allow the user to override conventional bindings for the operating environment (e.g., for access to help).
3. Provision two of this checkpoint does not require single physical key bindings for character input, only for the activation of user agent functionalities.
4. If the number of physical keys on the keyboard is less than the number of functionalities required by checkpoint 11.5, then provision two of this checkpoint does not require the user agent to allow single-key bindings for all of the functionalities. The user agent should give preference to those functionalities listed in provision one of checkpoint 11.5.
5. This checkpoint is mutually exclusive of checkpoint 11.3 since it is specific to the keyboard and to emphasize the importance of easy keyboard access.
6. Conformance detail: For user agent features

Notes

• Because single-key access is so important to some users with physical disabilities, user agents should ensure that: (1) most keys of the physical keyboard may be configured for single-key bindings, and (2) most functionalities of the user agent may be configured for single-key bindings. For information about access to user agent functionality through a keyboard API, see checkpoint 6.7.

UAAG2 ISSUES

11.5 Default input configuration (P2)

1. Ensure that the user agent default input configuration includes bindings for the following functionalities required by other checkpoints in this document:
   • move content focus to the next enabled element in document order, and move content focus to the previous enabled element in document order (checkpoints 9.3 and 9.7);
   • activate the link designated by the content focus (checkpoints 1.1 and 9.1);
   • search for text, search again for same text (checkpoint 9.8);
   • increase the scale of rendered text, and decrease the scale of rendered text (checkpoint 4.1);
   • increase global volume, and decrease global volume (checkpoint 4.7); and
   • stop, pause, resume, and navigate efficiently selected audio and animations, including video and animated images (checkpoint 4.5).
2. If the user agent supports the following functionalities, the default input configuration must also include bindings for them:
   • next history state (forward), and previous history state (back);
   • enter a URI for a new resource;
   • add a URI to favorites (i.e., bookmarked resources);
   • view favorites;
   • reload a resource;
   • interrupt a request to load or reload a resource;
   • for graphical viewports: navigate forward and backward through rendered content by approximately the height of the viewport; and
   • for user agents that render content in lines of (at least) text: move the point of regard to the next and previous line.

Sufficient techniques

1. The user agent may satisfy the functionality of entering a URI for a new resource in a number of ways, including by prompting the user or by moving the user interface focus to a control for entering URIs.

Normative inclusions and exclusions

1. Conformance detail: For user agent features

Notes

• This checkpoint does not make any requirements about the ease of use of default input configurations, though clearly the default configuration should include single-key bindings and allow easy operation. Ease of use is addressed by the configuration requirements of checkpoint 11.3.

UAAG2 ISSUES

11.6 User profiles (P2)

1. For the configuration requirements of this document, allow the user to save user preferences in at least one user profile.
2. Allow the user to choose from among available user agent default profiles, profiles created by the same user, and no profile (i.e., the user agent default settings).

Normative inclusions and exclusions

1. This checkpoint does not require the user agent to provide multiple default profiles.
2. This checkpoint does not require that user profiles be portable (i.e., removable from the user agent to be reread by a different instance of the user agent). Portable user profiles are very useful, however.
3. Conformance detail: For user agent features

UAAG2 ISSUES

11.7 Tool bar configuration (P3)

1. For graphical user agent user interfaces with tool bars, allow the user to configure the position of user agent user interface controls on those tool bars.
2. Offer a predefined set of controls that may be added to or removed from tool bars.
3. Allow the user to restore the default tool bar configuration.

Normative inclusions and exclusions

1. Conformance detail: For user agent features

UAAG2 ISSUES