No Accessible name :
   Class: javax.swing.JTabbedPane {  |  } 


 No Accessible description :
   Class: javax.swing.ColorChooserDialog {   |  } 
   Class: javax.swing.JButton {  Cancel |  } 
   Class: javax.swing.JButton {  OK |  } 
   Class: javax.swing.JButton {  Reset |  } 
   Class: javax.swing.JTabbedPane {  |  } 

What we can do here is really just adding a dialog title that tells it's a color
chooser dialog, those buttons don't need any description, the name says it all.
The JTabbedPane is out of our control.

I don't think it's necessary to go with the approach to take JColorChooser panel
and display with NB dialog, it only gives us the control over buttons and dialog
description, and as I said, those components have unambiguous accessible names,
they are fine. 

Dialog title has been added.

yes, title is good, but according to netbeans absent of a11y description is an
important issue.

OK, we may have gone too far on this whole a11y exercise.

Let's get to the bottom of the problem. Why do we care about accessible name and
description? To make our tool accessible to the visually impaired by providing
descriptions of the components that will receive focus. A component receives
focus when a user or AT reader selects it, usually via keyboard controls.

AccessibleContext() defines two methods that can be used to provide accessible
information:

    * setAccessibleName(String name) sets the name to associate with a given
Accessible object. Typically, an assistive reader will present this name
whenever a component receives focus.

    * setAccessibleDescription(String description) sets the description to
associate with a given Accessible object. Typically, an assistive reader will
present this description when the user asks for more details about a component.

Having a description is always better when the name is considered insufficient
to describe the component, which I'm not convinced is the case here. When we
look at OK, Cancel, Reset buttons do we have questions on what those buttons are
for? 

I hope we have a common understanding on this issue now, and move on. I suggest
we close all those color chooser dialog bugs, leave one ( or create one ) to
depend on the JDK fix for the tracking purpose.

dialog title has been added so this is no longer a p1 issue.

If the dialog or a component name is obvious, a description is not necessary.
For this issue, the title for the Background Color and Border Color dialogs have
the same name "Color Chooser", I'd suggest to add a simple description to
indicate that this it's a color chooser for background for one and border for
the other. If this can not be fixed now, it can be marked for future in the
target milestone.

Change dialog name to "Background Color Chooser".

ok, changed dialog title to be more specific

verified in build netbeans-6.0-nightly-200705161200.