This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
a11y module output: Dialog: Specify Code Fragment No Accessible description : Class: javax.swing.JButton { OK | } Class: org.netbeans.core.windows.services.NbDialog { Specify Code Fragment | } Class: javax.swing.JFormattedTextField { | } Class: javax.swing.JFormattedTextField { | } Components with no mnemonic : Class: javax.swing.JButton { Select... | Selects a class from opened projects. } Class: javax.swing.JRadioButton { Part of Method Code: | Only a part of method defined by lines will be profiled. } Class: javax.swing.JRadioButton { Whole Method: | Whole method will be profiled. } No Accessible name : Class: javax.swing.JFormattedTextField { | } Class: javax.swing.JFormattedTextField { | } Components with no LABEL_FOR pointing to it : Class: javax.swing.JFormattedTextField { | } Class: javax.swing.JFormattedTextField { | } Dialog: Select Class No Accessible description : Class: javax.swing.JButton { OK | } Class: org.netbeans.core.windows.services.NbDialog { Select Class | } Components with no LABEL_FOR pointing to it : Class: org.openide.explorer.view.TreeView$ExplorerTree { Opened projects explorer. | Select a class from available projects. }
According to NetBeans Accessibility Guide (http://a11y.netbeans.org/a11yDevGuide.html) accessible descriptions need to be set for "components whose context is not obvious from their names". Please specify concrete components which you think don't have self-explaining accessible names (excl. javax.swing.JFormattedTextField).
I think the accessible names are sufficient.
Fixed accessibility for JFormattedTextFields, available in release55 branch. Mnemonics won't be fixed as this dialog isn't used in trunk.
closed