Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support relations providing live updates #2036

Closed
nvaccessAuto opened this issue Jan 9, 2012 · 2 comments
Closed

Support relations providing live updates #2036

nvaccessAuto opened this issue Jan 9, 2012 · 2 comments

Comments

@nvaccessAuto
Copy link

Reported by mwhapples on 2012-01-09 14:19
In eclipse's SWT there is a snippet showing how one can use a relation to provide live updates to access technologies, a description of this can be found at http://www-03.ibm.com/able/news/eclipse_introduces_iaccessible2.html#using_relations

According to the page linked to here this facility is provided by IA2 on windws. However when I tried snippet 340 which is an example the above page refers to showing this function in action, NVDA does not read th updates being made.

This ticket is a request that NVDA should support such live updates as described in the page linked to above.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2012-01-10 00:57
The cited example modifies the text of the describedBy relation. This should cause the description of the field to change and a descriptionChange event to be fired. NVDA already supports descriptionChange events, so if the event is being fired, NVDA should read the new description. Of course, reporting of descriptions must be enabled in NVDA (which is the default).

You might want to use a tool like !AccProbe to verify that EVENT_OBJECT_DESRIPTIONCHANGE is being fired by the control.

@ehollig
Copy link
Collaborator

ehollig commented Aug 7, 2017

The URL provided in the original post no longer exists. Also, it sounds like from @jcsteh's comment in #2036 (comment) that NVDA already supports descriptionChange events. If this issue still exists, and someone can provide another working example, the issue can be reopened. Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants