Community
Participate
Working Groups
- Open the Configuration Manager, Help->Software Updates->Manage Configuration Available tasks in the right pane may be tabbed through but Window-Eyes will only read the first item. The use of the CTRL+SHIFT+W method will read these tasks. But these are the main activities for the dialog and should be readable with tabbing.
This is FormText issue - moving.
Veronika, how can I kick JAWS to re-read the widget? The tabbing inside the Eclipse Forms text moves focus indication to the next link but the 'real' focus stays on the same physical widget. I would need to somehow cause JAWS to check the widget again.
Sorry for the slow response. Carolyn MacLeod is the prime for accessibility. You probably want to call Accessible.setFocus(int) when you move the focus internally. Note that there is also Accessible.selectionChanged() - this is if you are changing selection. You can get the Accessible object using Control.getAccessible().
Fixed in Forms. However, my use of 'ROLE_LINK' for the hyperlinks is not well liked by Window- Eyes - 'custom control' is heard instead. Moving to SWT for ROLE_LINK issue resolution.
Are you using the new SWT "Link" widget? Or is it a custom hyperlink of your own?
The Manage Configurations dialog does not use the SWT Link widget - it uses the UI Forms hyperlink widget FormText. I think Dejan told me that he can make it work with ROLE_LISTITEM but not with ROLE_LINK.
True. I am reporting children for each hyperlink in the text and fire proper notifications. for 'SELF' i fire ROLE_TEXT and for each hyperlink child, I report ROLE_LINK. inspect32.exe shows correct roles as a tab through the widget.
Sending to Platform UA inbox, either because owner is incorrect or no longer works on UA.
I will be taking a pass at forms accessibility shortly and will investigate if there is still a problem reading ROLE_LINK. Otherwise, this bug appears to be resolved.
I just tried this out and do not see any problem with ROLE_LINK. Window Eyes is reading the links as "link". While testing this I found a different problem with FormText link accessibility. I have opened bug 237702 to track that issue. Closing as FIXED.
