On Nov 24, 6:24 am, William <[EMAIL PROTECTED]> wrote: > On Nov 24, 3:46 am, patrick_h_lauke <[EMAIL PROTECTED]> wrote:> shame really > that google's engineers can't > > understand the problem of keyboard access properly... > > maybe it's because maps are a form of visual communication, and > keyboard accessibility is thought to mainly cater for blind users?
That thought isn't right, though. Keyboard accessibility is used for those with limited manual dexterity who can't handle a mouse but who can hit keys. This is why the limited accessibility offered by Pamela's post (and referenced by Patrick) is ok, but it doesn't go far enough. It should be possible to use keyboard shortcuts for all controls, which would probably mean the modularisation of GKeyboardHandler -- that may not be a bad thing -- and the addition of functionality for addControl to specify a hotkey for the keyboard handler to use. I think it's currently necessary to write one's own keypress event handler to act on map keys if the map has focus, which could lead to many reinventions of the same wheel. Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
