Debugging unfulfilled requirements?
Debugging unfulfilled requirements?
- Subject: Debugging unfulfilled requirements?
- From: Rich Siegel via Accessibility-dev <email@hidden>
- Date: Sat, 16 Dec 2023 10:07:05 -0500
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.
<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