On Sep 12, 2006, at 8:04 PM, Alastair Campbell wrote:
Something I would like is for the 'full keyboard access' mode to
include most of the VO commands, just without speech. However, I
may be a market of 1 ;)
One of the motivations for the broader developer community to use the
OS X framework accessibility API is that it makes building keyboard
access into an application much easier (relative to coding that
access from scratch)...quite straightforward, in fact.
I think there are lots of people that value comprehensive keyboard/
access control i.e. fortunately, I don't think you're a market of 1.
Apple agrees with you too. Excerpted from the accessibility docs:
--begin excerpt
Modifying your application to use the appropriate Carbon or Cocoa
frameworks [has important benefits including:
1. accomplishes much of the work needed to make your application
access-enabled.
2. It decreases the amount of work necessary to give your application
full keyboard access.
--
By making your application accessible, you make it a better app for
every user, not just those who need accessibility assistance. For
example, keyboard shortcuts and good design that reduces the number
of steps to complete a process are just as important and just as well-
loved by power users (that is, your app's most die-hard fans) as it
is by those who require accessibility.
--end excerpt
There really is no reason that every Mac app built with the "native"
Mac frameworks shouldn't have complete keyboard access. With the
accessibility API, you get it more less, for free.
Joe
