Re: Ignored windows are not 100% ignored?
Re: Ignored windows are not 100% ignored?
- Subject: Re: Ignored windows are not 100% ignored?
- From: Mike Engber <email@hidden>
- Date: Wed, 7 Jun 2006 09:51:19 -0700
On Jun 7, 2006, at 9:10 AM, Håkan Waara wrote:
If I subclass NSWindow, and return YES from accessibilityIsIgnored,
then the close button, maximize button, title (etc) are still in
the accessibility hierarchy.
Is this a bug?
No. Ignored elements let the accessibility hierarchy pass through
them - they don't block it.
When a ui element is ignored it means that element (alone) should not
show up in the hierarchy. Its children are still accessible - the
parent they report will be the next ui element up the chain that is
_not_ ignored (e.g. their grandparent).
Ignored ui elements are intended to be used for eliminating
intermediate views (e.g. clip views) that aren't a visible part of
the ui. Sometimes people get away with using accessibilityIsIgnored
to hide part of the hierarchy, but as you've discovered, this doesn't
work when there are children involved.
Hiding part of the hierarchy requires ensuring nothing returns
anything in that hierarchy - e.g. as children, from hit testing,
focus testing, any other attributes whose value is a ui element, ...
If you want to hide a window from accessibility, you're going to need
to subclass NSApp so the it doesn't report that window - in its
windows attribute, hit testing, focused ui element, ...
Is the window you're trying to hide visible to the user? If it is, it
doesn't seem proper for you to hide it from accessibility.
-ME
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden