W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2011

Re: HTML5 Sanity Check - before it goes to the Wiki

From: Simon Harper <simon.harper@manchester.ac.uk>
Date: Thu, 16 Jun 2011 17:18:12 +0100
Message-ID: <4DFA2CC4.8060902@manchester.ac.uk>
To: Markku Hakkinen <mhakkinen@acm.org>
CC: UAWG list <w3c-wai-ua@w3.org>
Hi Mark, I see what you are saying but the sequence is implied in that 
alt+f focuses the file menu - while S selects the access key of the 
items currently in focus. Without this alf f would open the file while S 
might start a search (or whatever) or do nothing... This is the kind of 
usability based progressive disclosure functionality I was getting at.

However, is the menu keyboard handle defined in html5 or other tech - ie 
the focus will be kept once say Alt+f is selected?


Simon Harper

University of Manchester (UK)
Web Ergonomics Lab - Information Management Group

On 16/06/2011 16:36, Markku Hakkinen wrote:
> Simon,
> Just a comment on 3.2.3
> On Thu, Jun 16, 2011 at 6:08 PM, Simon Harper
> <simon.harper@manchester.ac.uk>  wrote:
>> 3.2.3 Global attributes
>> accesskey - By only allowing an accessskey for be one unicode character we
>> remove the possibly of sequenced entry such as Alt+F S for file save.
> A sequence such as Alt+F S is activating two UI elements in sequence,
> the File menu followed by the Save sub menu item.. Although you are
> hitting them in sequence, and you the user may perhaps internally
> recall the key sequence as a combination to invoke the save action, it
> does not imply that the Save menu choice has an access key, or
> shortcut, property value of "Alt+F S".
> The handling of sequenced keys should be in the menu keyboard handler,
> not through assigning sequences to a given item.
> mark
Received on Thursday, 16 June 2011 16:18:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:40 UTC