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

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

From: <bugzilla@jessica.w3.org>
Date: Sun, 20 Nov 2011 15:21:32 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RS9D2-0005zG-UY@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13579

Michael[tm] Smith <mike@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needsinfo

--- Comment #3 from Michael[tm] Smith <mike@w3.org> 2011-11-20 15:21:32 UTC ---
Greg, this bug is waiting on your response to comment #2:
> 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, 20 November 2011 15:21:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 20 November 2011 15:21:37 GMT