W3C home > Mailing lists > Public > public-html@w3.org > September 2010

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

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 21:38:24 +0000
To: public-html@w3.org
Message-ID: <bug-10905-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10905

           Summary: clarify how assigning an accesskey to an element
                    affects the elements default role
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: faulkner.steve@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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>

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 30 September 2010 21:38:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:19 UTC