-
Bug
-
Resolution: Cannot Reproduce
-
P3
-
None
-
6u10
-
x86
-
windows_xp
FULL PRODUCT VERSION :
java version "1.6.0_04"
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
1.6.0_10-b33
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
EXTRA RELEVANT SYSTEM CONFIGURATION :
Must have JAWS installed and the JDK setup with accessbridge. You can download trial 40-minute version of JAWS here: http://www.freedomscientific.com/products/fs/jaws-product-page.asp
I just ran against 1.5.0_08 and the problem still occurs. Unfortunately I don't have any earlier release. So I guess I can't be sure it is a regression except that I know we didn't hit this issue during our last round of VPAT/508 testing.
It may be some strange incompatibility with JAWS 9.0 as well.
A DESCRIPTION OF THE PROBLEM :
If you have a Swing application that contains a JSpinner, JAWS will stop reading the accessible text of *all* components shortly after giving focus to the JSpinner. JAWS will continue to read things like keystrokes, but will not read accessible text.
This seems like a fairly serious accessibility problem for Swing UIs.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
With JAWS installed and enabled, run the attached program SpinnerTest2. Confirm that JAWS is working by tabbing between the two buttons only -- it should read "first group group box a button button" and "first group group box another button button" repeatedly.
Then tab over to the spinner. JAWS will read the spinner. Then tab off of it back onto the button, and tab a few more times. JAWS will stop reading all accessible text -- the buttons and the spinner. JAWS will occasionally read the wrong text for the focused component (e.g., it will read the text of the first button when you are on the second).
At this point it is broken and can only be fixed by restarting JAWS (even restarting the Java application does not fix it).
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Expected JAWS to continue reading accessibility text.
ACTUAL -
JAWS stops reading accessibility text for JComponents once the spinner has been given focus.
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import javax.swing.event.*;
import javax.swing.text.*;
import java.text.*;
public class SpinnerTest2 {
public static void main(String[] args) throws Exception {
UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
JFrame f = new JFrame();
f.setDefaultCloseOperation(JFrame.DISPOSE_ON_CLOSE);
f.add(createOtherPanel("First group"), BorderLayout.NORTH);
f.pack();
f.setLocationRelativeTo(null);
f.setVisible(true);
}
private static JPanel createOtherPanel(String title) {
JPanel p = new JPanel(new FlowLayout());
p.setBorder(BorderFactory.createTitledBorder(title));
p.setLayout(new FlowLayout());
p.add(new JLabel("This is a label"));
p.add(new JButton("A button"));
p.add(new JButton("Another"));
p.add(new JSpinner());
return p;
}
}
---------- END SOURCE ----------
java version "1.6.0_04"
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
1.6.0_10-b33
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
EXTRA RELEVANT SYSTEM CONFIGURATION :
Must have JAWS installed and the JDK setup with accessbridge. You can download trial 40-minute version of JAWS here: http://www.freedomscientific.com/products/fs/jaws-product-page.asp
I just ran against 1.5.0_08 and the problem still occurs. Unfortunately I don't have any earlier release. So I guess I can't be sure it is a regression except that I know we didn't hit this issue during our last round of VPAT/508 testing.
It may be some strange incompatibility with JAWS 9.0 as well.
A DESCRIPTION OF THE PROBLEM :
If you have a Swing application that contains a JSpinner, JAWS will stop reading the accessible text of *all* components shortly after giving focus to the JSpinner. JAWS will continue to read things like keystrokes, but will not read accessible text.
This seems like a fairly serious accessibility problem for Swing UIs.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
With JAWS installed and enabled, run the attached program SpinnerTest2. Confirm that JAWS is working by tabbing between the two buttons only -- it should read "first group group box a button button" and "first group group box another button button" repeatedly.
Then tab over to the spinner. JAWS will read the spinner. Then tab off of it back onto the button, and tab a few more times. JAWS will stop reading all accessible text -- the buttons and the spinner. JAWS will occasionally read the wrong text for the focused component (e.g., it will read the text of the first button when you are on the second).
At this point it is broken and can only be fixed by restarting JAWS (even restarting the Java application does not fix it).
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Expected JAWS to continue reading accessibility text.
ACTUAL -
JAWS stops reading accessibility text for JComponents once the spinner has been given focus.
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import javax.swing.event.*;
import javax.swing.text.*;
import java.text.*;
public class SpinnerTest2 {
public static void main(String[] args) throws Exception {
UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
JFrame f = new JFrame();
f.setDefaultCloseOperation(JFrame.DISPOSE_ON_CLOSE);
f.add(createOtherPanel("First group"), BorderLayout.NORTH);
f.pack();
f.setLocationRelativeTo(null);
f.setVisible(true);
}
private static JPanel createOtherPanel(String title) {
JPanel p = new JPanel(new FlowLayout());
p.setBorder(BorderFactory.createTitledBorder(title));
p.setLayout(new FlowLayout());
p.add(new JLabel("This is a label"));
p.add(new JButton("A button"));
p.add(new JButton("Another"));
p.add(new JSpinner());
return p;
}
}
---------- END SOURCE ----------