23616 2013-10-23 20:08:15 +0000 clarify how assigning an accesskey to an element affects the elements default role 2016-04-28 15:59:55 +0000 1 1 1 Unclassified HTML.next default unspecified PC All RESOLVED MOVED a11y, a11ytf, aria P1 major --- 10888 10905 23613 10066 23611 1 mark.sadecki+w3c chaals dghrjyan faulkner.steve ian john laura.lee.carlson mike plh public-html-a11y public-html-admin public-html-wg-issue-tracking robin schwer w3c public-html-bugzilla oldest_to_newest 95236 0 mark.sadecki+w3c 2013-10-23 20:08:15 +0000 +++ 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> 116497 1 chaals 2014-12-18 15:41:31 +0000 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? 116499 2 chaals 2014-12-18 15:42:52 +0000 *** Bug 23611 has been marked as a duplicate of this bug. *** 116506 3 plh 2014-12-18 16:27:02 +0000 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> ]] 125232 4 chaals 2016-02-23 15:52:24 +0000 *** Bug 10905 has been marked as a duplicate of this bug. *** 126269 5 chaals 2016-04-28 15:59:55 +0000 moved to https://github.com/w3c/html/issues/296