Raising NSAccessibilityValueChangedNotification during real-time coauth?
Raising NSAccessibilityValueChangedNotification during real-time coauth?
- Subject: Raising NSAccessibilityValueChangedNotification during real-time coauth?
- From: Charlie Powell <email@hidden>
- Date: Thu, 08 Feb 2018 19:58:30 +0000
- Msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=email@hidden; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-02-08T19:58:28.8334564Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
- Thread-topic: Raising NSAccessibilityValueChangedNotification during real-time coauth?
Our macOS app has the ability for multiple users (the local user and 1 or more
remote users) to edit content in the app simultaneously and in real time
(similar to the functionality in Google Docs). Whenever the content of one of
our accessibility elements changes as a result of the local user, we fire an
NSAccessibilityValueChangedNotification along with
NSAccessibilitySelectedTextChangedNotification. We're using
NSAccessibilityElements as opposed to NSViews/NSResponder elements, and this is
how we get the basic scenarios of typing feedback from VO to work as expected.
When content changes as a result of remote users, we fire an
NSAccessibilityValueChangedNotification (because the value of the element has
indeed changed). We've noticed that at least sometimes, this causes VO to
announce information to the local user, which is confusing since it makes it
sound like it's a result of the local user typing even though she hasn't. If we
suppress the value changed notification that solves the announcement issue, but
then VO has problems navigating content where the remote user made changes
because it's (seemingly) unaware of the fact that the content is different
(since there was no notification posted).
We're exploring ways to mitigate these issues, but ultimately it seems like we
may not be able to completely solve the problem - we seemingly need to fire the
NSAccessibilityValueChangedNotification in order for VO to be aware that the
content changed as a result of some remote user, but if VO also uses that
notification to read content to the user, how can we reliably limit VO's
announcement to edits of just the local user?
_______________________________________________
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