XHTML Access Module: Key Mapping & User Control
Contents
Current Wording
Source: XHTML Access Module, Section 3.1.2.
3.1.2. key = Character
This attribute assigns a key mapping to an access shortcut. An access key is a single character from the document character set. Note: Authors should consider the input method of the expected reader when specifying an accesskey.
Triggering an access key defined in an access element changes focus to the next element in navigation order from the current focus that has one of the the referenced role or id values. Note that it is possible to deliver alternate events via XMLEVENTS. It is also possible to have the target element activated through the use of the activate attribute. Finally, it is possible to associate additional event handlers with targets which might then perform additional actions once focus is changed.
If neither a targetrole nor a targetid attribute are specified, the user agent MUST NOT define a mapping nor deliver any events.
An access element must have either a targetrole or a targetid attribute specified.
The invocation of access keys depends on the implementation. For instance, on some systems one may have to press the "alt" key in addition to the access key. On other systems, one generally has to press the "cmd" key in addition to the access key.
The rendering of access keys depends on the user agent. We recommend that authors include the access key in label text or wherever the access key is to apply. User agents should render the value of an access key in such a way as to emphasize its role and to distinguish it from other characters (e.g., by underlining it).
The character assigned to a key, and its relationship to a role or id attribute, are a suggestion of the author. User agents may provide mechanisms for overriding, disabling, or re-assigning keys. In such user agents, user-specified assignments must take precendence [sic]. If no key attribute is specified, the user agent SHOULD assign a key.
Proposed Re-Wording
3.1.2. key = Character
This attribute assigns a key mapping to an access shortcut. An access key is a single character from the document character set.
Triggering the access key defined in an access element moves focus from its current position to the next element in navigation order that has one of the referenced role or id values (consult Section 3.1.1, Activate for information on how the element may be activated). Note that it is possible to deliver alternate events via XMLEVENTS.
The invocation of access keys depends on the implementation. For instance, on some systems one may have to press an "alt" or "cmd" key in addition to the access key.
User agents MUST provide mechanisms for overriding the author setting with user-specified settings in order to ensure that the act of moving content focus does not cause the user agent to take any further action, as required by UAAG 1.0, Checkpoint 9.5. The character assigned to a key, and its relationship to a role or id attribute SHOULD be treated as an author suggestion. User agents may override any key assignment (e.g., if an assignment interferes with the operation of the user interface of the user agent, if the key is not available on a device, if a key is used by the operating environment). User agents SHOULD also allow users to override author assigned keys with their own key assignments (UAAG 1.0, Checkpoint 11.3). If a user chooses to change the key binding, the resultant user-defined remapping SHOULD persist across sessions.
If no key attribute is specified, the user agent SHOULD assign a key and alert the user to the key mapping and the resultant user agent assigned key SHOULD persist.
The rendering of access keys depends on the user agent. We recommend that authors include the access key character in label text or wherever the access key is to apply. If the user agent can recognize that the currently mapped access key character appears in the label text of the element to which it is mapped, then the user agent may render the character in such a way as to emphasize its role as the access key and distinguish it from other characters (e.g., by underlining it).
A conforming user agent SHOULD also provide a centralized view of the current access key assignments (UAAG 1.0 Checkpoint 11.1, UAAG 1.0 Checkpoint 11.2).
Pertitent UAAG 2.0 Principles & Success Criteria
Note: We must ensure that the following principles are adequately covered by the preceding proposed re-wording.
UAAG 2.0 - 4.1.10 User Override any Binding: The user can override any binding that is part of the user agent default input configuration except for conventional bindings for the operating environment (e.g., for access to help) or author-specified bindings. The keyboard combinations offered for rebinding include single key and key plus modifier keys if these are available in the operating environment. (Level AA)
Note: The wording above reflects Jim's proposed re-wording for the extant UAAG 2.0 - 4.1.10
Note: Thanks to Jim Allan, Kelly Ford, Al Gilman, and Jan Richards for their input on this issue. Thanks, as well, to the User Agent Accessibility Guidelines Group for their attention to detail and invaluable contributions.
For UAWG Review: Access Element | Activate Attribute | Key Mapping/Binding