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 23611 - 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: CLOSED DUPLICATE of bug 23616
Alias: None
Product: HTML.next
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
Hardware: PC All
: P1 normal
Target Milestone: ---
Assignee: Charles McCathieNevile
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf, aria
Depends on: 10888 10905 23613 23616
Blocks: 10066
  Show dependency treegraph
 
Reported: 2013-10-23 19:42 UTC by Mark Sadecki
Modified: 2016-02-23 15:50 UTC (History)
10 users (show)

See Also:


Attachments

Description Mark Sadecki 2013-10-23 19:42:09 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:42:52 UTC

*** This bug has been marked as a duplicate of bug 23616 ***