FB10280662

I considered using CFRunLoopSource (there's an aside buried at the end of the readme mentioning that as a future exploration) but it didn't offer a clear enough win on unsafe usage (so far). As far as questions my experience in the 1:1 labs in the past was that it's better to come in and show the project and point at some of the sharper edges and see what feedback you get but if the forums is better suited to specificity I'd ask for feedback about the usage of pthread specific as a way to hold state for observer callbacks when working against an API (AXObserver) that has no defined safe point to perform cleanup after removing an observer. What I have is working, but it's quite warty.

You could use accessibilityRep to replace the card view with a button with two elements one for the card and one for the button with non overlapping frames so exploring by touch works well

I'll post the swift wrapper I've been using as an example https://codeberg.org/SpeakUp/AX and another library that among other things offers a way to handle the tricky ceremony of cleaning up observers https://codeberg.org/SpeakUp/AccessibilityElement