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 36638

Summary: a11y: no accessible name for JTextField in the 'Source Editor [properties *]' dialog
Product: utilities Reporter: bnv <bnv>
Component: PropertiesAssignee: issues@utilities <issues>
Status: RESOLVED FIXED    
Severity: blocker CC: bnv, ccv, juhrik, mbudris, petersl, vgorr
Priority: P3 Keywords: A11Y
Version: -S1S-   
Hardware: Sun   
OS: SunOS   
Issue Type: DEFECT Exception Reporter:
Attachments: A11Y tester output

Description bnv 2003-10-16 11:09:52 UTC
Product Version:  Sun ONE Studio 5  Standard
Edition (Build 030904)
IDE Versioning:   IDE/1 spec=3.42.2 impl=030904
Operating System: SunOs version 5.8 running on sparc
Java:             1.4.1_05


    To reproduce the bug:
1. Create template Other/Property File from New Wizard
2. Highlight 'properties' node in the explorer tree
3. Select 'Open' from context menu
4. Wait for the 'Source Editor[properties *]' dialog
5. Add New Property in the table

See results of Accessibility Tester:
===============================================
Tested Window title : Source Editor[properties *]
===============================================
Results of Accessibility test

 No Accessible name :
   Class: javax.swing.JTextField {  |  } 

 No Accessible description :
   Class: javax.swing.JTextField {  |  }
Comment 1 pzajac 2003-10-20 09:18:22 UTC
reassigned to properties module.

Comment 2 Marian Petras 2003-10-20 11:57:26 UTC
Accepted.
Comment 3 Jaromir Uhrik 2004-05-26 15:35:12 UTC
[200405251800; j2sdk1.4.2_04]
Mariane it seems to be working perfectly now - see attached a11y
tester tool. I hope this issue is about "New Property" Dialog (it's
not clear to me from the description) - if I am right please mark it
as resolved.
Comment 4 Jaromir Uhrik 2004-05-26 15:35:40 UTC
Created attachment 15285 [details]
A11Y tester output
Comment 5 Jan Stola 2004-06-04 14:56:15 UTC
I agree with Jaromir Uhrik's comment. The New Property dialog
seems to be accessible. Unfortunately it is not clear
whether this issue was about this dialog. Feel free
to reopen if it was about another window that still has
some accessibility problem.