Mixing NSViews and NSAccessibilityElements in accessibility hierarchy
Mixing NSViews and NSAccessibilityElements in accessibility hierarchy
- Subject: Mixing NSViews and NSAccessibilityElements in accessibility hierarchy
- From: Charlie Powell <email@hidden>
- Date: Tue, 23 Aug 2016 19:14:43 +0000
- Thread-topic: Mixing NSViews and NSAccessibilityElements in accessibility hierarchy
Our apps are using NSAccessibilityElements to implement accessibility for our custom controls. We have some scenarios where it would be beneficial to put native controls (e.g. NSButton or other things that do inherit from NSView) in the
hierarchy. However, our initial attempts at this have been unsuccessful. Additionally, the API for accessibilityAddChildElement: only accepts other NSAccessibilityElements, as opposed to any NSObject or id, implying this is not possible.
We know that it is possible to have NSAccessibilityElements as accessibility children of NSView-based elements, but it doesn’t seem practical to have the reverse (NSView-based elements as accessibility children of NSAccessibilityElements).
Aside from the aforementioned API, there’s also the problem of what the superview for this NSView-based accessibility elements would be… presumably it would have to be a subview of some other view that’s potentially many levels higher up in the accessibility
hierarchy, but is it okay for that to be the case and have the accessiblityChild/Parent relationship be different as long as it’s consistent? Has anyone else tried tackling this problem?
Thanks,
Charlie
|
_______________________________________________
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