- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Fri, 21 Sep 2007 13:24:19 -0500
- To: "Charles McCathieNevile" <chaals@opera.com>
- Cc: "Maciej Stachowiak" <mjs@apple.com>, "public-html@w3.org WG" <public-html@w3.org>, public-html-request@w3.org
- Message-ID: <OFCA18A9D8.576EA310-ON8625735D.0064B908-8625735D.006519BE@us.ibm.com>
Hi Charles, Interesting. So there are few exceptions. I would like to see navigation by role like access (when this makes it in). You could place an optional key assignment here like access and eliminate accesskey altogether. Looking at the DOM Interface, why is there a click on a command? This is not something that is visible. Rich Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist Chair, IBM Accessibility Architecture Review Board blog: http://www.ibm.com/developerworks/blogs/page/schwer "Charles McCathieNevile" <chaals@opera.com To > Richard Schwerdtfeger/Austin/IBM@IBMUS 09/21/2007 11:13 cc AM "Maciej Stachowiak" <mjs@apple.com>, "public-html@w3.org WG" <public-html@w3.org>, public-html-request@w3.org Subject Re: Proposal for Keyboard Shortcuts for HTML5 On Fri, 21 Sep 2007 17:38:27 +0200, Richard Schwerdtfeger <schwer@us.ibm.com> wrote: > Hi Charles, > > I just joined the HTML working group. Regarding accesskey, Has the group > looked at using a modified version of the access element from xhtml 2 > which supports device independence? As far as I can tell, the command element in HTML5 is mostly rewriting the same thing, plus a bit of stuff clarifying how it relates to any other kind of element... cheers Chaals -- Charles McCathieNevile, Opera Software: Standards Group hablo español - je parle français - jeg lærer norsk chaals@opera.com http://snapshot.opera.com: - Kestrel (9.5α1)
Attachments
- image/gif attachment: graycol.gif
- image/gif attachment: pic11904.gif
- image/gif attachment: ecblank.gif
Received on Friday, 21 September 2007 18:24:43 UTC