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 89906 - a11y: unable to access some fields in the project properties dialog box
Summary: a11y: unable to access some fields in the project properties dialog box
Status: CLOSED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Thomas Preisler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-23 00:51 UTC by julieg
Modified: 2007-12-21 15:35 UTC (History)
0 users

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 julieg 2006-11-23 00:51:21 UTC 
Several A11Y issues are found in the project properties dialog:
1) the Tab key does not reach Ok or Cancel buttons
2) No focus shown in the "Configuration Properties" with the Tab key
3) the Tab key goes through each field in "Project Defaults"
   (The Tab key works the same as the down arrow key)
Comment 1 Thomas Preisler 2007-01-09 21:05:29 UTC 
1) confirmed
2) don't think it is a bug. Initial focus is not on the Configuration Properties
node but un the General node. If you set focus on the Configuration Properties
node and tabs several times, it gets focus again when it comes back to this panel
3) Isn't this OK? If not, please open a separate issue against NB. This is
'standard' property panel behavior.
Comment 2 Thomas Preisler 2007-01-11 23:23:03 UTC 
1) It is correct that OK and Cancel buttons are not reachable with plain tabs,
but if you hit ctrl+tab when focus is in the property sheet, focus jumps to the
read-only field below the sheet and then a regular tab takes you to the OK
button. So the tab sequence to take you to OK button is: tab, tab, Ctrl+tab,
tab. This make the dialog accessible (even the sequence is not obvoius).
2) is fixed
3) is OK (I believe). If not, pls open a separate issue against NB. It is not
fixable in our code.
Comment 3 dnikitin 2007-12-21 15:35:17 UTC 
1),3) it's ok
2) verified

I will closed this issue