This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
+++ 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>
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?
*** Bug 23611 has been marked as a duplicate of this bug. ***
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> ]]
*** Bug 10905 has been marked as a duplicate of this bug. ***
moved to https://github.com/w3c/html/issues/296