Certainly the accessability working group could, and probably should, address this. But I think "keyboard navigation" is out of scope for the DOM. Remember, the DOM is a Document Model API. Screen navigation is an user interface issue. The DOM will happily pass those characters through its event system. But how they're interpreted by the UI is not under the DOM's control, so there isn't anything the DOM spec can usefully say about this. ______________________________________ Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more. "The world changed profoundly and unpredictably the day Tim Berners Lee got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filkReceived on Monday, 6 December 2004 14:31:31 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:24:57 GMT