You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Accessibility APIs require applications to raise events when the UI state changes, or in some cases, when UI elements are added or removed. AccessKit should imply as many of these events as possible from tree updates, to make it as easy as possible to implement accessibility correctly and completely. But some events will need to be raised directly by toolkits.
The text was updated successfully, but these errors were encountered:
Our implementation of implicit events needs to be smart enough to only raise events for things that have actually changed. For example, an immediate-mode GUI should be able to send a whole tree per frame without spamming ATs with events for things that haven't changed.
I believe we now have a robust implementation of automatic events based on changes to the tree. I'll leave this issue open until we've figured out which events need to be explicitly provided rather than being implied from tree changes.
Accessibility APIs require applications to raise events when the UI state changes, or in some cases, when UI elements are added or removed. AccessKit should imply as many of these events as possible from tree updates, to make it as easy as possible to implement accessibility correctly and completely. But some events will need to be raised directly by toolkits.
The text was updated successfully, but these errors were encountered: