W3C home > Mailing lists > Public > public-html@w3.org > August 2011

[Bug 13594] New: Handling of duplicate keyboard shortcuts

From: <bugzilla@jessica.w3.org>
Date: Wed, 03 Aug 2011 06:53:46 +0000
To: public-html@w3.org
Message-ID: <bug-13594-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13594

           Summary: Handling of duplicate keyboard shortcuts
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: a11y, a11ytf
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: gcl-0039@access-research.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, public-html-a11y@w3.org


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?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 3 August 2011 06:53:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:37 GMT