Re: Accessibility-dev Digest, Vol 20, Issue 35
Re: Accessibility-dev Digest, Vol 20, Issue 35
- Subject: Re: Accessibility-dev Digest, Vol 20, Issue 35
- From: Rich Siegel via Accessibility-dev <email@hidden>
- Date: Sat, 16 Dec 2023 16:18:15 -0500
On 16 Dec 2023, at 15:08, Rain (Sk) via Accessibility-dev wrote:
> Hi Rich,
>
> If you're debugging a Mac application, you can use the Accessibility
> Inspector debug tool that comes with Xcode to inspect your application's
> accessibility. I'd recommend observing the structure of a native macOS
> application using this tool. You can also attach it to a running application,
> open the "notifications" window, and observe the events the application sends
> as you type in a text box.
Thanks for the tip on the Notifications window; we've successfully used the
Accessibility Inspector to verify the correctness of our accessibility API
support in other areas, but perhaps this will help as well. (One thing I don't
think the inspector helps with is keeping track of what the OS asks the
*application* for.)
> From what you describe, it sounds like your application doesn't support the
> accessibility API in macOS.
That's not correct, although I get that I didn't give you enough information to
avoid making that assumption. :-)
> The accesskit open source project can be a great resource in understanding
> what accessibility API expect.
Thanks for the pointer, I will check that out as well.
> Unfortunately there's very little in the way of guidance from Apple on this
> subject.
Quite so, and I'd love to see that changed. Someday, perhaps.
R.
--
Rich Siegel Bare Bones Software, Inc.
<email@hidden> <https://www.barebones.com/>
Someday I'll look back on all this and laugh... until they sedate 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