Final Proposed Re-Wording for Access Module - Section 3.1.2.

as amended by the XHTML2 WG on 2008/05/14

http://www.w3.org/2008/05/14-xhtml-minutes#item06

and the UAWG on 2008/05/15

http://www.w3.org/2008/05/15-ua-minutes

<REV 
cite="http://www.w3.org/WAI/UA/wiki/AccessModule/KeyMappingBinding">
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 
[1] for information on how the element may be activated). Note that it 
is possible to deliver alternate events via XMLEVENTS. [2]

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. [3] 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). [4] 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).  [5] [6]
</REV>

Hyperlinks for Section 3.1.2.
[1] http://www.w3.org/TR/xhtml-access/#sec_3.1.1
[2] http://www.w3.org/TR/xhtml-access/#ref_XMLEVENTS
[3] http://www.w3.org/TR/UAAG10/guidelines.html#tech-configure-no-handlers
[4] http://www.w3.org/TR/UAAG10/guidelines.html#tech-configure-input
[5] http://www.w3.org/TR/UAAG10/guidelines.html#tech-info-current-ua-config
[6] http://www.w3.org/TR/UAAG10/guidelines.html#tech-info-current-author-config

----------------------------------------------------------
ACCOUNTABILITY, n. The mother of caution.
                 -- Ambrose Bierce, The Devil's Dictionary
----------------------------------------------------------
         Gregory J. Rosmaita, oedipus@hicom.net
      Camera Obscura: http://www.hicom.net/~oedipus/
   Read 'Em & Speak: http://www.hicom.net/~oedipus/books/
----------------------------------------------------------

Received on Friday, 16 May 2008 16:31:24 UTC