This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13594 - Handling of duplicate keyboard shortcuts
Summary: Handling of duplicate keyboard shortcuts
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Greg Lowney
QA Contact: HTML WG Bugzilla archive list
Keywords: a11y, a11y_focus, a11y_ua
Depends on:
Reported: 2011-08-03 06:53 UTC by Greg Lowney
Modified: 2014-02-26 18:57 UTC (History)
9 users (show)

See Also:


Description Greg Lowney 2011-08-03 06:53:46 UTC
While we can and should define mechanisms to let dynamic content, add-ins and the like negotiate to try to avoid conflicts, they may still occur at times. With HTML4 and below, the behavior in such circumstances is left undefined, and consequently is handled differently by different user agents and so cannot be planned for. By contrast, native applications can count on specific, platform behaviors; for example, on Windows if a menu has two items with the same underlined accelerator key, the user knows that pressing the key will move the focus sequentially between them, and they can activate the one with the focus by pressing the Enter key. 

Issue: Should the author be able to suggest ways to handle shortcut conflicts? If an author could specify that pressing a shortcut would move focus sequentially between the elements that have that accesskey, and wrap, they author could design keyboard UI to take advantage of this in a way that is not otherwise possible. On the other hand, issues such as whether sequential navigation wraps should ideally be under the user's control, since wrapping is a significant advantage to some users (e.g. those who need to minimize the number of input commands) but a disadvantage to others (such as those who may not be able to tell when wrapping has occurred). Should the HTML5 spec state instead that user agents should follow platform conventions?
Comment 1 Michael[tm] Smith 2011-08-04 05:02:59 UTC
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-12-01 23:45:36 UTC
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:

Status: Did Not Understand Request
Change Description: no spec change
Rationale: Do you have a concrete example of a page where this problem exists? I don't think I have a full grasp of the request here.