Community
Participate
Working Groups
3.6 and HEAD. From bug 272167 comment 13: Btw: There is a small enhancement in that page regarding accessibility. Provide some description to the field that contains the delay value and to the field that contains the trigger value. Actually orca only reads the value of that fields, no description is present. The desired behavior is present in content assist preferences of ant editor.
Interesting. On the Mac, VoiceOver does read those labels. The only difference to the Ant editor preference page is that the Java editor preference page creates labels with SWT.WRAP style. Changed this to SWT.NONE in HEAD of CodeAssistConfigurationBlock. Jose, please reopen if not fixed.
(In reply to comment #1) > Interesting. On the Mac, VoiceOver does read those labels. > > The only difference to the Ant editor preference page is that the Java editor > preference page creates labels with SWT.WRAP style. > > Changed this to SWT.NONE in HEAD of CodeAssistConfigurationBlock. > Jose, please reopen if not fixed. Looking in the output debug from orca, I found the following: When reading the field from java editor preferences orca receives the following event: OBJECT EVENT: object:state-changed:focused detail=(1,0,None) app.name='' name='None' role='text' state='editable enabled focusable focused sensitive showing single line visible' relations='' When reading the field from ant editor preferences orca receives the following event: OBJECT EVENT: object:state-changed:focused detail=(1,0,None) app.name='Eclipse' name='None' role='text' state='editable enabled focusable focused sensitive showing single line visible' relations='labelled by' The difference is that in the first case the relations is empty, while in the seconde case it has a value, 'labelled by'. If I had to guess, I'd say that the following is missing: textField.getAccessible().addRelation(ACC.RELATION_DESCRIBED_BY, liveLabel.getAccessible());
>The only difference to the Ant editor preference page is that the Java editor >preference page creates labels with SWT.WRAP style. Maybe we should report that to SWT?
hi. The fix is available in last nightly build? I'd like to test. Thanks.
>The fix is available in last nightly build? yes.
(In reply to comment #5) > >The fix is available in last nightly build? > yes. Testing with eclipse build id N20100726-2000. Orca doesn't read the label of the field, only its value. The bug seems not fixed.
Thanks for testing!
It gets even more interesting from day to day ;-). Moving to SWT, since this seems to be a GTK problem. My next guess is that this is a problem of the Group widget. On the Ant content assist preference page (where the label is correctly read), the controls are inside a Composite but on the Java page, they're inside a Group.
*** This bug has been marked as a duplicate of bug 318786 ***
