Re: Accessibility and Content and UIElement Inspector
Re: Accessibility and Content and UIElement Inspector
- Subject: Re: Accessibility and Content and UIElement Inspector
- From: Mike Engber <email@hidden>
- Date: Wed, 6 Aug 2003 08:52:50 -0700
The calls you mentioned (in fact, everything in that whole section of
documentation) are only useful if you're trying to make some of your
custom Cocoa controls work with accessibility.
They're of absolutely no use if you're writing an assistive app like
UIElement inspector.
Assistive apps should be using the calls in Accessibility.h;
AXUIElement.h, AXValue.h, AXConstants.h.
NSAccessibility.h is primarily intended to be used by people trying to
fix their Cocoa apps to work with accessibility (a small audience).
There's a similar header for Carbon developers trying to do the same.
-ME
So If I were to place these calls and functions
somewhere in one of the files of the UIElement
Inspector, and "re-built" and opened the application,
and put my cursor over a Cocoa window (let's say a
Safari webpage), would the contents of the webpage
come spewing out along with all the info about the UI
Elements?
Thanks in advance. I'm very new at this.
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
_______________________________________________
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.
_______________________________________________
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.