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 83260 - a11y: Properties. Stereotypes window - Name textfield unreachable by keyboard
Summary: a11y: Properties. Stereotypes window - Name textfield unreachable by keyboard
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Properties (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Yang Su
URL:
Keywords: A11Y
Depends on:
Blocks:
 
Reported: 2006-08-23 10:12 UTC by bugbridge
Modified: 2006-11-13 15:59 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 bugbridge 2006-08-23 10:12:22 UTC
Class Element --> Properties --> Stereotypes

Results of Accessibility test, window with title "Class - Stereotypes"
 
Components not reachable with tab traversal :
   Class: javax.swing.plaf.basic.BasicComboBoxEditor$BorderlessTextField
Comment 1 Andrew Korostelev 2006-08-24 09:07:29 UTC
Can't enter stereotype name.
how to reproduce:
- open properies for class element on class diagram
- open Stereotypes editor dialog
- press 'Alt+A' to add new empty stereotype record.
issues:
* can't edit name textfield even if it is selected using tab traversal
* can't access name combobox using tab traversal
Comment 2 Yang Su 2006-11-10 23:03:42 UTC
OK, I did a little research on the issues related to editable combo box as table
cell editor, see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4513773

Default behavior is to use F2 to enter editing mode in combo box.

We now provide mnemonic access to the table, tab also traverses through table
cells, a11y issues are resolved. However, a much bigger issue remains, while
adding a new record with empty row, we do not validate user input, and in
property customizer, the client has no control over the property dialog to
enable/disable OK button based on the data validity. I see quite a few bugs
around this property customizer in deleting and saving the record. 

In order to address data validation, we can consider providing an input dialog
when "Add" is invoked, a valid record will then be inserted to the table. Seems
like "Add", "Edit" and "Delete" combination is the standard UI for manipulating
list/table records.
Comment 3 Andrew Korostelev 2006-11-13 15:59:57 UTC
I verify this issue.
User has an ability to edit cell content.
But we use too much different approaches...