Reported by spmealin on 2013-04-01 03:01
When the setAccessibleDescription(String) method in the AccessibleContext class is called in Java, NVDA does not read the new accessible description value until focus is moved and then reacquired.
For example, if focus is set on a JPanel object, and then the accessible description is updated (because of a received keystroke), it is necessary to alt-tab away from the application and back again before NVDA reads the new accessible description aloud.
I’m not sure if this is a bug or feature request, but would it be possible to get NVDA to monitor propertyChange events, and read them as soon as they are received? This would reflect functionality found in other screen readers, such as Jaws.
Thank you
Reported by spmealin on 2013-04-01 03:01
When the setAccessibleDescription(String) method in the AccessibleContext class is called in Java, NVDA does not read the new accessible description value until focus is moved and then reacquired.
For example, if focus is set on a JPanel object, and then the accessible description is updated (because of a received keystroke), it is necessary to alt-tab away from the application and back again before NVDA reads the new accessible description aloud.
I’m not sure if this is a bug or feature request, but would it be possible to get NVDA to monitor propertyChange events, and read them as soon as they are received? This would reflect functionality found in other screen readers, such as Jaws.
Thank you