On Sun, 25 Jul 2004, Erik Heil wrote: > developed under the new API, some of the accessibility traits are > automatically inherrited though. And that's exactly what Apple has done with their implementation. If you use the OSX development tools, and make it work *only* on the latest OSX release, then you do get some of the screen reader behavior w/o having to specifically code for them. However, it's also possible to roll your own interface, not using the Apple libs, in which case there would be no speech at all. This is what Apple needs to make clear in their advertising about the csreen reader functionality. They've already said, there's room for a 3rd-party screen reader that can pick up (or add to) the existing interface, since there implementation does not make everything speak, and indeed doesn't tryt o do so. If speakup or Yasr could be ported to the mac OSX platform, it would provide acc3ess to a whole range of apps currently not supported by the API apple is including with the os.
