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.

Bug 127908 - [A11Y] Missing Accessible Description in Add Java Platform dialog
Summary: [A11Y] Missing Accessible Description in Add Java Platform dialog
Status: VERIFIED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Platform (show other bugs)
Version: 6.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords: A11Y
Depends on:
Blocks:
 
Reported: 2008-02-20 16:28 UTC by Petr Dvorak
Modified: 2008-04-14 12:07 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Dvorak 2008-02-20 16:28:38 UTC
[A11Y] Missing accessible description in dialog (P1): Tools > Java Platforms > Add Java Platform (2st step)

Result of A11Y test:

===========================================
  Tested Window title : Add Java Platform 
===========================================

Results of Accessibility test

Doesn't implement Accessible : - none.

No Accessible name : - none.

No Accessible description :

Class
    org.netbeans.core.windows.services.NbDialog { Add Java Platform | } 

Label with LABEL_FOR not set : - none.

Components with no LABEL_FOR pointing to it : - none.

Components with no mnemonic : - none.

Components with wrong mnemonic (mnemonic isn't ASCII , label doesn't contain mnemonic): - none.

Components not reachable with tab traversal :

Class
    javax.swing.JButton { Cancel | n/a } 
Class
    javax.swing.JButton { Help | Help button } 
Class
    javax.swing.JButton { Next > | Next step: 3. Detected Platforms }
Comment 1 Karol Harezlak 2008-02-25 10:26:28 UTC
It's not mobility related issue, please change module to the one related to the Java Platform.
Comment 2 Jaromir Uhrik 2008-02-25 12:31:51 UTC
Reassign to java/platform. The priority is assigned properly - the fix seems to be simple.
Comment 3 Tomas Zezula 2008-02-25 13:20:39 UTC
JFileChooser embedded  into panel.
JFileChooser => not accessible
<Modus Ponens>
not accessible

Comment 4 Lukas Hasik 2008-02-25 15:58:00 UTC
Tomasi, the reason why the issue is P1 is 
No Accessible description :
Class
    org.netbeans.core.windows.services.NbDialog { Add Java Platform | } 

You should provide accessible description for dialog that is created by NB. The filechooser is just a part of the Add
Platform dialog, right?
Comment 5 Tomas Zezula 2008-02-25 16:08:20 UTC
OK, I can provide AD for the dialog, but I cannot do anything with the focus traversal.
I will add the AD for the Panel.
Comment 6 Petr Dvorak 2008-02-25 16:11:26 UTC
Focus traversal works... Problem is with the plugin... Ignore focus traversal in A11Y issues unless explicitly specified.
Comment 7 Tomas Zezula 2008-02-25 18:20:58 UTC
Missing AD on NbDialog evaluation:
The WizardDescriptor.Panel.getComponent() has AD. The NbDialog (NbPressenter subclass) delegates to currentMessage which is 
WizardDescriptor.WizardPanel which delegates to rightComponent which implements Accessible and provides AD => the NbDialog has an AD.
Strange thing is that I got completely different output from accessibility tester (downloaded from: http://a11y.netbeans.org/Instructions.html)
Here is what I got on my MacBook Pro (10.5.2):
===============================================
 Tested Window title : Add Java Platform
===============================================

Results of Accessibility test


 Doesn't implement Accessible :
   Class: org.netbeans.swing.dirchooser.InputBlocker {  } 


 No Accessible name :
   - none.

 No Accessible description :
   - none.

 Label with LABEL_FOR not set :
   - none.

 Components with no LABEL_FOR pointing to it :
   - none.

 Components with no mnemonic :
   - none.

 Components with wrong mnemonic (mnemonic isn't ASCII , label doesn't contain mnemonic):
   - none.

 Components not reachable with tab traversal :
   - none.

Comment 8 Petr Dvorak 2008-04-14 12:07:48 UTC
Verified: 20080411

(Results of the accessibility testing are the same as tzezula says, which means they are correct and I probably messed
up something when working with the a11y plugin).