W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13579] Clarify behavior of accesskey on static content elements

From: <bugzilla@jessica.w3.org>
Date: Sun, 07 Aug 2011 08:21:10 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qpybe-00058Q-4E@jessica.w3.org>

Joshue O Connor <joshue.oconnor@cfit.ie> changed:

           What    |Removed                     |Added
                 CC|                            |joshue.oconnor@cfit.ie

--- Comment #2 from Joshue O Connor <joshue.oconnor@cfit.ie> 2011-08-07 08:21:08 UTC ---
I am curious as how the suggested @accesskey mappings would work in conjunction
with the new HTML 5 elements that define web page functionality? Are we in
danger of element bloat and how will Assistive Technologies harmonise these new
elements in HTML 5 with existing user functions like skipping headings by
pressing the 'H' key, 'on top' of more author defined accesskeys?

We are yet to see support for many of the new HTML 5 elements in AT, will
resurrecting accesskeys make implementation of the spec more complex and prone
to error?

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 7 August 2011 08:21:11 UTC

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