Post

Replies

Boosts

Views

Activity

AX Elements in some apps only exposed when using VoiceOver or Accessibility Inspector
i build apps that act as Screen Readers to 1) add Vim motions everywhere on macOS 2) click (and more) AX Elements through the keyboard 3) scroll through the keyboard. it works extremely well with native apps. with non-native apps, i need to blast them with some extra AX Attributes (AXManualAccessibility, AXEnhancedUserInterface) to get them to expose their AX Elements. but there are a couple of apps tho which i can't get them to expose their AX Elements programmatically. now the weird thing is as soon as i start VoiceOver, those apps open up. or for some, if i use the Accessibility Inspector to go through their AX Elements, then they start opening up. so i'm wondering, is there one public known way that i'm missing to open up those apps, or is Apple using private APIs? any way i could make my apps behave like VoiceOver or the Accessibility Inspector to force those recalcitrant apps to open up? thanks in advance.
1
1
469
Jun ’24
modify screen tint on macOS
i'm new to macOS development. i do mainly web dev. i want to build an app that allows a Vim experience all around macOS. i thought it'd be pretty straightforward but after 2 months of books, tutorials, building a few apps, i'm finding that i barely understand anything about Apple's API and how to use the documentation. i'm now going step by step. the first thing i'm trying to achieve now is changing the screen tint when a keyboard shortcut is hit. i've checked the Accessibility docs and i can't find anything related to what i'm trying to do. after a week of searching and playing around i basically haven't been able to write one line of code. probably i'm looking at the wrong place. i don't see to find any usable information. any hint possible on where to look? thanks in advance
1
0
376
Nov ’20