Abstract: User interface information related to relevant events of interest is provided. Events can occur anywhere in a document, and may or may not be relevant to a user utilizing an assistive technology (AT) application, such as a screen reader. A provider-side signaling system component determines whether raised events are relevant to the user. In some examples, when an application makes a plurality of attribute changes in a document at once, the signaling provider batches the related events as a single transaction, and generates a generalized annotation describing the changes. The signaling provider further packages the event notification, and sends the event notification to a client-side signaling system component. The signaling client receives the notification, and determines whether to alert the user of the event(s) based on verbosity settings. The AT application is enabled to interpret the event notification and alert the user in a meaningful way.

Abstract: User interface information related to relevant events of interest is provided. Events can occur anywhere in a document, and may or may not be relevant to a user utilizing an assistive technology (AT) application, such as a screen reader. A provider-side signaling system component determines whether raised events are relevant to the user. In some examples, when an application makes a plurality of attribute changes in a document at once, the signaling provider batches the related events as a single transaction, and generates a generalized annotation describing the changes. The signaling provider further packages the event notification, and sends the event notification to a client-side signaling system component. The signaling client receives the notification, and determines whether to alert the user of the event(s) based on verbosity settings. The AT application is enabled to interpret the event notification and alert the user in a meaningful way.