Re: Accessibility penalty?
Re: Accessibility penalty?
- Subject: Re: Accessibility penalty?
- From: Bill Cheeseman <email@hidden>
- Date: Wed, 30 Jul 2003 17:58:50 -0400
on 03-07-30 2:26 PM, Guy Fullerton at email@hidden wrote:
>
AppleScript isn't considered quite the same type of security risk
>
because app developers get to make the choice of exactly how much (if
>
any) of their application is scriptable. (The details of how this
>
choice is made depends on the framework used to build the app, of
>
course.)
>
>
However, Accessibility happens behind the developer's back (for the
>
standard widgets/controls/views), thereby eliminating the developer's
>
ability to choose not to support Accessibility for any of their
>
existing apps. The user cannot be guaranteed that any of their existing
>
apps offer the correct level of security with respect to the
>
Accessibility APIs, so therefore Accessibility must be turned off by
>
default.
I had not thought of it this way. It's a good point. Especially the one that
came up about passwords in non-Cocoa text fields.
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com
The AppleScript Sourcebook -
http://www.AppleScriptSourcebook.com
Vermont Recipes -
http://www.stepwise.com/Articles/VermontRecipes
_______________________________________________
accessibility-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/accessibility-dev
Do not post admin requests to the list. They will be ignored.