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 23616 - clarify how assigning an accesskey to an element affects the elements default role
Summary: clarify how assigning an accesskey to an element affects the elements default...
Status: RESOLVED MOVED
Alias: None
Product: HTML.next
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
Hardware: PC All
: P1 major
Target Milestone: ---
Assignee: Charles McCathieNevile
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf, aria
: 10905 23611 (view as bug list)
Depends on: 10888 10905 23613
Blocks: 10066 23611
  Show dependency treegraph
 
Reported: 2013-10-23 20:08 UTC by Mark Sadecki
Modified: 2016-04-28 15:59 UTC (History)
13 users (show)

See Also:


Attachments

Description Mark Sadecki 2013-10-23 20:08:15 UTC
+++ This bug was initially created as a clone of Bug #10905 +++

in the editor states "for example any element with accesskey="" can end up having a role."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10603

yet it is not specified in the spec (that I can find) how the adding of an accesskey to "any element" affects  its role 

for example how is the role of the following affected by the presence of an accesskey?

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

or

<p accesskey="a">pooter</a>

or 

<td accesskey="a">pootsville</a>
Comment 1 Charles McCathieNevile 2014-12-18 15:41:31 UTC
Not clear what the reference is. But any element can have a role, no?

Adding an accesskey should make an element focusable. I think that is all that is really needed, no?
Comment 2 Charles McCathieNevile 2014-12-18 15:42:52 UTC
*** Bug 23611 has been marked as a duplicate of this bug. ***
Comment 3 Philippe Le Hegaret 2014-12-18 16:27:02 UTC
the spec currently says (non-normatively):
"Each element that can be activated or focused can be assigned a single key combination to activate it, using the accesskey attribute."
http://www.w3.org/TR/html5/editing.html#assigning-keyboard-shortcuts


what kind of conformance requirements do we expect with the following examples?

Example 1:
[[
<!doctype html>
<p accesskey='c'>Hello World!</p>
]]


Example 2:
[[
<!doctype html>
<p accesskey='c' onclick="doSomething();">Hello World!</p>
]]
Comment 4 Charles McCathieNevile 2016-02-23 15:52:24 UTC
*** Bug 10905 has been marked as a duplicate of this bug. ***
Comment 5 Charles McCathieNevile 2016-04-28 15:59:55 UTC
moved to https://github.com/w3c/html/issues/296