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 18614 - Implement AccessibleSelection for components in designer
Summary: Implement AccessibleSelection for components in designer
Status: CLOSED WONTFIX
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords: A11Y
Depends on:
Blocks:
 
Reported: 2001-12-13 12:54 UTC by Marian Mirilovic
Modified: 2005-07-15 13:20 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2001-12-13 12:54:41 UTC
[nb](3.3)

 Doesn't implement Accessible :
   Class: org.netbeans.modules.form.fakepeer.FakePeerContainer {  } 


 No Accessible name :
   Class: org.netbeans.modules.form.HandleLayer {  |  } 


 No Accessible description :
   Class: org.netbeans.modules.form.HandleLayer {  |  } 

and new added components haven't Accessible descriptions,
and issue 18412 - no accessible description of Top Component.
Comment 1 Filip Rachunek 2001-12-14 08:46:03 UTC
Reassigned.
Comment 2 jrojcek 2001-12-17 13:00:13 UTC
Will be fixed in 3.3.1.
Comment 3 Marian Mirilovic 2002-01-07 17:57:04 UTC
This issue must be fixed in 3.3.1, rise priority to P2
Comment 4 jrojcek 2002-01-08 20:29:34 UTC
Description of HandleLayer is fixed. There is no need to set
description to FakePeerContainer.

There still exist problem with accessible context of selected
component in Form designer. As the component is not focused then
assistive technology doesn't have access to accessible context of such
component. HandleLayer should provide implementation of
AccessibleSelection interface, but the documentation of accessible
APIs is not absolutely clear about it and it is also hard to test
whether the implementation is correct. So for now I would mark it
enhancement. Keyboard users and users of assistive technologies should
use only Component Inspector which is accessible when working with
designer.
Comment 5 Marek Grummich 2002-07-22 09:58:22 UTC
Set target milestone to TBD
Comment 6 Marek Grummich 2002-07-22 10:02:06 UTC
Set target milestone to TBD
Comment 7 Tomas Pavek 2005-05-16 17:45:43 UTC
We could probably do this, however I doubt it makes sense practically - the
designer canvas is completely visual and interactive component where the
AccessibleSelection can't help with designing the GUI anyway. The selection
itself can be tracked in Inspector, as already pointed out.
Comment 8 Marian Mirilovic 2005-07-15 13:20:19 UTC
closed