This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
as part of the substeps to run for each value in keys, in the order the tokens appeared in the attribute's value: QUOTE 3. If the user agent can find a combination of modifier keys that, with the key that corresponds to the value given in the attribute, can be used as a shortcut key, then the user agent may assign that combination of keys as the element's assigned access key and abort these steps. UNQUOTE what does this subset mean? it should precisely address the following: 1. does this subset require a user agent to automatically determine a modifier or combination of modifier keys? 2. if so, is this so as to avoid conflicts with application and operating system hotkeys? 3. if the user agent automatically determines a modifier or combination of modifier keys, how will this information be conveyed to the user 4. does the user retain control over which modifier key or combination of modifier keys the user agent uses?
> 1. does this subset require a user agent to automatically determine > a modifier or combination of modifier keys? No. If it did, it would say so. > 2. if so, is this so as to avoid conflicts with application and > operating system hotkeys? n/a > 3. if the user agent automatically determines a modifier or combination > of modifier keys, how will this information be conveyed to the user This is discussed in other parts of the specification. > 4. does the user retain control over which modifier key or combination > of modifier keys the user agent uses? The user and user agent in concert do so, yes. EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: As far as I can tell this is all addressed already.
The HTML A11y Bug Triage Subteam decided that this not an issue and that Gregory should escalate this bug if he feels it is warranted.
This has been changed [1], since the HTML5 approach was broken both in principle - user agents don't *know* what the user's keyboartd has available, let alone whether a key is actually a *shortcut* - and in practice since what cannot work is unlikely to do so, and indeed didn't. [1] https://github.com/w3c/html/pull/87