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.
-there are missing mnemonics and description =============================================== Tested Window title : NetBeans Users Satisfaction Survey =============================================== Results of Accessibility test Doesn't implement Accessible : - none. No Accessible name : - none. No Accessible description : Class: javax.swing.JButton { Go to Survey | } Class: javax.swing.JButton { Remind Later | } Class: javax.swing.JButton { Skip Survey | } Label with LABEL_FOR not set : - none. Components with no LABEL_FOR pointing to it : - none. Components with no mnemonic : Class: javax.swing.JButton { Go to Survey | } Class: javax.swing.JButton { Remind Later | } Class: javax.swing.JButton { Skip Survey | } Components with wrong mnemonic (mnemonic isn't ASCII , label doesn't contain mnemonic): - none. Components not reachable with tab traversal : - none.
I have fixed issue with mnemonics. But there is still no accessible description. But fix for this relates to Dialogs API . And it should be other issue. The problem that usage of dialog API doesn't allow to manage A11Y for buttons that it provides. So this API should somehow set up accessible description inside its implementation . This issue concerns usage of setOption(Object[]) method in NotifyDescriptor class. This method should lead to setting up accessible description for created buttons in dialog. Either one need provide an API method for this. Possibly this is already fixed and should be rechecked. changeset: 70204:7f76cb083814
forgot to reassign
Now closing as fixed.
i think it's possible to use accessible enabled JButton instances in setOptions() directly...
1) You are wrong. JButton cannot be set in array with setOptions() method. It's checked. Please read documentation for this method. JButton will be converted into String via toString() and just labels appears in Dialog, not JButtons. 2) Even if such suggestion would be possible there is still bug in Dialogs API becuase in this case usage of setOptions(String[] ) method will always lead to bad result : there will be no a11y support in resulting buttons. So why one need such method at all ? Each time when you need good a11y support you will need to use your own Jcomponent in setOptions() method. It is problem implementation of API or API itself. 3) You suggestion can be applied to DialogDescriptor class. But in this case you will need to provide your own content panel and this will lead to change UI. And moreover you are not able to use NotifyDescriptor nested classes in this case ( when you need to set up your own text for JButtons ). So each time problems in Dialogs API appears and the best way to fix a lot of related possible problems is fix in Dialogs API , not in each usage of this API.
Ops, sorry . I don't understand why in previous time when I checked there was just label instead of button. You are right , it is possible to set JButton via setOptions. I will do it . But I still think that there is issue in impl of Dialogs API because setOptions(String[] ) method should never be used because of a11y problems.
Fully fixed ( access. descr is added also ). changeset: 70667:5c0828406168