RE: issues with global attribute "accesskey" as-is in HTML5

aloha, paul!

i'll try and log the issues i outlined as soon as i get a chance to
convert the review into bug reports, which i hope to have logged well
in advance of the next TF meeting...

i am going to file an additional bug "is @accesskey irretrievably broken 
as an attribute?", based on discussion on

http://www.w3.org/WAI/PF/HTML/wiki/Talk:Access/access_key_requirements

an issue which is closely tied to what i identified in my initial post 
as: "ISSUE 4. HTML5 hard-binds "Action" to accesskey key-press"

which addresses the utility of the Access Module/Element's boolean 
attribute @activate, which provides for author control over whether 
the firing of an accesskey moves focus to or activates the element 
for which the accesskey has been defined, as well as the Access 
Module/Element's explicit stipulation:

QUOTE src="http://www.w3.org/TR/xhtml-access/#sec_3.1.1."
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 per Checkpoint 9.5 of UAAG 1.0)
UNQUOTE

NB: proposed Access Element draft, which is applicable to XML-derived
dialects and may or may not be applicable to HTML5, is located at: (obscenely 
long URI warning:

http://lists.w3.org/Archives/Public/www-archive/2010May/att-0020/access-element-20100519.html

gregory.
-------------------------------------------------------
BRAIN, n.  An apparatus with which we think we think.
             -- Ambrose Bierce, The Devil's Dictionary
-------------------------------------------------------
        Gregory J. Rosmaita, oedipus@hicom.net
    Camera Obscura: http://www.hicom.net/~oedipus/
Oedipus' Online Complex: http://my.opera.com/oedipus/
-------------------------------------------------------