- From: Jonathan Chetwynd <j.chetwynd@btinternet.com>
- Date: Wed, 16 Nov 2005 17:50:16 +0000
- To: w3c-wai-ua@w3.org
Is it too restrictive to insist on there being only one element in focus at any time(1)? thanks again Jonathan Chetwynd Accessible Solutions http://www.eas-i.co.uk --- (1) keyboard tab and mouse offer alternative methods to navigate a web page or application. Assuming that it is device independent and accessible. However it hasn't been satisfactorily described what should happen when both are in use: what will the window.status show as the destination URL? (2) If there is to be a single focus, should the tab 'jump' to the current mouse event locus? and vice versa Would changing mouse location be more contentious? When one swaps between flying and cycling, one doesn't expect to drop back where one last used that mode of transport. (2) https://bugzilla.mozilla.org/show_bug.cgi?id=316191 (3) This relates to a bug I may propose to the CDFWG http://www.w3.org/ 2004/CDF/ : (draft) window.status & duel focus one example of a really fundamental philosophical flaw: Should there be only one element allowed to be in focus? For instance if one tabs through a document and at the same time mouseover a document It will be normal that a click will deliver me to one URL, whereas an enter will deliver me to another. Device independence suggests that maybe this isn't such a good idea. consider, what will the window.status show as the destination URL? It can only be 'right' 50% of the time. Unless one implements a 'last use' policy with a single focus. (3)This particular bug has the result that once the tab has been used, the mouse is effectively disabled, and the window must be closed. --- Jonathan Chetwynd Accessible Solutions http://www.eas-i.co.uk
Received on Wednesday, 16 November 2005 17:50:30 UTC