W3C home > Mailing lists > Public > public-html@w3.org > June 2009

Re: accesskey should always define a command

From: Simon Pieters <simonp@opera.com>
Date: Mon, 22 Jun 2009 14:46:49 +0200
To: "public-html@w3.org" <public-html@w3.org>
Message-ID: <op.uvxe4b0jidj3kv@zcorpandell.linkoping.osa>
On Mon, 22 Jun 2009 14:39:59 +0200, Simon Pieters <simonp@opera.com> wrote:

> "An element that is focusable, has an assigned access key, and is [not  
> an element that already defines a command], defines a command."
> http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#using-the-accesskey-attribute-to-define-a-command
>
> Please remove "that is focusable, ", since it seems pointless to require  
> that e.g.
>
>     <div accesskey=a onclick=foo()>test</div>
>
> should have an assigned access key that does nothing.

Although you can add an authoring conformance requirement saying that an  
element with an accesskey attribute that wouldn't otherwise define a  
command must also have a tabindex attribute (since the browser should be  
able to just focus the element).

-- 
Simon Pieters
Opera Software
Received on Monday, 22 June 2009 12:47:27 GMT

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