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: "Rain \(Sk\) via Accessibility-dev" <email@hidden>
- Date: Sat, 16 Dec 2023 20:08:46 +0000
- Feedback-id: 85946040:user:proton
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.
From what you describe, it sounds like your application doesn't support the
accessibility API in macOS. The accesskit open source project can be a great
resource in understanding what accessibility API expect. Unfortunately there's
very little in the way of guidance from Apple on this subject.
Hope that points in a good direction,
-------- Original Message --------
On Dec 16, 2023, 21:00, wrote:
> Send Accessibility-dev mailing list submissions to
> email@hidden To subscribe or unsubscribe via the World
> Wide Web, visit https://lists.apple.com/mailman/listinfo/accessibility-dev
> or, via email, send a message with subject or body 'help' to
> email@hidden You can reach the person managing
> the list at email@hidden When replying, please
> edit your Subject line so it is more specific than "Re: Contents of
> Accessibility-dev digest..." Today's Topics: 1. Debugging unfulfilled
> requirements? (Rich Siegel)
> ----------------------------------------------------------------------
> Message: 1 Date: Sat, 16 Dec 2023 10:07:05 -0500 From: Rich Siegel To:
> email@hidden Subject: Debugging unfulfilled
> requirements? Message-ID: Content-Type: text/plain I'm trying to debug
> situations in which accessibility features (such as "speak typing feedback")
> or third-party clients (such as Grammarly) don't work correctly in my
> application. Unfortunately, in both cases I have no information on what
> requirements aren't being met, so I don't know where to start. It looks like
> there's a domain "com.apple.universalaccess.debug" which might have something
> to do with debugging. But I can't find any documentation on keys, values, or
> behavior. What's the best way to approach this? Thanks for any advice, R. --
> Rich Siegel Bare Bones Software, Inc. Someday I'll look back on all this
> and laugh... until they sedate me. ------------------------------ Subject:
> Digest Footer _______________________________________________
> Accessibility-dev mailing list email@hidden
> https://lists.apple.com/mailman/listinfo/accessibility-dev
> ------------------------------ End of Accessibility-dev Digest, Vol 20, Issue
> 35 *************************************************
_______________________________________________
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