Bug 51963 - Group Boxes no longer show up as radio button parents in screen readers
Summary: Group Boxes no longer show up as radio button parents in screen readers
Status: RESOLVED DUPLICATE of bug 69350
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Carolyn MacLeod CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2004-02-13 10:40 EST by Tod Creasey CLA
Modified: 2005-04-13 17:04 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tod Creasey CLA 2004-02-13 10:40:35 EST
M7

When you read a radio button in a group box its parent is not read. Checking 
with inspect objects it is no longer showing up in the parent field
Comment 1 Carolyn MacLeod CLA 2004-05-20 14:14:13 EDT
Works fine in the following snippet (the group is not the immediate parent, 
but it never was. It shows up in the ancestors list).
Can you modify the snippet to show what is not working?
Thanks!

import org.eclipse.swt.*;
import org.eclipse.swt.widgets.*;
import org.eclipse.swt.layout.*;

public class GroupWithRadiosTest {
	static Display display;
	static Shell shell;
	static Group group;
	
	public static void main(String[] args) {
		display = new Display();
		shell = new Shell(display);
		shell.setLayout(new GridLayout());
		shell.setText("Group with Radios Test");
		
		group = new Group(shell, SWT.NONE);
		group.setText("Group with Radios");
		group.setLayout(new GridLayout());
		group.setLayoutData(new GridData(GridData.FILL_BOTH));
		
		Button radio1 = new Button(group, SWT.RADIO);
		radio1.setText("Radio 1");
		
		Button radio2 = new Button(group, SWT.RADIO);
		radio2.setText("Radio 2");

		shell.pack();
		shell.open();
		while (!shell.isDisposed()) {
			if (!display.readAndDispatch()) display.sleep();
		}
	}
}
Comment 2 Carolyn MacLeod CLA 2004-08-27 03:00:50 EDT
Not sure if this is now a dup of bug 69350. Need to investigate further.
Comment 3 Steven Wasleski CLA 2005-04-12 11:12:07 EDT
We are in the process of updating the accessibility information for 3.1.  Is 
this bug going to be fixed in 3.1, is it not really a problem as mentioned in 
comment 1 or has it been fixed in JAWS as implied by the defect referenced in 
comment 2 (which probably should be marked resolved)?
Comment 4 Carolyn MacLeod CLA 2005-04-13 17:04:24 EDT
This has been fixed in JAWS 6.0.

*** This bug has been marked as a duplicate of 69350 ***