Re: Proposed Accessibility implementation change in Carbon
Re: Proposed Accessibility implementation change in Carbon
- Subject: Re: Proposed Accessibility implementation change in Carbon
- From: Bill Cheeseman <email@hidden>
- Date: Sat, 25 Oct 2003 06:32:44 -0400
on 03-10-24 9:19 PM, Guy Fullerton at email@hidden wrote:
>
4) If you are writing an assistive application, you might want to be
>
tolerant of the fact that a given UIElementRef may still support the
>
AXChildrenAttribute or AXParentAttribute even though neither of the
>
attributes are reported via AXUIElementCopyAttributeNames. This would allow
>
your assistive application to properly handle any apps who ran into #1 or
>
#2, but who haven't had a chance to fix it yet.
In general, assistive apps should always have a fallback capability to
handle any element, action or attribute that isn't defined in the
accessibility API, because any application can create its own elements,
actions and attributes and give them its own names. An example is the
Panther Finder, which defines its own AXFinderItem element, with its own
AXOpenAction action and AXFinderIsContainer attribute (if I remember their
names correctly).
And if your assistive app already has such a fallback capability, you should
be able to handle the proposed AXChildrenAttribute and AXParentAttribute
changes without revising any code.
Right?
--
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.