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
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.
The text was updated successfully, but these errors were encountered:
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.
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
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.
The text was updated successfully, but these errors were encountered: