W3C home > Mailing lists > Public > public-html-a11y@w3.org > October 2010

[Bug 10905] clarify how assigning an accesskey to an element affects the elements default role

From: <bugzilla@jessica.w3.org>
Date: Thu, 14 Oct 2010 08:47:18 +0000
To: public-html-a11y@w3.org
Message-Id: <E1P6JT4-00011s-K9@jessica.w3.org>

--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-14 08:47:18 UTC ---
Setting the "accesskey" attribute results in the element having an "assigned
access key".
 - http://c.whatwg.org/m#the-accesskey-attribute
 - http://c.whatwg.org/m##assigned-access-key

An element that has an assigned access key defines a command.

An element that defines a command, whose Type facet is "command", and that is a
descendant of a menu element whose type attribute in the list state has strong
native semantics and implied ARIA semantics giving it a menuitem role.
 - http://c.whatwg.org/m#annotations-for-assistive-technology-products-(aria)

So, if you have a page like this:

      <h1 accesskey="a">Demo</h1>

...then the <h1> element will have the role "menuitem".

This seems pretty clear in the spec, and is a rather obscure edge case (and one
that, at least for <h1>, is pretty useless and not especially interesting to
authors), so I don't really see why an example would help here.

Could you clarify whether you really want an example for this? It's not clear
to me how authors would benefit from one.

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 Thursday, 14 October 2010 08:47:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:15 UTC