mobility challenged users of non-keyboard navigational aids.

Hey,

As a general rule people do not have access to non-keyboard assistive
technologies for their testing, unless the developer or tester themselves
uses such, so in developing we tend to focus on how the keyboard will be
used. I suppose that non-keyboard solutions being the less common that they
have built in functionality to disguise themselves as a mouse or keyboard
as need be? Are there any common situations one should think about where
you think you have developed a nice solution for the keyboard but you might
not be serving the needs of these users at a reasonable level?

Thanks,
Bryan Rasmussen