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 110415 - [A11Y] Missing accessible description in Include/Exclude dialog
Summary: [A11Y] Missing accessible description in Include/Exclude dialog
Status: RESOLVED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords: A11Y
: 128194 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-07-20 13:35 UTC by Jiri Prox
Modified: 2008-02-25 06:49 UTC (History)
0 users

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 Jiri Prox 2007-07-20 13:35:33 UTC
Product Version: NetBeans IDE Dev (Build 070720) 
Java: 1.6.0_02-ea; Java HotSpot(TM) Client VM 1.6.0_02-ea-b02 
System: Linux version 2.6.5-1.358 running on i386; UTF-8; en_US (nb) 
Userdir: /home/jp159440/.netbeans/dev

Accessible descriptions are missing in Include/Exclude dialog

===============================================
 Tested Window title : Configure Includes & Excludes
===============================================
 
Results of Accessibility test
 
 
 Doesn't implement Accessible :
   - none.
 
 No Accessible name :
   - none.
 
 No Accessible description :
   Class: javax.swing.JList {  Excluded Files: |  }
   Class: javax.swing.JList {  Included Files: |  }
   Class: javax.swing.JTextField {  Excludes: |  }
   Class: javax.swing.JTextField {  Includes: |  }
   Class: org.netbeans.core.windows.services.NbDialog {  Configure Includes & Excludes |  }
 
 
 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.
Comment 1 Jesse Glick 2007-07-23 21:33:26 UTC
Why does a component with a label need a separate accessible description? I would just give it the same acc desc as the
label already says. After all, we presume the dialog is somehow meaningful for the average user who can see it, who is
understanding the usage of the components based on the associated label. Same for the dialog - what would an acc desc
provide that the regular title doesn't already? Please advise, as this makes little sense to me.
Comment 2 Jaromir Uhrik 2007-07-24 08:55:23 UTC
Jesse is right. There is no need of acc. description in this case.
Comment 3 Jesse Glick 2007-07-24 19:06:54 UTC
In that case, why does the tool report such a dialog as erroneous? I am guessing there would be dozens or even hundreds
of such issues in Issuezilla. Is there a document which describes exactly what the criteria for A11Y are?
Comment 4 Jiri Prox 2008-02-25 06:49:32 UTC
*** Issue 128194 has been marked as a duplicate of this issue. ***