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 22341 - a11y: press/release alt for resize,minimize,maximize etc. doesn't work in single window mode
Summary: a11y: press/release alt for resize,minimize,maximize etc. doesn't work in sin...
Status: CLOSED DUPLICATE of bug 17550
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@ide
URL:
Keywords: A11Y
Depends on:
Blocks:
 
Reported: 2002-04-12 02:02 UTC by Peter W Carlson
Modified: 2011-05-24 16:00 UTC (History)
2 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 Peter W Carlson 2002-04-12 02:02:38 UTC
This is a core a11y bug.  

We allow the user to run the IDE in either of two modes: 
they can run in single-window mode where all IDE content 
is contained in one window or they can run in multiple 
window mode where each component is independent of the 
others.
The bug is really a design issue.  When in single window 
mode, hitting and releasing "Alt" (and then an arrow key) 
will bring up a menu with "resize", "move", "close" etc.  
Since the entire IDE is in one window these functions will 
be applied to the IDE as a whole.  There isn't a way to 
apply these functions to the individual components.
So, for example, the user might have a properties sheet 
open, hit and release "Alt" and select "close" (or the 
user might just hit "Alt-F4") and it will try to close the 
entire IDE rather than the property sheet.
Comment 1 Marian Mirilovic 2002-04-12 08:23:39 UTC
a11y is a module, please next time file issue against appropriate 
module, thanks.
Comment 2 Jan Chalupa 2002-04-21 07:02:07 UTC
This issue has been presented to the Sun's Accessibility Program
Office some time ago. The question was whether the SDI multi-window)
interface can be considered a viable alternative to the MDI
(single-window) mode from the accessibility point of view. The answer
was "yes", as long as:

o they both provide the same functionality
o the SDI version is completely covered in the product's         
documentation and meets 508's requirements
o the SDI resident online help meets 508's requirements
o the assessment you turn in makes a note on the SDI/MDI point 

Based on this, it is believed that, the SDI mode *is* accessible and
can be considered a viable alternative to the MDI mode.

The accessibility problem in MDI does need to be addressed in future
releases, but it's not a showstopper for FFJ 4.0. I'm lowering the
priority to P3.


Comment 3 Jiri Mzourek 2002-04-24 12:54:29 UTC

*** This issue has been marked as a duplicate of 17550 ***
Comment 4 Quality Engineering 2003-07-01 15:16:02 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 5 Quality Engineering 2003-07-01 15:19:05 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.