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 25685 - Top Components in SDI mode or undocked from MDI haven't set Accessible Descriptions
Summary: Top Components in SDI mode or undocked from MDI haven't set Accessible Descri...
Status: CLOSED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Peter Zavadsky
URL:
Keywords: A11Y
Depends on:
Blocks:
 
Reported: 2002-07-16 13:37 UTC by Marian Mirilovic
Modified: 2008-12-23 09:07 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2002-07-16 13:37:39 UTC 
[nb_34](20020716), [jdk1.4.0](fcs)


For example Output Window

No Accessible description :
   Class:
org.netbeans.core.windows.frames.TopFrameTypeImpl
{  Output Window [CoreTests.TestInsideIDE - I/O]
|  }
Comment 1 Marian Mirilovic 2002-07-16 14:14:59 UTC 
The same result for 
Properties of something window.
Comment 2 Marian Mirilovic 2002-07-16 14:46:13 UTC 
Search results
Comment 3 Marian Mirilovic 2002-07-16 15:51:03 UTC 
[nb_34](20020716), [jdk1.4.0](fcs)

The same result for internal frames

No Accessible description :
   Class: org.netbeans.core.windows.frames.InternalFrameTypeImpl { 
Output Window [Output] |  }
Comment 4 Peter Zavadsky 2002-07-16 18:00:44 UTC 
Accessible names are not set for the frames. 
With the accessible descriptions is a problem they are set from
currently selected TopCompoennt in the mode frame. If the selected
TopComponent has null accessible description it is also set for frame.
I fix it that way, to the frame will set description pointing out the
selected TopComopnent has null accessible description.
Comment 5 Peter Zavadsky 2002-07-16 18:16:10 UTC 
Fixed in [trunk]

Fix:
org/netbeans/core/windows/Bundle.properties [1.8]
                         /ModeImpl.java [1.152]
                         /frames/Bundle.properties 
                                /InternalFrameTypeImpl.java [1.27]
                                /TopFrameTypeImpl.java [1.19]

Note:
Now the frames have the accessible names and in case the selected
TopComponent doesn't have accessible description (is null), then is
set accessible description which describes the component name,
pointiing out it doesn't have an accessible desciption.
Comment 6 Marian Mirilovic 2002-07-17 09:40:50 UTC 
In my opinion your fix isn't the best what we can do. Why ?

because if we explicitly set Accessible Description in
InternalFrameImpl or TopFrameTypeImpl if top component doesn't provide
it (its AD=null) it will be hard to top components with AD=null,
because tools for testing accessibility looks only for components with
AD,AN = null.

SO reoepen, please revert this fix, thanks.
Comment 7 Peter Zavadsky 2002-07-17 09:48:40 UTC 
The changes of the fix reverted.

The accessible description for the frames are retrieved from the
currently selected component, thus if the component has null
accessible description it is propagated to the frame (that's the
problem). 

Note: there cannot occure the situation the null is passed from other
 reason.
If no selected component is found, there is still some description set.
Comment 8 Marian Mirilovic 2002-07-17 10:14:53 UTC 
Thanks for explanation,

I have filed issues against appropriate top components:

issue 25718 - OutputTabTerm has null Accessible Description
issue 25719 - Properties Window has null Accessible Description
issue 25721 - Serach Result has null Accessible Description