W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 23616] New: clarify how assigning an accesskey to an element affects the elements default role

From: <bugzilla@jessica.w3.org>
Date: Wed, 23 Oct 2013 20:08:15 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-23616-2486@http.www.w3.org/Bugs/Public/>

            Bug ID: 23616
           Summary: clarify how assigning an accesskey to an element
                    affects the elements default role
           Product: HTML.next
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Keywords: a11y, a11ytf, aria
          Severity: major
          Priority: P1
         Component: default
          Assignee: chaals@yandex-team.ru
          Reporter: mark@w3.org
        QA Contact: public-html-bugzilla@w3.org
                CC: faulkner.steve@gmail.com, ian@hixie.ch,
                    laura.lee.carlson@gmail.com, mike@w3.org,
                    public-html-a11y@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org, robin@w3.org,
                    schwer@us.ibm.com, w3c@kliehm.com
        Depends on: 23613, 10888, 10905
            Blocks: 23611, 10066

+++ 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."

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

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


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


<td accesskey="a">pootsville</a>

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 23 October 2013 20:08:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:45 UTC