[ui-dev] AT suggestions

[Everett Zufelt]

Good evening,   My name is Everett Zufelt.  I am new to using OpenOffice and to this list.  I am a blind user, I use JAWS 7.0 as my screen-reader of choice.  I have some background in computer programming, VB and Java mostly, so hopefully I will be able to make coherent comments and suggestions.   What I have noticed about OpenOffice's interaction with JAWS, or perhaps with the Java Access Bridge depending on where the problem lies, follows.   1.  When speaking menu items, JAWS does not read the name of menu items which themselves contain a sub-menu (e.g. Edit > Changes) until I hit the right-arrow key.  Once I do this the name of the sub-menu and the first sub-menu item are spoken.   2.  When using the down arrow key within a document the first line of most paragraphs is not spoken until I find the second line of the paragraph and then press the up arrow once.   3.  In most word processors, and other programs, pressing CTRL + down-arrow moves the cursor to the beginning of the next paragraph and begins reading.  This does not happen with OpenOffice, this is an intuition for me, and I assume other screen-reader users, that may improve the appeal and usability of the program.   4.  When reaching a blank line in an OpenOffice Writer document the word "Edit" is spoken by JAWS.  Though this is minor in comparisson to the prior comments I have mentioned, it would be nicer if the word "blank" were spoken.   5.  Finally, I have noticed that the text (edit) boxes on the Find and Replace dialog are not labled (or atleast the lable is not read by JAWS when I tab to each field.     I do not mean these comments to be complaints.  I have mostly enjoyed working with OpenOffice this past week and plan to continue using it.  I hope my comments can contribute to the program.     Regards, Everett