| Hi folks, Still attempting to explore this custom application for the MJ phone service. Here’s what I’ve found so far: - Its main window (according to the script below) contains thirty elements; - Each of these thirty elements contains zero sub-elements; - Each role attribute is “AXUnknown”; - Each class is just UI element; - All the names return missing value errors [i.e] none of the elements appear to be named. Accessibility Inspector appears not to work with VoiceOver; possibly because it’s a floating window. Is there a way to get AI to log what it sees to a file, which I could review with an editor? Here’s one of my testing scripts: tell application "System Events" to tell process "magicJack" activate tell front window set UICount to number of UI elements of UI element 1 display dialog "Main window contains " & UICount & "elements." repeat with i from 1 to UICount display dialog "UI element name is " & name of UI element i of UI element 1 end repeat end tell end tell
Any suggestions how I might explore further? I’m sure this app is just one of thousands out there that don’t readily expose anything about their UIs that the Mac’s screen reader can use. I’d like to work on such apps, and perhaps eventually get VoiceOver speaking at least some of these presently inaccessible UI elements, similarly to how the Windows readers can now work with more of the custom controls in Windows apps. Can I add MJ to the sys prefs accessibility table some way, even though it’s in a hidden folder that starts with a period? Thanks for any light you can shed :-)
|