Hi Sean, I don't think this is necessary. My reasoning is that a sighted person has no idea whether to press enter or not, unless it says so. You can associate an action with a text field, but you should also have a label saying "Enter a number and press enter". Unless, of course, it is obvious from the context. In other words, it comes down to good UI design, whether you're seeing the screen or using a screen reader. In uni they taught us how to enter text into a text field by pressing enter just because it's a convenient way of getting user input without first teaching students about buttons. I'd be interested to know if you know of any professional applications that use this method for anything useful. Saqib -----Original Message----- From: speakup-bounces@xxxxxxxxxxxxxx [mailto:speakup-bounces at braille.uwo.ca] On Behalf Of Janina Sajka Sent: 29 April 2004 21:41 To: Sean McMahon; Speakup is a screen review system for Linux. Subject: Re: accessability with reguards to java not necessarily linux onlybut may be useful This issue would be appropriate to the Java Accessibility list that Sun hosts: JAVA-ACCESS at JAVA.SUN.COM The Sun Java developers, including Peter Korn, monitor and contribute on that list. Sean McMahon writes: > Pleasse pass this along to some one who might have more use for it or > direct me to someone who might have more use. Yesterday I handed in a > program which a gui to my instructor and informed him that although > there were 6 buttons there were > 8 calculatable functions he wanted and did not specify the implementation for. > Inother words there were 2 missing buttons. Sinse his guidelines were > strict about the gui implementation, I informed him of his mistake. > At this point I was embarrassed to discover that the functions I > needed were to be implemented by pressing enter after typing > information into the edit field. No pressing enter does not click one > of the gui's buttons it performs it's own function provide you've > defined it in the program which is how this assignment is supposed to > work. This is a major problem because java defines the class as an > edit field and does not require any additional properties for that > edit field to say whether you can hit enter and invoke a function or > not. It does have an editable property fore fields which you can not > edit . I think those of us who program should get a hold of those who > develop java and request the change in implementation so a screen > reader can see whether the edit field is one which also acts like a button or just a plane old text field. My question for any of you is how do we go about making this change and who do we inform? > > Write to me privately if you'd rather not clog up this list. > Sean PS. when I finnish the code I can send to anyone who wants it > so you can see what I'm talking about. > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Janina Sajka, Director Technology Research and Development Governmental Relations Group American Foundation for the Blind (AFB) Email: janina at afb.net Phone: (202) 408-8175 _______________________________________________ Speakup mailing list Speakup at braille.uwo.ca http://speech.braille.uwo.ca/mailman/listinfo/speakup
