Greg said:
VoiceOver that scripting language, AppleScript , is a system service
found with in the OS. It along with its companion Automator can be used
to access applications which are not by themselves accessible. It is even
possible in a few cases to add accessibility to application which do not
now support it without access to the programs source code.
Has anyone tried to do this with VoiceOver under Lepoard?
If so, what was your experience?
Thanx.
-- Rich
----- Original Message -----
From: "Greg Kearney" <[EMAIL PROTECTED]>
To: "General discussions on all topics relating to the use of Mac OS X by
theblind" <[email protected]>
Sent: Thursday, November 08, 2007 8:36 PM
Subject: Re: Responce from Apple Accessibility
Accessibility in the Macintosh environment is much more dependent on the
applications themselves than on the screen reader. Applications which
follow modern development practices will be accessible with but small
effort on the part of the developer.
Improvements in accessibility on the Mac are more often than not small
changes done not so much to VoiceOver itself but to the applications. An
example of this is when iTunes went from all but unusable to nearly fully
accessible between versions 7.1 and 7.2. This was a change made in iTunes
itself and not in VoiceOver.
It is worthwhile to not that VoiceOVer has a scripting language the same
as Jaws or WindowEyes. But in keeping with the central idea of VoiceOver
that scripting language, AppleScript , is a system service found with in
the OS. It along with its companion Automator can be used to access
applications which are not by themselves accessible. It is even possible
in a few cases to add accessibility to application which do not now
support it without access to the programs source code.
Greg Kearney
535 S. Jackson St.
Casper, Wyoming 82601
307-224-4022
[EMAIL PROTECTED]
On Nov 8, 2007, at 6:12 PM, Orin wrote:
From what I've heard, the applications that you use get updated with
accessibility features and not the way around where special scripts
need to be created for a windows screen reader. If the application was
changed, say, if it was inaccessible to an accessible one, it'd have to
have standard controls and such. In other words I really don't think VO
supports custom interfaces yet. They can't make designs and what not to
the buttons or change colors for the buttons to be read properly. I
know I'm understanding this somewhat right here...
If anyone can add more detail, please do so.
Do you like mudding? Want to join a group of like-minded people for
discussion via EMail? Go to:
http://tbmic.jiglu.com
