- From: James Craig <jcraig@apple.com>
- Date: Tue, 16 Jun 2009 14:40:54 -0700
- To: Charles McCathieNevile <chaals@opera.com>
- Cc: Jeff Ganyard <jeff.ganyard@macspeech.com>, wai-xtech@w3.org
On Jun 16, 2009, at 2:11 PM, Charles McCathieNevile wrote: > On Tue, 16 Jun 2009 20:09:44 +0200, Jeff Ganyard <jeff.ganyard@macspeech.com > > wrote: > >> On Tue, Jun 16, 2009 at 10:30 AM, James Craig <jcraig@apple.com> >> wrote: >> >>> Hi Jeff, this sounds like a reasonable idea. Perhaps this is one >>> potential solution to the #9 request on the following page. >>> >>> http://esw.w3.org/topic/PF/XTech/HTML5/AccesskeyRequirements >> >> If all 9 of those items were adopted and actually implemented, I >> would be >> more than content! But addressing #3, #4 & #9 are the most critical >> from the our perspective as a developer of an external process to a >> browser trying to improve the user's experience within the browser. > > Actually, the current HTML 5 draft probably deals reasonably well > with requirement 9. For the sake of thread completeness, Chaals is referring to these portions of the editor's draft. Accesskey http://www.whatwg.org/specs/web-apps/current-work/#using-the-accesskey-attribute-to-define-a-command http://www.whatwg.org/specs/web-apps/current-work/#assigned-access-key http://www.whatwg.org/specs/web-apps/current-work/#the-accesskey-attribute http://www.whatwg.org/specs/web-apps/current-work/#dom-accesskey http://www.whatwg.org/specs/web-apps/current-work/#dom-accesskeylabel Commands API http://www.whatwg.org/specs/web-apps/current-work/#commands http://www.whatwg.org/specs/web-apps/current-work/#command-api document . commands Returns an HTMLCollection of the elements in the Document that define commands and have IDs. And for each element in the collection element . commandType element . id element . label element . title element . icon element . accessKeyLabel element . hidden element . disabled element . checked element . click()
Received on Tuesday, 16 June 2009 21:41:33 UTC