Accessibility and Content and UIElement Inspector
Accessibility and Content and UIElement Inspector
- Subject: Accessibility and Content and UIElement Inspector
- From: hanshoff <email@hidden>
- Date: Wed, 6 Aug 2003 08:32:02 -0700 (PDT)
Sorry if this has been covered before (I'm a newbie)
...
According to the "Accessibility-Hierarchy" and
"Creating an Ignored Object" page, at least this is my
understanding, "Content" can be gotten at by using
these:
NSArray *NSAccessibilityUnignoredChildren(NSArray
*originalChildren);NSArray
*NSAccessibilityUnignoredChildrenForOnlyChild(id
originalChild);
and
- (id)accessibilityAttributeValue:(NSString
*)attribute{ if ( [attribute
isEqualToString:NSAccessibilityChildrenAttribute] )
return NSAccessibilityUnignoredChildren( _children
); else if ( [attribute
isEqualToString:NSAccessibilityParentAttribute] )
return NSAccessibilityUnignoredAncestor( _parent );
else return [super
accessibilityAttributeValue:attribute];}
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.